08 — DOT Manage Updates Applied / Required

Macro: DOT_MANAGE_LEGO_TRANSITION_SURVEY_FOR_C1_DRYRUN · Date: 2026-06-22.

Answers macro §3.7 + §2.1. DOT manage is updated so information does not go stale. KB-doc updates are allowed and were performed; governed-runtime registry updates are NOT executable here and are recorded as exact operator actions.

---

A. Updates APPLIED (KB_DOC_UPDATE_ALLOWED — additive, no governed-runtime mutation)

path	old issue	new addendum/status	why needed	readback evidence
…/dot-manage/dot-manage-lego-transition-status-c1-2026-06-22.md	DOT manage had no LEGO-transition / C1 status note; agents re-derived C1 status and "missing" assumptions each run	NEW status addendum: C1 status (designed+sandbox-proven, NOT registered/runnable); frozen-DOT-not-live-enforced warning; reuse-first quick ref; the single Gate-B blocker; posture	prevents stale "C1 missing, build from scratch" and "frozen DOTs are just active" assumptions	created, revision 1
…/dot-manage/README.md	README pointed only to the handbook + 9A0 reports; no link to C1/LEGO transition state	added a Contents pointer to the transition-status addendum + the full survey package	makes the transition note discoverable from the canonical entry point	patched, revision 2
…/reports/dot-manage-lego-transition-for-c1-dryrun/* (index + 01–11 + codex packet)	no transition survey existed	full survey/plan package (this set)	the macro deliverable; the standing reference	created (see index readback)
…/reports/macro-dot-manage-lego-transition-for-c1-dryrun-2026-06-22.md	—	macro rollup	top-level entry	created

Deliberately NOT done (lower-risk choice): an inline new section (§20) appended to the large canonical handbook (dot-usage-handbook.md, rev12) was not performed, because update_document replaces the full body and the handbook is large — full-body rewrite risks silent truncation of canonical content. Instead the standalone additive note + README pointer carry the same information at near-zero corruption risk. A future, careful handbook §20 pointer-edit (additive, single-section) is listed as a low-priority operator/next-agent follow-up below.

B. Updates REQUIRED but NOT executable by Claude (operator / governed actions)

required DOT-manage / registry update	why Claude cannot perform it	exact operator action
Reflect handbook §13 freeze status into live dot_tools (so dot-birth-trigger-setup, dot-birth-backfill, dot-schema-birth-registry-ensure are flagged frozen/monitored at the registry level, not just in prose)	requires a governed write to dot_tools rows (status/flag); every write tool is allowlist-denied / read-only; DOT-only rule	via the governed Directus path, set a freeze/forbid flag (or status) + extra_metadata on those rows so registry readers cannot reuse a frozen DOT
Reconcile CAT-006 record_count (309) vs actual_count (163)	governed catalog write	re-run dot-catalog-sync (on-deploy) and reconcile the catalog scan field
Register the C1 surface (collection + table_registry row + DOT_C1_* contracts + dot_tools rows)	no governed write/DDL/registration channel; lawful registrar dot-dot-register creds absent	Gate-B: see 09 one-shot plan, steps 2–6
Mint 1 scoped single-use governance_build_authorization grant + a C1 governance_object_ownership row	OSPA=0; sovereign-grant authority required; no write tool	Gate-B: 09 step 7
Supply dot-dot-register admin creds + Owner Phase-2 open	creds absent (config/credentials.local.json); Owner-only act	operator provides creds; Owner issues Phase-2 open
(REAL_RUN only, deferred) execute-gate flips + hardening GAPs 2/3/4 + DOT-executor role	Owner-only dot_config/role/grant writes	deferred until after a successful governed dry-run

C. DOT-manage staleness check (what future agents now read)

• The README (rev2) now links the transition-status addendum (rev1), which links the full survey package. A future agent entering at the canonical DOT-manage folder will find: current C1 status, the frozen-not-enforced warning, the reuse-first map, and the single blocker — without re-deriving them.
• No canonical doc content was removed or overwritten; all updates are additive.

---

Update verdict: DOT-manage update requirement is SATISFIED for everything KB-writable (addendum + README pointer + package + rollup, all readback-confirmed). All governed-runtime registry updates are precisely recorded as operator actions in B (and as the executable plan in 09). No governed registry was mutated by this macro.