READY-TO-ASSEMBLE-LEGO1-PATCH1 10 — [P2-1/P2-2] Truthful Blast-Radius & Overclaim Retraction — 2026-06-22

Closes Codex P2-1 and P2-2. Gate: REGISTRATION_HOLD · CAN_PROCEED = NO · 0 runtime mutations.

---

1. [P2-1] Operational dependency map (beyond the carrier graph)

"No incoming carrier edge (E1–E8)" is true but does not mean no build dependency. C1's build has these operational dependencies, each with an explicit join/preflight contract:

Operational dependency	Why C1 depends on it	Join / preflight contract
apr_action_types / process_axis_action_vocabulary (value source)	provides R_C1 candidate values + provenance	file 04 resolver; PF9
governance_build_authorization (authorization)	gates the build; exact-scoped grant	file 05 verifier; PF5
Directus metadata (directus_collections/directus_fields) + table_registry	the collection is created here (DOT-only)	file 02; PF1, PF-SCHEMA-DOT, Registry Wiring Rule
Dispatcher fn_process_agent_api_dispatch + paired DOT contract	the only execution channel	file 02; precond_endpoint_bound
Real-run gate set v_dotkg_realrun_preflight	governs DRY_RUN→REAL_RUN	file 07 PF7
dot_iu_runtime_lease (concurrency)	single-execution guard	file 05; PF-LEASE
Audit sink (governance_audit_log / governed handler)	rollback/audit evidence	file 06 S6; file 09
dot_config flips (dry_run_only, execute_enabled, real_run_enabled)	enable REAL_RUN	file 07 (BLOCK today)
President/owner authority (process_axis_action_vocabulary.requires_president; owner gate)	canon-mutating admission requires president; owner gate present	file 07 gate_dotkg_owner_present; carried …PRINCIPAL_SURFACE…

2. [P2-1] Truthful blast-radius model

Surface	Blast radius	Truthful statement
Existing C2 data	zero proven orphan — C2 absent (file 02 §5)	"No currently proven C2 data reference would be orphaned." (NOT "blast radius = 0")
Directus metadata	non-zero	a new collection writes directus_collections/directus_fields + table_registry
Audit sink	non-zero	birth + per-value admission write audit rows
Authorization	non-zero	one grant consumed
Config / gates	non-zero (if flipped)	REAL_RUN requires governed dot_config flips affecting the runtime posture
Future lookup contract	non-zero	once C2 is built, E1 becomes a live dependency on C1

Corrected claim: C1 has a bounded, non-zero operational blast radius confined to its own collection + Directus metadata + table_registry + audit + one authorization + (on REAL_RUN) governed config; it has zero proven orphan risk on existing C2 data because C2 is absent.

3. [P2-2] Overclaim retraction (superseded phrases)

Prior phrase	Where	Status	Replacement
"blast radius = 0" / "blast radius of zero"	base file 05 §3, file 06 §6	SUPERSEDED	"no currently proven C2 data reference would be orphaned; bounded non-zero operational blast radius" (§2)
"structurally complete" (re governance_build_authorization)	base file 02 §3.4, file 11	SUPERSEDED	"carries the necessary columns; enforcement is the file-05 verifier contract, unproven until a grant is created+verified"
"read-only inventory complete" / "inventory complete"	base file 02, file 13	SUPERSEDED	"read-only inventory sufficient for C1 preparation; PF7 governed real-run preflight now included; live re-verification required at build"
"the only remaining work is authority/execution"	base file 13 §2, rollup	QUALIFIED	"after PATCH1 closes P0/P1/P2, the remaining residuals are authority/execution plus the Gate-B governed review/curation act (manifest selection, config flips, owner/president, Chairman token) — all governance/execution, not missing design"

4. Honest residual classification (post-PATCH1)

Residual	Class	Preparation gap?
Gate-B governed manifest curation	governance review act	No — resolver + snapshot prepared (file 04)
Authorized schema DOT for C1 collection	authority	No — path specified; authorization is Gate-B (PF-SCHEMA-DOT)
dot_config real-run flips + owner/president present	authority/execution	No — governed by v_dotkg_realrun_preflight
Chairman exact-scoped grant	authority	No — verifier + template defined (file 05)
Execution window	execution	No

No PREPARATION_INPUT_MISSING remains. The honest claim is scoped, not absolute.

5. Boundary attestation

Design-only correction of claims; no mutation. REGISTRATION_HOLD retained; CAN_PROCEED = NO; 0 runtime mutations. Supersedes the four overclaim phrases above in the base package.