KB-7768

FIX7 Executable Artifact Evidence Report (2026-06-10)

4 min read Revision 1

FIX7 Executable Artifact Evidence Report

  • Date: 2026-06-10 · Object ID: TKT-OBJ-054 · provisional-non-authority, evidence-only · Codex: NOT consulted
  • Evidence root (hash-bound): …/packets/fix7-codex-recheck-9-2026-06-10/ (README §3–§7).

1. Artifact existence proof (the recheck-8 L1/L3 root cause)

artifact recheck-8 now sha256
canonicalizer-fix7-canon-v1-ssot.md (SSOT source) EXISTS EXISTS (KB rev1) local copy 8f80f9…
canonicalizer-fix7-canon-v1-ssot.py (declared runnable) ABSENT → exit 2 MATERIALIZED via byte-extraction; runs; exit 0 9355f0… (10550 bytes)
materialize_canonicalizer.py (extraction command) n/a NEW b854d1…
fix7_canon_v1_ssot_extended.py (production-complete) n/a NEW; 36/36 PASS; runnable from KB 196d98…

2. Materialization command (P1) — reproducible

python3 materialize_canonicalizer.py reads the SSOT .md, slices the first ```​python fence, writes the declared .py. Output: extracted_bytes: 10550, py_sha256: 9355f076…. The .md is the single canonical source; the .py is a derived materialization (no duplicate authority). This converts L1/L3 "file absent / exit 2" → "file present / exit 0".

3. Command-execution proof

command cwd exit result
python3 materialize_canonicalizer.py /tmp/fix7-canon 0 wrote .py, py_sha256 9355f0…
python3 canonicalizer-fix7-canon-v1-ssot.py --selftest /tmp/fix7-canon 0 22/22 PASS; membership reproduced
shasum -a 256 membership_input.bin /tmp/fix7-canon 0 f2bda8…fe251 (cross-tool == hashlib)
python3 fix7_canon_v1_ssot_extended.py --selftest /tmp/fix7-canon 0 36/36 PASS
python3 fix7_canon_v1_ssot_extended.py --produce docs … /tmp/fix7-canon 0 membership_frozen_ok: True; 6/8 digests
python3 kb_roundtrip.py --selftest (KB copy) /tmp/fix7-canon 0 36/36 PASS (round-trip integrity)
  • Determinism: selftest stable across 3 runs; --produce run1 == run2 byte-identical.
  • Environment: offline, stdlib python3 3.11.6, macOS; no network/DB.

4. Selftest truthfulness proof

The recheck-8 "22/22" was unverifiable (file absent). Now: 22/22 reproduced with the materialized file AND extended to 36/36 whose new 14 checks execute the production extractor + 11 fail-closed statuses + dup-authority inventory — i.e. they cover the production seal path L2 said the 22 did not. Full pasted output: packet README §3–§4.

5. Honesty caveats

  • canonicalizer_sha256_candidate (8f80f9…) is over the local SSOT .md copy; the authoritative value is over KB MCP bytes at the sealed revision (Codex computes).
  • The 10 input docs are byte-exact MCP fetches (char counts verified == KB content_length); their per-doc N1 hashes are real candidates.

Verdict

EXECUTABLE_ARTIFACT_EVIDENCE_BOUND — the absent-.py root cause is fixed with a reproducible materialization + run; every command has cwd/exit/output/hash; selftest truthfulness demonstrated (36/36 over the production path); KB round-trip confirms the artifact runs from KB.

Back to Knowledge Hub knowledge/dev/laws/tool-kiem-thu/reports/fix7-executable-artifact-evidence-report-2026-06-10.md