Repository navigation
http-capability-gateway tier-2 production-wiring (ADR-0004) #91
Description
Activity
- added sub-issues
on May 17, 2026 - added a commit that references this issue
on May 18, 2026 - added 4 commits that reference this issue
on May 20, 2026 24 remaining items
- added 10 commits that reference this issue
on Jun 14, 2026 Re-verified 2026-08-27 — the blocker holds, the gap list does not
The blocker is real and unchanged:
boj-server/.machine_readable/contractiles/trust/Trustfile.a2mlline 900 still reads
status: "PENDING — http-capability-gateway wiring forthcoming".But all three "stated gaps" now have in-tree artifacts
gap artifacts found mTLS src/abi/MTLSPolicy.idr,test/mtls_test.exs,docs/mtls-rotation-runbook.adoc, 7 test fixturesE2E e2e_test.exs,e2e_boj_integration_test.exs,e2e_property_test.exs,forged_trust_e2e_test.exsBenchmarks bench/baseline.json,gateway_latency.exs,docs/perf-contract.adoc,docs/RELEASE-CRITERIA.adoc⚠️ Presence is not passing. Nobody has verified these go green — and given the estate-widestartup_failureepidemic (#657), their CI may never have run at all. That is the actual next step, and it is cheap.The "~8–12 weeks" scope no longer describes the work. Recommend: run the suites, then either flip line 900 or re-file against whatever actually fails.
http-capability-gateway tier-2 production-wiring. ADR-0004 is Accepted but not production-wired:
Trustfile.a2mltier-2 =PENDING; stated gaps = mTLS-as-primary path, E2E verification, benchmark evidence (~8–12 wks per the ADR). This is the real blocker for a governed public surface — until it lands the unified core stays internal/loopback and consumer K9 gates stay red (tracked, not masked). Tracks the existing ADR-0004 + audit; does NOT duplicate them.