coulomb/railiance-forge
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Publish Forge resource economics evidence
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
This commit is contained in:
tegwick 2026-08-22 12:34:25 +02:00
parent a0f4c493a3
commit 35dbe4dd42
12 changed files with 632 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/forge-resource-evidence.md Normal file
View file

@ -0,0 +1,18 @@
# 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.