<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

Example (read-only) — v0.2 Pre-Codex Review Packet

Purpose: show a real L0/L1/L2 packet that the base template generalizes. Read-only: this references the governed v0.2 packet; it does not mutate it.

Source

knowledge/dev/laws/tool-kiem-thu/dev/v0.2-hardening/review/v02-pre-codex-review-packet-2026-06-10/ (NON_AUTHORITY / NOT_PROMOTED). Tree pin (post file-completeness repair): packet_tree.sha256 = 08a17307… = sha256(HASH_MANIFEST.txt).

Layout (maps to the template)

Packet file	Template role
README_FOR_OWNER_AND_CODEX.md (0bd3569e…)	README_FOR_REVIEWER.md
commands.sh	gate runner G0..G6
exit_codes.json (83afb142…, byte-exact)	verdict anchor
HASH_MANIFEST.txt / packet_tree.sha256 (08a17307…)	L0 integrity surface + tree pin
content_bind_oracle.py (0c582901…) + content_bind_oracle.json (a331eb6c…)	checker + committed DEV_FIXTURE_STATIC oracle
content_bind_verify.py (3bdee7d2…, rev2)	fail-closed verifier
content_bind_regression.py (afd07c60…)	regression matrix
content_bind_rerun.sh (ff36e176…)	RERUN (DEV/STRICT/V3)
sp_probes.py (04098c6a…)	L2 probe suite (28 probes, 0 fail-open)
real-sut/fix7_canon_v1_ssot.py (d9caa9fe…)	frozen SUT, by-reference byte-identical

What it demonstrates for the base

• L0: the file-completeness repair — 6 manifest-listed files were absent; the fix added the file-presence check (manifest_file_presence_policy.md).
• L1: bash commands.sh → OVERALL_RESULT: PASS; fresh KB reconstruct → shasum -a 256 -c HASH_MANIFEST.txt 10/10 OK; packet_tree matches.
• L2: sp_probes.py → 28/28, any_invalid_exit0=false, any_PASS_emitted_for_invalid=false, any_SEAL_emitted_for_invalid=false; the detector-correctness fix (SEAL substring inside a rejection message) is recorded.
• Verifier exit family: 0 PASS · 2 absent · 3 malformed/authority-claim · 5 content-binding failure · 6 strict-seal-without-content.

Boundary it illustrates (why base ≠ semantic)

The --produce gate binds filename membership, not content (ADOPT-FIND-1 / V02-PB-PRODUCE-CONTENT). Content-binding is a dev profile (G2), and seal is authority-only (G3). The base layer proves G1 + G2 and refuses false G3; it makes no semantic claim.