Skip to content

integ: land exodus-zone-gate-engine (+464L)#22

Merged
mdheller merged 1 commit into
mainfrom
integ/zone-gate-only
Jul 4, 2026
Merged

integ: land exodus-zone-gate-engine (+464L)#22
mdheller merged 1 commit into
mainfrom
integ/zone-gate-only

Conversation

@mdheller

@mdheller mdheller commented Jul 4, 2026

Copy link
Copy Markdown
Member

Phase 1 integration — clean backlog branch, no conflict. (forensic-sealing branch deferred: GitGuardian FP on a test path .../Mail/secret.eml, not a real secret.)

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).
@mdheller mdheller merged commit 703001d into main Jul 4, 2026
10 checks passed
@mdheller mdheller deleted the integ/zone-gate-only branch July 4, 2026 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant