<!-- DOC_STATUS: NON_AUTHORITY -->

v0.2 NVSZ Governance Fold Patch Package (2026-06-11)

Status: NON_AUTHORITY · NOT_PROMOTED · may_gate=false · decision_effect=NONE · Object: TKT-OBJ-300 (PROPOSED) Macro: TKT_V02_NVSZ_ROOT_PROVISIONING_DRYRUN_AND_GOV_FOLD_PATCH_PACKAGE · Host: T2/Claude-Code/Fable5 APPLY_NOW = NO — prepared, NOT applied. Machine-readable twin: v02-nvsz-governance-fold-patch-package-2026-06-11.json (TKT-OBJ-301).

0. Why APPLY_NOW = NO

The canonical registry JSON (tool-kiem-thu-object-registry-2026-06-10.json, rev20) and 00-index.md (rev110) are shared surfaces. T1's FIX7 lane has been mutating them this cycle (index 108→110 observed) and authority work (N7/N8/P7 inputs) may continue. Per the operating macro, canonical registry/index fold must not be applied while T1 is active — even if T1 is later confirmed inactive, application requires an explicit owner/GPT instruction. So this package prepares the exact patch and defers application. The validator enforces this too: nvsz_root_validator.py rejects any fold-apply descriptor with t1_active=true (exit 13).

1. Live collision-safety scan

• Canonical registry JSON rev20: body distinct TKT-OBJ-*, max in body = 224.
• IDs 225..262 registered via prior governance-addendum docs + 00-index pointers (the established "no 55KB rewrite" pattern), not the JSON body.
• Reserved ranges (live-confirmed against index/current-state references):
  • T1: 182..200, 208..216, 225..253, 273..288 (FIX7 N-number/N6 repair; Codex-recheck confirmed).
  • T2: 201..207, 217..224, 254..262, 263..272 (NVSZ evidence-escrow planning).
• Codex recheck current-state (2026-06-11) explicitly states: "T1 273..288 and T2 NVSZ proposed 263..272 do not collide." → block 263..272 is collision-clean.
• This macro's new objects = 289..304, strictly above T1's 288 → collision-clean.
• Highest reserved anywhere after this macro = 304.

object id range	owner	artifacts	current status	fold action	collision risk	apply now?
263..272	T2	NVSZ evidence-escrow planning (inventory/reqs/model/decision/probes/recon/validator/checkpoint/current-state/gov)	PROPOSED, KB-births only	register in registry md/json + 1 index pointer	none (Codex-confirmed vs 273..288)	NO
289..304	T2	this macro (dry-run packet 289..296 + reports 297..299 + fold pkg 300..301 + checkpoint 302 + current-state 303 + gov addendum 304)	PROPOSED, KB-births only	register in registry md/json + 1 index pointer	none (above 288)	NO

2. Exact registry JSON patch proposal (for 263..272)

To be appended to the registry JSON objects array (or carried as an addendum block, matching the established pattern). Each entry:

{ "id": "TKT-OBJ-263", "title": "v0.2 NVSZ evidence inventory", "type": "report",
  "path": "knowledge/dev/laws/tool-kiem-thu/dev/v0.2-hardening/reports/v02-nvsz-evidence-inventory-2026-06-11.md",
  "authority": "NON_AUTHORITY", "may_gate": false, "decision_effect": "NONE", "owner_class": "T2", "rev": 1 }

…through TKT-OBJ-272. Full entries in the JSON twin (TKT-OBJ-301), key registry_json_patch.objects. The patch is additive; it changes no existing object and bumps final_status to note the fold.

3. Registry MD addendum fold proposal

Append one addendum section to governance/tool-kiem-thu-object-registry-2026-06-10.md:

Addendum (fold) — NVSZ evidence-escrow planning, TKT-OBJ-263..272 (T2, 2026-06-11): 10 NON_AUTHORITY objects at the paths in §2/JSON twin. Deconflicted from T1 273..288 (Codex-recheck confirmed). Registry md rev → next; json rev20 → next.

4. 00-index fold proposal

Add one pointer line under the index header boundary (body untouched, per the corruption-avoidance pattern):

• TKT v0.2 NVSZ evidence-escrow planning → TKT_V02_NVSZ_EVIDENCE_ESCROW_PARTIAL_OPERATOR_BLOCKER (2026-06-11, T2): objects TKT-OBJ-263..272; root not designated (V02-PB-NVSZ-1); see current-state/reports/tkt-v02-nvsz-evidence-escrow-planning-2026-06-11.md.

(A second analogous pointer line for 289..304 when this macro's block is also folded.)

5. Collision scan report (summary)

check	result
263..272 vs T1 273..288	no overlap (Codex-confirmed)
289..304 vs T1 273..288	no overlap (strictly above 288)
289..304 vs T2 263..272	no overlap
any id in package already in registry JSON body (≤224)	no
registry JSON rev at scan	20
00-index rev at scan	110

6. Apply procedure (for the authorized actor only — NOT this macro)

1. Confirm T1's lane has landed and owner/GPT authorizes the fold.
2. Re-run the collision scan (§1/§5) against the then-current registry JSON + index revs.
3. Append the §2 JSON entries (263..272, then 289..304) and bump final_status.
4. Append the §3 MD addendum; bump registry md rev.
5. Add the §4 index pointer line(s); bump 00-index rev.
6. Flip blocker V02-NVSZ-GOV-FOLD-1 to CLOSED.

7. Verdict

Fold patch package PREPARED and collision-scanned, covering both the prior NVSZ block (263..272) and this macro's block (289..304). NOT applied — APPLY_NOW=NO while T1 is active and absent explicit owner/GPT authorization. Bookkeeping-only; blocks no engineering, no Codex review.