KB-1359

Phase 3 FIX7 Read/Report Pilot Execution Report — 2026-06-10

4 min read Revision 1
tool-kiem-thuphase3fix7-pilotarticle-14execution-reportPASS

Phase 3 FIX7 Read/Report Pilot Execution Report

Verdict: PHASE3_FIX7_PILOT_PASS · Date: 2026-06-10 · Run: 27248508492 · Venue: GitHub-hosted ephemeral runner (NOT Mac-local)

The pilot ran through the offline MVP only, inside the B4′ deny-by-default container, on the FIX7 Recheck-8 dossier (Fixture A). It is read/report level: it caught the Article-14 adequacy class without running FIX7, invoking any FS-DOT/IU/detector, recomputing any hash, or claiming global absence. Evidence, not authority.

What it caught (Fixture A = the real FIX7 Recheck-8 dossier shape)

The dossier claims the .py canonicalizer SSOT exists and runs, selftest 22/22 PASS, exit 0, and a reproduced pinned hash — with only a wrong-kind .md offered as evidence. The pilot fired:

Check Per-claim verdict What it means
C1 NOT_EVIDENCED_IN_ALLOWED_SURFACES .py existence not resolvable on a governed-provenance item — scoped, not "does not exist"
C5 INSUFFICIENT_EVIDENCE_FOR_CLAIM a .md was offered for an "executable runs" claim (wrong kind)
C2 ×2 INSUFFICIENT_EVIDENCE_FOR_CLAIM selftest + exit-code claims with no accepted LOG/EXIT_CODE/RUN_LEDGER
C8 INSUFFICIENT_EVIDENCE_FOR_CLAIM hash-match claim with no pinned HASH_EVIDENCE (never recomputed)
C4 READ_LEVEL_FAIL prose asserts "22/22 PASS / exit 0" without resolvable+capable evidence

Net: final_verdict = READ_LEVEL_FAIL, article14_status = NOT_PROVEN_EXECUTION_UNVERIFIED. The .py existence sub-verdict is NOT_EVIDENCED_IN_ALLOWED_SURFACES, not "the .py does not exist." This is exactly the rev4 requirement: it proves "not adequately evidenced via the packet's allowed surfaces," never global absence.

Honesty fields (verbatim from the pilot report.json)

  • catches_article_14_adequacy_class: true
  • proves_execution: false
  • proves_global_absence: false
  • decision_effect: NONE · may_gate: false
  • the non-global denial disclaimer is present verbatim in the report header (test #23).

Prohibitions held (Article 14 / pilot §7)

Did NOT: run the canonicalizer / any command / selftest / detector; recompute any hash; resume or alter any FIX7 document; perform any live KB/PG read; write KB / system_issues / Directus; collapse denominators; join TAC/IU; read a local path as authority; access secrets; open a DB driver. Reads only the governed-provenance packet; writes only the local /out triplet. The fixtures A′/B/C/D (discoverability / stripped / resolvable-insufficient / global-wording-trap) are validated by pytest (#42/#44/#43/#45) — see the matrix binding.

Companion: the real grounded discovery result (cited, not re-run)

Per FIX7 pilot design §3.2 (recorded as a packet-item fact, not re-executed here): FIX7-CANON-V1-CANONICALIZER resolves on KB only to the Markdown SSOT doc; the .py does not resolve on KB and is out of scope of the only governed FS-mirror surface wf_fs_dot_bin_snapshot=/opt/incomex/dot/bin.py existence = NOT_EVIDENCED_IN_ALLOWED_SURFACES. Codex's Recheck-8 "can't open file / exit 2" finding came from running (the deferred run-half); v0.1 is prohibited from making that global-absence claim and instead reports the scoped non-evidenced verdict.

Machine detail: reports/phase3-fix7-read-report-pilot-execution-report-2026-06-10.json. Raw logs: reports/phase3-fix7-read-report-pilot-raw-log-index-2026-06-10.md.

Back to Knowledge Hub knowledge/dev/laws/tool-kiem-thu/reports/phase3-fix7-read-report-pilot-execution-report-2026-06-10.md