6033ae1aef
Publish capacity, recovery, labor, and allocation-driver evidence for resource:railiance:apps-pg so resource-control can forecast and allocate without reading application data or inventing booked cost.
89 lines
2.8 KiB
Markdown
89 lines
2.8 KiB
Markdown
---
|
|
id: RAILIANCE-WP-0016
|
|
type: workplan
|
|
title: "Publish apps-pg resource and recovery evidence"
|
|
domain: financials
|
|
repo: railiance-platform
|
|
status: finished
|
|
owner: codex
|
|
topic_slug: railiance
|
|
created: "2026-08-11"
|
|
updated: "2026-08-14"
|
|
state_hub_workstream_id: "49084fb8-de63-4f32-a4a9-3a42d4e708ac"
|
|
related:
|
|
- 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
|
|
|
|
```task
|
|
id: RAILIANCE-WP-0016-T01
|
|
status: done
|
|
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
|
|
|
|
```task
|
|
id: RAILIANCE-WP-0016-T02
|
|
status: done
|
|
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
|
|
|
|
```task
|
|
id: RAILIANCE-WP-0016-T03
|
|
status: done
|
|
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.
|
|
|
|
## Outcome
|
|
|
|
Published 2026-08-14. Observation
|
|
`docs/evidence/RAILIANCE-WP-0016-apps-pg-observation.json` and narrative
|
|
`docs/evidence/RAILIANCE-WP-0016-apps-pg-resource-evidence.md`.
|
|
|
|
- T01: 1/1 instance, 10Gi local-path, 590 MiB PGDATA, no CPU/memory
|
|
requests, two consumer catalogs (~16.6 MiB), `vergabe_db` unused.
|
|
- T02: no ScheduledBackup, not an Option A target, RPO unbounded, RTO
|
|
undefined — unresolved local-storage risk. Labor: ~6h setup, ~0.5h/month
|
|
recurring, high uncertainty, no EUR.
|
|
- T03: method `apps-pg-dbbytes-v1`, driver `database_gb`, residual
|
|
`platform:apps-pg-overhead` (94.8% of used volume is WAL/catalog).
|
|
|
|
Refresh: `make apps-pg-evidence`. resource-control can now replace the
|
|
illustrative `examples/control-cycle/apps-pg-*.json` fixtures.
|