<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

FIX7 / TKT v0.2 Object-ID Allocation & Collision Report (2026-06-11)

Host: T1. Authority: NON_AUTHORITY. Registry/Directus mutated: NO (governance addendum only).

Live collision check (method)

Live-read of the governed registry JSON …/governance/tool-kiem-thu-object-registry-2026-06-10.json and the index 00-index.md. Object IDs extracted programmatically (grep -oE "TKT-OBJ-[0-9]+"), max computed numerically, and the registry's own reservation notes read.

Findings

• Highest allocated TKT-OBJ id = 224 (numeric max over all literal ids).
• Numbers 225–399 that a naive regex catches (228, 235, 240, …) are hash fragments / row-counts, e.g. b221f224 (tree), system_issues(224019) — none is a TKT-OBJ-NNN literal. Verified by context inspection.
• Registry states verbatim: "TKT-OBJ-208..216 RESERVED for the T1 FIX7 N-Node clarification lane (deconflict); v0.2 pre-codex-review uses 217..224."

Known lane allocations (from registry + memory)

range	lane
001..121, 148, 172..173	earlier phases / T1+T2
182..200, 208..216	T1 FIX7 (authority-seal + N-node clarification)
201..207, 217..224	T2 v0.2 (self-codex proof + pre-codex review)

Allocation for THIS macro (provably non-colliding)

• Reserved range: TKT-OBJ-225..240 (16 slots) — strictly above the proven ceiling 224. Zero collision risk.

id	object
TKT-OBJ-225	packet root fix7-authority-n-node-tkt-v02-alignment-2026-06-11/
TKT-OBJ-226	n_node_checker.py
TKT-OBJ-227	sp_align_probes.py
TKT-OBJ-228	commands.sh (gate ledger)
TKT-OBJ-229	RERUN.sh
TKT-OBJ-230	manifest.json / HASH_MANIFEST.txt / packet_tree.sha256 / exit_codes.json
TKT-OBJ-231	README_FOR_OWNER_AND_CODEX.md
TKT-OBJ-232	cross-lane governance alignment report
TKT-OBJ-233	this object-id allocation report
TKT-OBJ-234	N-node numbering reconciliation (md + json)
TKT-OBJ-235	N-node checker-probes report
TKT-OBJ-236	Codex rejection defect re-verification report
TKT-OBJ-237	self-Codex adversarial probes report
TKT-OBJ-238	governed-evidence completeness + report-vs-file audit + authority firewall reports
TKT-OBJ-239	checkpoint
TKT-OBJ-240	current-state

Governance handling

To avoid corruption risk on the 60 KB registry JSON, these objects are governed via the allocation addendum …/governance/fix7-tkt-v02-object-allocation-225-240-2026-06-11.md (no-orphan), referenced from 00-index.md. A future low-risk bookkeeping pass may fold them into the master registry JSON/MD. No object ID collision remains.