Reconcile reef bindings and evidence
This commit is contained in:
parent
721398125b
commit
3e98b10d81
15 changed files with 541 additions and 36 deletions
|
|
@ -2,16 +2,18 @@ reef_id: reef-railiance
|
|||
hosted_rails:
|
||||
- rail_id: rail-kubernetes
|
||||
role: primary
|
||||
readiness_state: declared
|
||||
readiness_state: verified
|
||||
contract_version: 1.0.0
|
||||
evidence:
|
||||
- evidence/admission/rail-kubernetes-baseline.json
|
||||
notes: First-wave default execution rail for the grouped Railiance home reef.
|
||||
- evidence/verification/rail-runtime-2026-08-21.json
|
||||
notes: First-wave default execution rail; live verification still records one Ready control-plane and etcd node.
|
||||
- rail_id: rail-knative
|
||||
role: derived
|
||||
readiness_state: declared
|
||||
readiness_state: verified
|
||||
contract_version: 1.0.0
|
||||
base_rail: rail-kubernetes
|
||||
evidence:
|
||||
- evidence/admission/rail-knative-baseline.json
|
||||
notes: Declared second-wave rail; not installed or production-approved.
|
||||
- evidence/verification/rail-runtime-2026-08-21.json
|
||||
notes: Installed and verified for private operation; production approval remains blocked by the single-node failure domain.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue