f3c44c7a80
railiance-platform surveyed the four-axis model against the live cluster and all six family repos and routed the findings here (messages 04c776c4 and f88f938d): rapp.yaml has no schema and has drifted three ways, reef bound_rapps is a stale hand-maintained list, and ~17 live workloads sit against 3 rapps. Takes ownership of the schema, the composition block with its two cardinalities (repos many:many with rapps, deployables 1:1), and a validator over all three family declaration files. Migration stays with the owning repos. T01 done: both messages acknowledged, ownership confirmed to railiance-platform. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| archived | ||
| .gitkeep | ||
| ADHOC-2026-07-30.md | ||
| RAILIANCE-WP-0017-rail-rapp-reef-repo-separation.md | ||
| RAILIANCE-WP-0018-first-wave-repo-family-materialization.md | ||
| RAILIANCE-WP-0019-knative-qonto-runtime-on-reef-railiance.md | ||
| RAILIANCE-WP-0020-openbao-migration-to-reef-railiance.md | ||
| RAILIANCE-WP-0021-rapp-declaration-schema.md | ||