<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

TKT Base — Validation & Probes Report

Macro: TKT_BASE_STRUCTURAL_EVIDENCE_GOVERNANCE_PACKAGING_MACRO_2026_06_11 Status contribution: Workstream C. Authority: NON_AUTHORITY / NOT_PROMOTED. Date: 2026-06-11 · Host lane: T2

Every load-bearing claim below carries: governed file · command · cwd · expected exit · actual exit · hash · verdict.

---

1. Base validation harness — 10 fail-closed probes + 4 controls

• File: harness/tkt_base_harness.py sha256=8e3d7d9baec009e562f7c5230c938e8b2f513dcb97e011c0f7a33bce837a8a4c
• Command: python3 harness/tkt_base_harness.py
• cwd: …/tkt-base-structural-evidence-governance-pack-2026-06-11/
• Expected exit: 0 · Actual exit: 0 · Verdict: PASS

Probe	Invalid input	Expected	Actual exit	Token emitted	Verdict
P1 missing load-bearing file	manifest lists absent file	FAIL	5	no	FAIL_CLOSED
P2 stale hash	content mutated, old hash kept	FAIL	5	no	FAIL_CLOSED
P3 duplicate manifest path	path listed twice	FAIL	3	no	FAIL_CLOSED
P4 unlisted file	governed file not in manifest	FAIL	5	no	FAIL_CLOSED
P5 report-PASS-but-evidence-absent	report PASS, evidence missing	FAIL	5	no	FAIL_CLOSED
P6 invalid-emits-certificate	invalid input asks for cert	FAIL	3	no	FAIL_CLOSED
P7 duplicate object ID	sample registry dup id	FAIL	3	no	FAIL_CLOSED
P8 raw-evidence-no-hash/pointer/regen	record missing pointer.hash	FAIL	3	no	FAIL_CLOSED
P9 NVSZ root invented	designated_by=agent	FAIL	9	no	FAIL_CLOSED
P10 semantic-PASS-without-IU	SEMANTIC_TEXT_AS_CODE_PASS, no IU	FAIL	3	no	FAIL_CLOSED
C0 manifest clean	valid packet	PASS	0	PASS (no seal)	PASS
C1 evidence clean	valid local record	PASS	0	no seal	PASS
C2 object ids clean	ids 326..328 > 325	PASS	0	no seal	PASS
C3 verdict in scope	L3 verdict, no overclaim	PASS	0	no seal	PASS

Aggregate: probes_fail_closed=10/10, controls_pass=4/4, any_fail_open=false, any_PASS_emitted_for_invalid=false, any_SEAL_emitted_for_invalid=false, OVERALL: PASS.

Detector-correctness rule exercised

P10's rejection message contains the substring SEMANTIC_TEXT_AS_CODE_PASS (which contains PASS), but the process exits 3 → token_emitted=false. The harness correctly counts this as FAIL_CLOSED, not FAIL_OPEN — reproducing the exact v0.2 gotcha (a *_REJECTED message must not be mistaken for an emitted token).

2. Pack self-verification gates (the pack is itself a TKT packet)

• Command: bash commands.sh · cwd: pack root · Expected: 0 · Actual: 0 · OVERALL_RESULT: PASS

Gate	Checks	Expected	Actual
G0_manifest	tree pin + shasum -a 256 -c HASH_MANIFEST.txt	0	0
G1_harness	python3 harness/tkt_base_harness.py	0	0
G2_required_files	28 required pack files present	0	0
G3_overclaim_guard	policy + limitations name the 3 forbidden tokens	0	0

• exit_codes.json sha256=21e03bcbf53f9044312e0c769cd63e32861c7583a00f99df56633b382111f581 — byte-stable across reruns (verified before==after).

3. L0/L1 — file pass + reconstruction

• L0: shasum -a 256 -c HASH_MANIFEST.txt → ALL OK (28/28); tree pin MATCH (packet_tree.sha256 = 6a6137d1… == sha256(HASH_MANIFEST.txt)).
• L1: bash RERUN.sh → RERUN_RESULT: PASS (exit 0). Reconstructs into a fresh mktemp -d, reverifies manifest + tree + gates + harness independent of the working dir.

4. Fresh reconstruction from KB

Recorded in the checkpoint and current-state after publication: the pack is fetched back from KB into a clean /tmp dir and shasum -a 256 -c HASH_MANIFEST.txt + bash commands.sh are re-run. (See checkpoint §"Fresh KB reconstruct".)

5. Scope reality checks

• No FIX7/T1 surface touched · no v0.2 destructive mutation · no production action · no Codex call · no owner ask · no canonical registry/index fold · no NVSZ root designated · no semantic PASS emitted.
• The harness writes only exit codes + local logs; emits no seal, writes no registry/PG/Directus row.

6. Verdict

Workstream C complete: the base validation harness exists, runs, and fails closed 10/10 with 0 fail-open; the pack self-verifies L0/L1/L2; the overclaim guard is executable (P10). TKT_BASE_RESULT: level_reached = L3 for the pack itself.