12 — DOT-Manage Updates & Registry Readback — 2026-06-22

Governed registry: NO mutations (operator-only)

DOT-manage SSOT surfaces (dot_tools, CAT-006/meta_catalog, dot_agent_api_contract, table_registry) are updated only through governed DOT paths, which require the operator/deploy execution channel. This macro made 0 governed registry mutations; readback confirms all counts unchanged (file 10).

Reuse-first recorded (file 03)

• Reused (operator-run) as-is: DOT-REGISTER, DOT_COLLECTION_REGISTER, DOT_COLLECTION_CREATE, DOT_SCHEMA_ENSURE, DOT_SCHEMA_TABLE_REGISTRY_ENSURE, [DOT-REG] CDC flows.
• New via Path A (operator deploy time, not authored to runtime here): DOT_C1_VOCAB_BUILD + DOT_C1_VOCAB_VERIFY (+ C1 preflight/rollback bindings).
• Rejected wrong-fit: generic schema-ensure as a vocab authority; IU collection create; cross-axis verifiers.

Frozen/forbidden DOTs NOT reused

No FROZEN/MONITORED birth DOT was invoked. No legacy/forbidden DOT reused. (Prior survey noted handbook §13 marks 3 birth DOTs FROZEN/MONITORED while their dot_tools rows show status=active with no enforced flag — a KB-prose-vs-registry drift; this macro did not rely on any of them.)

No orphan DOT

Because nothing was partially written (no dot_tools row without a contract, no contract without an endpoint, no collection without a registry row), no orphan DOT exists as a result of this run. fn_dot_wf_orphan_detector surface unchanged.

DOT-manage status document

A status pointer is written: knowledge/dev/laws-new/newlaws/dot-manage/dot-manage-governed-c1-dryrun-p0-p6-status-2026-06-22.md — recording that the P0–P6 execution attempt confirms C1_DRYRUN_CAPABILITY_LOCKED_OPERATOR_ACTION_REQUIRED, with the exact operator action. The governed dot_tools/contract/handbook rows themselves are not editable from here (no write channel) and remain an operator action.

Result

DOT-manage = current and consistent; the only outstanding update (registering the C1 DOTs/contracts) is the operator action named in file 14.