codex 0d26b5d21b

CI Smoke / host-smoke (push) Successful in 0s

Details

CI Smoke / container-smoke (push) Successful in 1s

Details

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>

2026-08-11 23:09:36 +02:00

2.1 KiB

Raw Blame History

type

title

domain

repo

status

owner

topic_slug

created

updated

state_hub_workstream_id

RAILIANCE-WP-0016

workplan

Publish apps-pg resource and recovery evidence

financials

railiance-platform

ready

codex

railiance

2026-08-11

49084fb8-de63-4f32-a4a9-3a42d4e708ac

RAILIANCE-WP-0003

RESOURCE-WP-0003

RAILIANCE-WP-0016 — apps-pg resource evidence

Goal

Provide platform-owned evidence for resource:railiance:apps-pg: demand, utilization, recovery, operations labor, and consumer allocation. Origin: RESOURCE-WP-0003-T04 delegated evidence gap.

T01 — Publish database capacity and utilization

id: RAILIANCE-WP-0016-T01
status: todo
priority: high
state_hub_task_id: "c772bcea-7ae0-4532-b434-31f75c905431"

Record instance count, CPU/memory requests and observed use, provisioned and used storage, database growth, connections, I/O or other available saturation proxies, and consumer database attribution with timestamps and provenance.

Done when resource-control can forecast database capacity without reading application data or credentials.

T02 — Publish recovery and operational evidence

id: RAILIANCE-WP-0016-T02
status: todo
priority: high
state_hub_task_id: "4eafebd5-0434-42a2-a126-c292c29c1f21"

Record backup coverage, restore-test results, recovery objectives, upgrade and maintenance cadence, incidents, and setup/recurring operator labor. Keep service procedures and execution in railiance-platform.

Done when the portfolio can distinguish verified recovery, unresolved local storage risk, and platform labor cost.

T03 — Define shared database allocation drivers

id: RAILIANCE-WP-0016-T03
status: todo
priority: medium
state_hub_task_id: "fc329443-a2fc-4409-b670-dfb103df2794"

Publish candidate consumer drivers such as database storage GB-month, connections, transactions, or measured I/O. Include shared overhead, unattributed residual, method version, and uncertainty.

Done when resource-control can allocate a referenced apps-pg cost without making railiance-platform a financial ledger.

2.1 KiB Raw Blame History