Executable zone-gate engine (CHK-01..CHK-10) + gate policies#19
Closed
mdheller wants to merge 1 commit into
Closed
Executable zone-gate engine (CHK-01..CHK-10) + gate policies#19mdheller wants to merge 1 commit into
mdheller wants to merge 1 commit into
Conversation
Metadata Standards §7 defined the WNZL promotion gates as a schema with zero policy instances and no enforcement. This makes them executable, fail-closed: - scripts/exodus_gate.py: evaluate_gate() runs a policy's required fields + checks and returns a GateDecision + the CustodyEvent to write (ZonePromotion vs PolicyException; custody_status=IntegrityViolation when CHK-01 fails; auto_promote false whenever human/legal review is outstanding). - examples/gate-policies/: first concrete policies — Landing→Examination, Examination→Integration (the adversarial-evidence gate: counter-explanations CHK-04 + null hypothesis CHK-05 at E3+), Integration→Governed (CHK-06/07 + human+legal review). All validate against schemas/policy-gate.json. - scripts/test_exodus_gate.py: dependency-free CHK matrix; wired into CI. - docs/zone-gate-enforcement.md: check semantics + what remains (TriTRPC BEACON_COMMIT sealing, atom signing, ForensicBundle export command).
Member
Author
|
Closed as superseded (keeper review, 2026-07-05). This branch's content landed on main via #22 ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Phase-0 Metadata Standards schema pack is committed, but §7's WNZL Dirt-to-Diamond promotion gates were schema-only:
policy-gate.jsonreferenced CHK-01..CHK-10, yet there were zero policy instances and no enforcement. This makes the gates executable and fail-closed.What
scripts/exodus_gate.py—evaluate_gate(artifact, policy, ctx)runs a policy's required fields + checks and returns aGateDecisionplus the CustodyEvent to write:ZonePromotionwhen admitted,PolicyExceptionwhen blocked;custody_status = IntegrityViolationwhenever CHK-01 fails (recomputed BLAKE3 ≠ stored) — and fail-closed if bytes weren't recomputed at all;auto_promoteonly when checks pass and no human/legal review is outstanding (Governed/Diamond never auto-promote).examples/gate-policies/— the first concrete gate policies (all validate againstschemas/policy-gate.json):GATE-Landing-Examination-v1(CHK-01/03/09/10 + CHK-08 non-blocking flag)GATE-Examination-Integration-v1— the adversarial-evidence gate: CHK-04 counter-explanations + CHK-05 null hypothesis at E3+GATE-Integration-Governed-v1(CHK-06/07 + human + legal review)scripts/test_exodus_gate.py— dependency-free CHK matrix (each check pass/fail, integrity-violation custody status, non-blocking duplicate flag, review-gated Governed promotion). Wired into CI.docs/zone-gate-enforcement.md— check semantics + traceability.Verification
python3 scripts/test_exodus_gate.pypasses; CLI smoke works; the existingvalidate_phase0_schemas.pystill passes; all 3 policies validate against the JSON-Schema.Still open (unchanged)
TriTRPC
BEACON_COMMITsealing of CustodyEvents, HellGraph atom signing, the working ForensicBundle export command, account-registry population, BSM ingest. The engine emits the CustodyEvent shape; cryptographic sealing is the next dependency.🤖 Generated with Claude Code