railiance-forge/docs/forge-resource-evidence.md
tegwick 35dbe4dd42
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Publish Forge resource economics evidence
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
2026-08-22 12:34:25 +02:00

18 lines
1,000 B
Markdown

# Forge resource evidence
Run `make forge-observe REMOTE=railiance01` to capture a timestamped,
non-secret observation for `resource:railiance:forgejo`. The collector reads
Kubernetes deployment, metrics, PVC, CNPG, backup-resource, and aggregate
`du` surfaces. It does not read repositories, packages, Secrets, or pod
environments.
The observation separates requested/limited compute from observed usage,
records storage and recovery posture, and preserves unavailable dimensions as
measurement gaps. The companion YAML files define service/labor assumptions
and candidate allocation drivers. Unknown targets, labor, consumer
attribution, and booked cost stay unknown; `resource-control` owns allocation
method selection and `fin-hub` owns financial reconciliation.
The current capture also makes the recovery gap explicit: CNPG reports
continuous archiving, but no `Backup` or `ScheduledBackup` resource exists for
`forgejo-db`, and shared-storage/runner restore drills have not been evidenced.