Raw view — DOMAIN-GLOSSARY-1@v3

sha256: 29792680370132ea0bf81ad6a2eb36449a4d93fa9a30a7517a6d50ae6b820c89

Published law page — ← laws index — raw .md

# DOMAIN-GLOSSARY-1 — v3

Word Of Clout, LLC · published as the ARCHIVE-1 supersession re-cut (attribution lines removed, rule text identical; WO-20261003-01 U0) · supersedes the v2 text (bytes archived) · stable path: /laws/domain-glossary-v3.md · sha256 (this file's bytes): see the parity receipt — LAW-SHA256 quoted there.

**NAMED CORRECTION (v1 → v2).** The v1 term "Reliance state" listed
`POLICY (a policy value, never measured), MEASURED (observed), UNVERIFIED
(no evidence), CONTESTED (evidence disagrees)` as "the four-state verdict
vocabulary." That list conflates two vocabularies. The four-state verdict
vocabulary actually carried by published record propositions (and by the
kernel's definition single-source) is `VERIFIED / UNVERIFIABLE /
CONTESTED / STALE`. `POLICY` and `MEASURED` are re-check-deadline
semantics, not verdict states; they are stated under **Recheck deadline**
below. This draft corrects the term and adds a machine-readable block so
the parity test can hold the law to the kernel enum — order-insensitive,
nothing extra.

**LAW-IS-GENERAL-1:** a law states
rules, never instances. This glossary names no record ids, no
verification ids, no subjects, no receipts. Publish-time obligation: the
published-laws manifest's `terms` list for this law is re-derived from
the published v2 text in the same one-push (the current published terms
list mirrors v1 and will drift on the POLICY/MEASURED/UNVERIFIED
correction).

These are the reading terms of a Word Of Clout published record — the
vocabulary a reader needs. They are domain words, not system names: each
term is either defined here or it does not belong in record text.

## The Rule

**The terms below are the published domain vocabulary of the records
system. Where a term carries a machine name (the name used inside
machine-replayable fields), that machine name is listed with the term and
is the machine form of the defined concept.**

- **Subject** — the person or business a record speaks about (a licensed
  practitioner or a licensed establishment).
- **Proposition** (machine name: `propositions`) — one claim about a
  subject, carrying a four-state verdict. The machine name is the plural
  collection form of the concept.
- **Candidate relation** (`candidate_relations`) — an evidence join
  between records of different authorities, carrying no verdict: a link
  proposed by evidence, ratified by nothing, and claimed by no one until
  ratified.
- **Verification** (`verifications`) — a check of one proposition against
  recorded evidence.
- **Observation** (`observations`) — something an authority's own records
  say about a subject, independent of our verdicts.
- **Claim** (`claims`) — a statement recorded from an authority's published
  material.
- **Authorization** (`authorizations`) — a grant under which an operation
  on the ledger is permitted.
- **Transition** (`transitions`) — the recorded move of a proposition from
  one state to another.
- **Source artifact** (`source_artifacts`) — the stored bytes fetched from
  an authority, kept unmodified, with their fetch provenance.
- **Published record** (`published_records`) — the signed, publicly
  served record itself; the machine name is the collection form.
- **Crosswalk generation** (`crosswalk`) — the current signed binding of
  the key authority (the state medical board) to the federal authority
  (NPPES). A record cites the generation; it never claims an unratified
  link across it.
- **Epoch** — one measurement window of the system's decay policy.
- **Evidence cutoff** (`created_at`) — the newest evidence timestamp in a
  record's derived snapshot; the record speaks only as of this moment.
- **Issuance time** (`issued_at`) — when the record itself was issued; a
  record can never acquire an earlier issuance time because its evidence
  is older.
- **Reliance state** — the four-state verdict vocabulary of published
  record propositions: `VERIFIED` (an authority's published file supports
  the proposition, within its stated reliance period), `UNVERIFIABLE`
  (the check is complete but the admissible evidence cannot establish
  it; the recorded reason says why), `CONTESTED` (comparable evidence
  disagrees; both readings are kept), `STALE` (the last supported reading
  is retained but its re-check deadline has passed). The machine-readable
  block below is the parity target: it maps 1:1, order-insensitive, with
  the kernel's definition single-source — nothing extra, nothing missing.
- **Recheck deadline** (`next_required_by`) — the earliest date a
  proposition's reliance must be re-checked. Until three monthly epochs
  have been measured, the interval is `POLICY` — a fixed policy value,
  never measured; once measured, it is `MEASURED` — computed from the
  observed cycles. `POLICY` and `MEASURED` are deadline semantics of the
  re-check interval, not verdict states.
- **Decay horizon** — how long reliance is expected to stand; provisional
  until three monthly epochs have been measured.
- **Dependency manifest** (`dependency_manifest`) — the signed list of the
  artifacts, observation ids, and verification ids a record's content was
  derived from, with the hash that binds it.
- **Canonical form** — the exact byte recipe a verifier hashes before
  checking a signature; published separately as /laws/canonicalization-v1.md.
- **Signed scope** — exactly what the signature covers: every field except
  the signature, signing, and derivation blocks.
- **Supersession** (`supersedes`) — the pointer by which a newer record
  replaces an older one; the older record's bytes never change.

## The limit, stated plainly

This glossary defines **reading terms**. It does not publish system
internals: names of collections beyond the machine names listed above,
operations, environment variables, gates, realms, paths, or people are NOT
domain vocabulary and remain barred from record text. Where a term here
carries a machine name, the machine name is permitted exactly as the
machine form of the defined concept — inside fields labeled
machine-replayable, never dressed as prose. A definition in this glossary
is the only way a collection-shaped word stops being treated as an
internal name.

## Parity

GLOSSARY-STATE-PARITY-1: the reliance-state vocabulary in the
machine-readable block below maps 1:1, order-insensitive, onto the
kernel's four proposition states — the definition single-source the
rendered definitions diff against, and the verdict enum the record pages
validate against. Nothing extra, nothing missing. The law names no
instances (LAW-IS-GENERAL-1): no verification ids, no record ids — the
vectors live in the parity runner. Parity runner:
`node lib/records/r14-3-glossary-v2-parity.test.mjs` — exit code quoted
in the commit receipt.

The machine-readable block (the parity test parses THIS block and
compares it 1:1, order-insensitive, with the kernel's four states — the
prose above is for the reader, this block is the law):

```glossary-states
reliance-state:
  - VERIFIED
  - UNVERIFIABLE
  - CONTESTED
  - STALE
```