04b — DOT Registry Reuse-First & Search Evidence — 2026-06-22

LABELS: LOCAL_DISPOSABLE_SANDBOX_DOT_EMULATOR · NOT_GOVERNED_RUNTIME · NOT_PRODUCTION · NOT_DIRECTUS_GOVERNED_WRITE · NOT_A_SUBSTITUTE_FOR_DOT_C1_REGISTRATION

Honors the DOT reuse-first rule. Registry consulted read-only before finalizing any DOT.

Registry sources consulted

• dot_tools collection (governed directus DB) — 309 tools total; entity dot_tool; meta-catalog CAT-006; sync dot-catalog-sync.
• dot_agent_api_contract — registered executable contracts (2 rows).
• dot_operations (code/name/description).
• Handbook pointers (KB): …/newlaws/dot-manage/dot-usage-handbook.md, …/newlaws/operations/dot-usage-handbook.md.

Required search (terms → result)

Query: dot_tools where code/name/operation ILIKE the C1 concept terms.

Term	Found in governed registry?	Notable hits
SCHEMA / ENSURE	Yes (family)	DOT_SCHEMA_ENSURE + 23× DOT_SCHEMA_<X>_ENSURE incl. DOT_SCHEMA_TABLE_REGISTRY_ENSURE, DOT_SCHEMA_REGISTRY_COLLECTIONS_ENSURE; DOT-TAC-SCHEMA-ENSURE
VERIFY	Yes (pattern)	DOT_GOV_VERIFY, DOT_KG_*_VERIFY, DOT-TAC-SCHEMA-VERIFY, DOT-CONTEXT-PACK-VERIFY (paired-verifier norm)
ROLLBACK	Yes	DOT-062 / dot-rollback (coverage_status=partial)
PREFLIGHT	No dedicated DOT	(verify pattern exists; no preflight-named DOT)
TABLE_REGISTRY	Yes	DOT_SCHEMA_TABLE_REGISTRY_ENSURE
REGISTRY	Yes	DOT_SCHEMA_REGISTRY_CHANGELOG_ENSURE, DOT_SCHEMA_REGISTRY_COLLECTIONS_ENSURE
C1	No	none
VOCAB	No	none
CANONICAL	No	none
HARNESS	No	none
EVIDENCE	No DOT (collections exist)	none in dot_tools
CREATE_COLLECTION / DIRECTUS	No DOT primitive	IU collection-create search → 0 rows; dot_iu_create_collection = IU-staging, not a Directus-DDL/canonical-vocab primitive

A. Existing DOT reused (pattern reuse for future governed promotion)

• Schema-ensure family pattern (DOT_SCHEMA_*_ENSURE, incl. DOT_SCHEMA_TABLE_REGISTRY_ENSURE) — the governed canonical way to ensure a collection + register it in table_registry. Future governed C1 ensure MUST follow this naming/pattern, not invent a parallel scheme.
• Producer+verifier pairing (DOT_KG_EXPLAIN/DOT_KG_EXPLAIN_VERIFY) — the governed contract norm; C1 build/verify must be a registered pair.

B. Existing DOT rejected with reason

DOT	Why it cannot be reused as-is for C1
DOT_SCHEMA_ENSURE (generic)	ensures schema generically; no canonical_operation_vocab shape, no resolver R_C1 over apr_action_types, no manifest/hash binding, no C1 carrier scope
DOT_SCHEMA_TABLE_REGISTRY_ENSURE	ensures the table_registry collection itself, not the C1 vocab table; reused only as the registration step pattern
DOT-062 / dot-rollback	generic, coverage=partial; not C1-carrier-scoped; no versioned-supersession validity oracle for canonical_operation_vocab
*_VERIFY family (KG/GOV/TAC)	domain-specific; none bind C1 manifest_hash / plan_ref / grant
dot_iu_create_collection (memory)	IU-domain staging primitive; not a governed Directus-DDL/canonical-vocab creator

C. New DOT created — SANDBOX EMULATOR ONLY (category E, not governed)

Seven C1-scoped DOTs were created only in the disposable sandbox c1.dot_agent_api_contract (contract_status='sandbox'): DOT_C1_SCHEMA_ENSURE, DOT_C1_VOCAB_BUILD, DOT_C1_VOCAB_VERIFY, DOT_C1_PREFLIGHT, DOT_C1_BAD_INPUT_HARNESS, DOT_C1_EVIDENCE_READBACK, DOT_C1_ROLLBACK_CHECK. They prove logic/shape only.

D. New DOT registry/catalog update — N/A (correctly)

• No governed DOT was created. Governed write is impossible from here (read-only/denied/docs-only — file 02) and forbidden (DOT-only rule). Zero governed mutations.
• Per rule #8, sandbox emulator DOTs MUST NOT be registered as governed DOT unless promoted through the governed registry path. They are therefore deliberately not in dot_tools/CAT-006.
• The HOLD C1_DRYRUN_HOLD_DOT_REGISTRY_NOT_UPDATED fires only when a new governed DOT is created but unrecorded. That precondition is false here → HOLD does not apply.

E. Local sandbox DOT emulator only — not governed DOT

All DOT_C1_* names exist solely in the sandbox emulator, labeled LOCAL_DISPOSABLE_SANDBOX_DOT_EMULATOR. No local name masquerades as governed DOT; no orphan governed DOT exists.

Carry-forward into the operator action (file 13)

Future governed promotion should reuse the schema-ensure family pattern + producer/verifier pairing + extend DOT-062 for rollback, registering each into dot_tools/CAT-006 via dot-catalog-sync — not invent net-new governed contracts.