Horos: name the boundary stone
Browse files
README.md
CHANGED
|
@@ -15,9 +15,14 @@ datasets:
|
|
| 15 |
- clinc/oos-eval
|
| 16 |
---
|
| 17 |
|
| 18 |
-
#
|
| 19 |
-
|
| 20 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 21 |
Given a free-text question, it predicts which UMA personal-data **scopes** the question
|
| 22 |
touches (e.g. `health:read`, `schedule:read`), predicts an explicit **`none`** class for
|
| 23 |
questions that touch no personal data, or signals **uncertainty** so the caller can
|
|
|
|
| 15 |
- clinc/oos-eval
|
| 16 |
---
|
| 17 |
|
| 18 |
+
# Horos
|
| 19 |
+
|
| 20 |
+
**ὅρος** — the inscribed boundary stones of ancient Athens. A horos stood at the edge of
|
| 21 |
+
a plot and announced whose land began there; some carried mortgage terms, some marked
|
| 22 |
+
sacred precincts nobody could enter. This model is a horos for personal data: an
|
| 23 |
+
on-device, multi-label scope router for [Topos](https://github.com/dialoguesai/topos)
|
| 24 |
+
that stands at the boundary of your data and names which region a question belongs to —
|
| 25 |
+
or refuses to let it pass.
|
| 26 |
Given a free-text question, it predicts which UMA personal-data **scopes** the question
|
| 27 |
touches (e.g. `health:read`, `schedule:read`), predicts an explicit **`none`** class for
|
| 28 |
questions that touch no personal data, or signals **uncertainty** so the caller can
|