Skip to content

Commit 66cc7d8

Browse files
committed
Document cleanup proof hardening
1 parent da4f70f commit 66cc7d8

3 files changed

Lines changed: 12 additions & 1 deletion

File tree

README.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,9 @@ The current harness covers:
6868
restart-claim fields
6969
- GEPA, TRINITY, cost/budget, and adaptive-control prior-fabric proofs
7070
- fugu single-node readiness handoff for the distributed `nshkr_v2` proof plan
71+
- cleanup hardening for strict Context ABI hashes, raw-payload rejection,
72+
model class-to-profile routing, GEPA optimizer boundaries, authority
73+
evidence verification, and proof artifact ledger posture
7174
- AITrace-backed receipt collection and release-proof mapping
7275

7376
This makes StackLab the answer to "does the stack claim have executable proof?"

docs/gn_ten_proof_matrix.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,10 @@ path, and run GitHub or Linear live commands by prefixing them with
138138
proof from admitted Context ABI packet through
139139
`Trinity.MezzanineRouterAdapter`, Mezzanine render handoff, Jido fake model
140140
invocation, AITrace bounded route/model/eval facts, AppKit projections, and
141-
StackLab context/router/coordination/model scanner receipts.
141+
StackLab context/router/coordination/model scanner receipts. Automation
142+
should precompile `examples/nshkr_router_fabric_roundtrip` before redirecting
143+
`--json` output so Mix dependency compilation logs cannot pollute the JSON
144+
receipt.
142145
- `fugu_single_node_readiness_handoff`: records the Phase 16 single-node
143146
provider-free handoff receipt that unblocks the `../nshkr_v2` distributed
144147
StackLab checklist. It names Context ABI, router fabric, and Extravaganza

guides/context_abi.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,11 @@ A green context proof records packet hash, authority ref, render refs, trace
2121
ref, redaction posture, and no-bypass scanner results. Monolith and distributed
2222
proofs compare semantic receipt fields, not placement or timing facts.
2323

24+
Scanner fixtures reject malformed packet hashes such as non-hex
25+
`sha256:...` values and any raw prompt/memory/provider payload leakage. The
26+
hash evidence is expected to come from owner canonical encoding rather than
27+
from ad hoc `inspect/1`, JSON, or Erlang term binary output.
28+
2429
## Local QC
2530

2631
```bash

0 commit comments

Comments
 (0)