{
  "schema": "cain42.sovereign.evo01.release_gate.v1",
  "generated": "2026-10-12",
  "source_revision_start": "6cfa3b9e465a35b846311e53503aae509fd457d7",
  "source_revision_tested": "code at 3eff02c2; deployed with bf225092 (tag deploy/20261012T034805Z, provenance 9eab7550)",
  "deployment": "DEPLOYED by session -17 with owner approval: tag deploy/20261012T034805Z at bf225092 includes c0b6a64b and 3eff02c2. -46 confirmed read-only: blue :8088 (started 03:47:28Z) and green :8098 (started 03:46:35Z) both started after 3eff02c2 (03:43:09Z), on-disk files equal bf225092, both run pipeline v27 with strict mode off. The containment change was NOT probed live (it would require quarantining a live agent); its evidence is the regression suite. -17 probed its own fixes on both instances.",
  "gates": [
    {
      "id": "G1",
      "rule": "no forbidden execution state reachable in a required model",
      "result": "FAIL",
      "evidence": "formal/z3_results.json: mcpgate_token_overrides_operator_allowlist (OPEN D-S46-11) = SAT; every other forbidden state UNSAT for FIXED"
    },
    {
      "id": "G2",
      "rule": "no critical authorization regression test fails",
      "result": "PASS",
      "evidence": "1168 passed, 2 xfailed (strict, D-S46-11) across 56 MCPGate/guard/capability/sovereign/continuum files; the 2 failures (test_cain_sentinel_guardian) read a live DEGRADED snapshot and also fail on 6cfa3b9e"
    },
    {
      "id": "G3",
      "rule": "no unresolved mandatory security state grants permission",
      "result": "FAIL",
      "evidence": "T-S46-08 / D-S46-11 (agent token overrides REQUIRE_APPROVAL). T-S17-03 resolved by -17 (9672bdc1, deployed)."
    },
    {
      "id": "G4",
      "rule": "required permits are action-bound and single-use",
      "result": "PARTIAL",
      "evidence": "action-bound and single-use per process (tests + model); replay across blue/green instances or after a failed ledger write is open (T-S46-06)"
    },
    {
      "id": "G5",
      "rule": "no confirmed critical enforcement bypass",
      "result": "FAIL",
      "evidence": "T-S17-05: no kernel-level enforcement on the hosted path; cain_enforce.bpf.c is tracepoint telemetry (BLOCKER, unchanged). D-S17-06 (published overclaim) FIXED for the claim: owner-approved wording correction in IP recalc V33-V45 (9fc79332, 656dac9a); the already-signed 8.1.0/8.2.0 kits keep the old V45 text"
    },
    {
      "id": "G6",
      "rule": "required evidence present and verifiable",
      "result": "PARTIAL",
      "evidence": "this evolution's evidence is hashed in evidence_manifest.json; MCPGate has no durable request-bound decision ledger (T-S17-06); test rows (1133-1150) sit in the live hosted ledger"
    },
    {
      "id": "G7",
      "rule": "tested source revision identifiable",
      "result": "PASS",
      "evidence": "commits listed above; tests run on the shared working tree whose code files were clean at those commits"
    },
    {
      "id": "G8",
      "rule": "mandatory deployment assumptions hold",
      "result": "FAIL",
      "evidence": "green :8098 was down 01:48-03:46Z and is now running (both instances verified by -17 and -46); the authorization suites are still not in CI (.github/workflows/ci.yml)"
    }
  ],
  "local_development_gate": "PASS \u2014 the changed code passes its regression tests and every suite that imports it",
  "production_release_gate": "BLOCKED",
  "verdict": "BLOCKED",
  "why": "One owner decision (D-S46-11 allowlist precedence) and one architecture gap (T-S17-05 no kernel enforcement, owner decision) remain, and the authorization suites are not in CI. A green suite is not production readiness.",
  "not_claimed": [
    "universal L5 containment",
    "Z3 proves LLM or tool behaviour",
    "kernel or hardware isolation",
    "third-party audit"
  ]
}