Checkable FIX7 Blueprint Package — claim/artifact/command inventory

• Date: 2026-06-10 · Macro: Tool-Kiem-Thu → FIX7 support (blueprint checkability)
• Target ("bản vẽ thi công"): T1 FIX7 Existing-System Refactor Execution Blueprint — KB folder knowledge/dev/reports/architecture/t1-fix7-existing-system-refactor-execution-blueprint-2026-06-08/ (14 docs, all .md; rev: 00=49, 06=70, 07=55, 12=64, canonicalizer=1) + its latest review Codex Recheck 8 (FIX7_REFACTOR_BLUEPRINT_CODEX_RECHECK_8_NEEDS_T1_FIX).
• Authority of THIS doc: provisional-non-authority, DERIVED VIEW. It does NOT canonicalize, seal, approve, or override the blueprint. The blueprint's SSOT remains the FIX7-CANON-V1 canonicalizer; the sealing authority remains Codex. This package exists only to make the blueprint checkable by the offline Article-14 inspector — it must never become a second canonical/duplicate authority (which would itself trip Lens 4). Object ID: TKT-OBJ-042.
• Source rule: KB-FIRST/PG-FIRST/LOCAL-LAST. Article 13 + 14 in force. Non-gating: decision_effect=NONE, may_gate=false.

1. What "checkable form" means here

The blueprint is converted into the inspector's claim-inventory shape (the FIX7 read/report pilot adequacy chain): every load-bearing assertion is extracted as a CLAIM with claim_type → required_evidence_class → declared_evidence → actual_evidence(read-only) → adequacy → verdict → lens. No verdict is "green"; the ceiling is READ_LEVEL_ACCEPTABLE/FAIL/NEEDS_FIX/BLOCKED/UNVERIFIED, fail-closed to execution-class. Counts/hashes are quoted verbatim, never normative.

2. Declared ARTIFACTS (inputs to the check)

AID	Declared artifact	Declared type	Blueprint claim	Actual (read-only, first-hand)
A1	canonicalizer-fix7-canon-v1-ssot.py	.py executable, "the ONE load-bearing canonical contract (Art.14/NT14)"	runs; --selftest exits 0	ABSENT. list_documents of the blueprint folder returns 14 docs, ALL .md; no .py.
A2	canonicalizer-fix7-canon-v1-ssot.md	.md w/ python fence + prose	pinned by canonicalizer_sha256; canonicalizer_path → the .md	EXISTS (rev1). No byte-exact extraction rule materializes the fence into A1.
A3	8 seal digests: active_corpus_sha256, marker_fence_registry_sha256, superseded_boundary_sha256, guard_set_sha256, envelope_manifest_sha256, detached_seal_sha256, membership, canonicalizer_sha256	computed outputs	all produced by the SSOT	only membership = f2bda8effc7be19b54722828126b82d7d2d48bee5e5e5dc0c8f347ce210fe251 reproducible; other 7 blocked (no extractor/encoder/seal code).
A4	ACTIVE_AUTHORITY_APPROVAL_ENVELOPE / doc-00 manifest	manifest	sealed before PKG-A may begin	builder/closed-roster validator absent; envelope_manifest_sha256 blocked.

3. Load-bearing CLAIMS (the checkable inventory)

CID	Claim (blueprint asserts)	claim_type	required_evidence_class	declared_evidence	actual_evidence (read-only)	verdict	Lens	Recheck-8 check
C-01	An executable canonicalizer SSOT exists and runs at …ssot.py	EXECUTION + ARTIFACT_EXISTENCE	runnable artifact + real run output	"implementation runs that artifact"	A1 absent; python3 …ssot.py --selftest → [Errno 2] exit 2	FAIL	L1 missing-artifact + L3 non-runnable	B CANONICALIZER_SSOT_FAIL
C-02	--selftest = 22/22 PASS, exit 0, reproduces f2bda8…fe251	EXECUTION	complete real pasted output of the declared command	"22/22 PASS (run by T1 this pass)"	unverifiable (file absent); 22 = narrow unit asserts, not production seal path; only membership independently confirmable	FAIL (fake/unverified selftest)	L2 fake-selftest	B / F
C-03	Exactly one canonical authority; all other prose is NON_AUTHORITY_EXPLANATION	AUTHORITY_UNIQUENESS	runnable duplicate-authority inventory over ACTIVE_AUTHORITY	banners + G-NO-DUPLICATE-CANONICAL-AUTHORITY	guard asserted, not executed; incomplete SSOT forces implementers to consult demoted prose ⇒ prose stays effective authority ⇒ structural duplicate authority recreated	NEEDS_FIX	L4 duplicate-authority	C NEEDS_FIX
C-04	Marker/scope contract enforced (kinds/literals + fences + boundary "current-authority-only")	SCOPE_ENFORCEMENT	executable whole-doc extractor + duplicate/fence/overlap tests + boundary scoping	unit-level check_marker() + closed status set	unit kind/literal OK; whole-doc extractor, duplicate-marker, fence balance/nesting/overlap, boundary scoping not executable	NEEDS_FIX	L5 forbidden-scope	E NEEDS_FIX
C-05	The 8 aggregate seal digests are produced	OUTPUT_PRODUCTION	the produced digest values	"Invocation contract" output list	7/8 not produced (membership only)	FAIL	L1 missing-output + L3	F / G BLOCKED
C-06	Detached seal is integrity-protected	INTEGRITY	independent signature or revision-bound anchor	hash stored beside seal content	only a recomputed hash beside mutable content; no independent signature/pinned revision	NEEDS_FIX	L4-adjacent (mutable authority)	A-residual / H / I
C-07	No new hardcode; PG-native preserved	NON_REGRESSION	scan results	guard scans	no NEW runtime hardcode, no PG regression — but incomplete SSOT = disguised fixed behavior (derive from prose)	NEEDS_FIX (construction-authority only)	L4/L5 adjacent	H / I NEEDS_FIX

4. Adequacy summary (no fake-green)

• ACCEPTED at blueprint level (from Recheck-8, not re-adjudicated here): A revision anchor, D document_id-MCP, J invariants/boundary.
• FAIL: C-01, C-02, C-05 (→ checks B, F; G blocked).
• NEEDS_FIX: C-03, C-04, C-06, C-07 (→ checks C, E, H, I, K).
• The whole failure chain is single-rooted: A1 (the runnable .py) does not exist ⇒ no production seal path ⇒ B-FAIL → F-FAIL → G-BLOCKED, with C/E/K as downstream consequences.

5. How this package is consumed

• Input to fix7-blueprint-article14-executable-evidence-check-report-2026-06-10.md (the 5-lens check) and to the approval punch-list.
• Re-derivable: any future blueprint revision re-runs this extraction; the package is a view, regenerated, never a stored authority.

Verdict

CHECKABLE_PACKAGE_BUILT — 4 declared artifacts + 7 load-bearing claims extracted into the inspector adequacy shape, each bound to read-only evidence and a detector lens; provisional-non-authority, non-gating, does not override Codex Recheck-8.