REGISTRY.adoc

The Standards Registry — Retired 2026-10-09

Important

The verifiable spec registry, the generators that wrote it and the gates that checked it were retired on 2026-10-09. Nothing in this repository generates, reads or checks a registry any more. This page stays at this path so that existing links still resolve.

Why it was retired

The registry was a generated A2ML file, and A2ML is retired (owner rulings D99, D269c, D312 and D313). Descriptive metadata now lives in deed clauses (grammar: deed.abnf), k9 contracts and the k9 coordination protocol (grammar: coordination-k9-grammar_v1.2.abnf). A generator that kept writing A2ML, and a required check that failed whenever that output drifted, kept a retired format alive. They went together.

What was retired

Retired	What it did
.machine_readable/REGISTRY.a2ml	The generated spec index: one block per standard (id, stream, home, canonical doc, source_hash, route), plus pointers to specs whose source of truth lives in another repo.
scripts/build-registry.sh and its test	Wrote the registry and TOPOLOGY.adoc. --check failed on drift.
.github/workflows/registry-verify.yml	The "Registry + topology in sync" check. It also ran the Mustfile PR gate, which the required "K9-SVC contractile validation" check (k9-contractile.yml) still runs with the same two commands, and build-scorecards.sh --check --strict --verify, which nothing runs now (see below).
scripts/build-scorecards.sh and its test	Wrote 0-canon/COMPLIANCE-DASHBOARD.adoc from the per-spec scorecards. --verify executed every scorecard pass row’s check, so a claimed pass that no longer held failed CI. That execution is retired with the generator; the scorecards are frozen data until ruling R5 settles them.
hypatia-rules/registry-staleness.a2ml	Hypatia rule HYP-S006: registry staleness, and re-fetching external pointers.
hypatia-rules/implementation-inside-canon.a2ml, scripts/check-implementation-inside-canon.sh, and the 16 HYP-S009 entries in .hypatia-baseline.json	Hypatia rule HYP-S009: flagged product/build manifests below a local spec home, as listed in the registry. Without the registry it had no input and only printed a warning. The carve-out debts it baselined stay tracked in #687.
Justfile registry, topology, registry-check, scorecards*	Local entry points. just validate no longer depends on registry-check.
The registry block in hooks/pre-commit; the registry-* checks in the Mustfile; the registry clause in MUST.contractile; the registry-staleness entries in the Adjustfile and Dustfile	Local and contractile enforcement of the above.

Where the old content is

The last tree that carried the registry is frozen at 6d19ce0e:

• the registry itself;

• its generator, including the EXTERNAL_SPECS table of external pointers (owning repo, canonical URL, version pin);

• the previous version of this page, which documents the fields and the drift automation.

What stays, frozen

• TOPOLOGY.adoc and 0-canon/COMPLIANCE-DASHBOARD.adoc are kept as frozen snapshots of their last generation. Nothing regenerates them. Read them as history, not as current state.

• The per-spec scorecards are archived, frozen, at .machine_readable/archive/scorecards-v1/ (ruling R5 on #837, option B, 2026-10-09; the mapping is in scorecard-corpus-decision.adoc).

What replaces it

Nothing yet: there is no live spec index in this repository today. standards-map.toml, checked by scripts/check-standards-map.sh, maps every tracked path to its district and gate, but it is not a spec catalogue. A deeds-era replacement is a separate decision.