Establish all six OAS dimensions as a working model
Populates each canonical dimension with Railiance's actual position, canon's sub-levels, owners where they exist, and honest status. Findings from doing it: - Q1 Security and Compliance is already implemented in S3 to a mature standard (approval gates, delegated apply, revocation, front-door readiness) and was never named as a dimension. Evidence the dimensions describe real structure rather than impose vocabulary. - Plane is operated in full and declared nowhere. P1 workload, P2 control (ArgoCD, CNPG, ESO, cert-manager), P3 management (State Hub, master, workplans). Likely to clarify the rail/rapp relationship, since a rail is essentially a P1 contract. - Intelligence is already referenced in practice - qonto-assistant cites an I1 isolation profile - and the whole agent operating model is I4-I5. Leaving it unmodelled understates what this fleet actually is. - Q3 Operability and Q7 Governance remain unowned; Q5 unaddressed. Adds a recommended establishing order for railiance-master to ratify: Quality first (most unowned concerns), Plane second (cheap, descriptive), Capability third (blocked on the C1 attribution drift), Intelligence fourth, Logic last or never if Helix Forge owns functional decomposition. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
cbc961ca09
commit
0d26b5d21b
2 changed files with 85 additions and 7 deletions
|
|
@ -9,10 +9,10 @@ owner: codex
|
|||
topic_slug: railiance
|
||||
created: "2026-08-11"
|
||||
updated: "2026-08-11"
|
||||
state_hub_workstream_id: "49084fb8-de63-4f32-a4a9-3a42d4e708ac"
|
||||
related:
|
||||
- RAILIANCE-WP-0003
|
||||
- RESOURCE-WP-0003
|
||||
state_hub_workstream_id: "49084fb8-de63-4f32-a4a9-3a42d4e708ac"
|
||||
---
|
||||
|
||||
# RAILIANCE-WP-0016 — apps-pg resource evidence
|
||||
|
|
@ -70,9 +70,3 @@ unattributed residual, method version, and uncertainty.
|
|||
|
||||
Done when resource-control can allocate a referenced apps-pg cost without
|
||||
making railiance-platform a financial ledger.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- [ ] Capacity and utilization evidence is consumer-aware and non-secret.
|
||||
- [ ] Recovery and labor evidence is timestamped and verifiable.
|
||||
- [ ] Shared allocation drivers reconcile with explicit residuals.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue