coulomb/railiance-master
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-master/docs/adr/ADR-0006-reef-production-admission.md
codex b3e9980321 feat: accept ADR-0008 private-by-default exposure (WP-0023 T01) 
Operator ratified the recommended table. Record the sibling ADR,
point ADR-0006 at it, and open T02.
2026-08-15 19:50:46 +02:00

1.3 KiB
Raw Blame History

ADR-0006: Reef Production Admission

Date: 2026-07-26 Status: Accepted

Context

Fabric topology can say that a reef hosts a rail or binds a workload, but that does not demonstrate capacity, isolation, recoverability, or approval for a critical internet-facing service.

Decision

Rail and rapp bindings use explicit readiness states: declared, installed, verified, production-approved, and deprecated.

Critical workloads require machine-readable conformance evidence plus explicit acceptance of residual risks that cannot be automated. Mixed-rail reefs use defined split triggers.

The detailed contract is docs/reef-production-readiness-contract.md.

Who may reach a listener is a different axis: ADR-0008. Production admission does not imply a public surface. A public surface requires this admission and an exposure grant.

Consequences

  • hosts_rail and binds_rapp no longer imply deployability.
  • reef-railiance may host Knative in wave 2, but Qonto cannot be called production-approved solely from that declaration.
  • Repeated evidence collection should become functional automation.
  • production-approved is not permission to publish a listener. See ADR-0008.