Skip to content

docs: use neutral entity language in shared guidance #311

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
abrichr wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: use neutral entity language in shared guidance #311

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/BYOC_CONNECTOR.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Cloud token creation is authenticated and organization-scoped in the dashboard.
bundle binding.
* **Up (to the control plane):** PHI-free status/metrics + a storage *path* into
the customer's own store. **Never** the report body, screenshots, OCR text, or
a patient identifier.
a record identifier.
* **The bundle and report bytes** are read from / written to the **customer's own
storage** (`--storage-root`, a local encrypted volume). Our control plane holds
no URL to them and signs no access.
Expand Down
4 changes: 2 additions & 2 deletions docs/DECISION_DELIVERY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,8 +48,8 @@ evidence.
a vocabulary the engine already owns — `Rung`, `ActionKind`, the console's halt
categories, the ARIA/UIA role names, `RecheckKind` — or is a bounded integer or
a boolean. A relay that stores this object is *structurally incapable* of
representing a patient name, an MRN, an observed value, a path, or a workflow
label.
representing a person name, a record identifier, an observed value, a path, or
a workflow label.

That is the same kind of guarantee `HumanDecisionTaskV1` already gives, and it
is checkable the same way: by reading a schema, not by trusting a detector. The
Expand Down
2 changes: 1 addition & 1 deletion docs/ECOSYSTEM_INTEGRATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ The string values are byte-identical, so a flow `Step` could emit/ingest an
- `Resolution` — which ladder rung resolved the target (`template/…/grounder`), point,
confidence, `elapsed_ms`.
- `IdentityCheck` — the pre-click same-entity verdict (`verified/mismatch/abstain/
unreadable` × `structured/pixel/vlm/context/param`). This is the wrong-patient safety
unreadable` × `structured/pixel/vlm/context/param`). This is the wrong-entity safety
core.
- `HealEvent`, `StepResult`, `RunReport`, `UnarmedStep` — audit/telemetry.
- `risk∈{reversible,irreversible}`, `identity_armed` — the halt-on-uncertainty gates.
Expand Down