tegwick
05a71e702f
Retires the shared prefix. Live plans move to the new prefix keeping their running number; finished and archived files keep the old prefix as historical record, per the ADR-007 option 2 migration ruling. Hub UUIDs are unchanged, so reconciliation matches on state_hub_workstream_id rather than filename and will update the slug in place instead of registering duplicates. Assigned in RMGR-WP-0004-T09. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
3.1 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | related | state_hub_workstream_id | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RFORGE-WP-0002 | workplan | Publish Forgejo resource economics evidence | financials | railiance-forge | ready | codex | railiance | 2026-08-11 | 2026-08-15 |
|
72f935a5-d921-48a4-96e4-2365556c7374 |
RFORGE-WP-0002 — Forgejo resource economics evidence
Goal
Provide the workload-owned demand, utilization, operations, and allocation
evidence for resource:railiance:forgejo, which supplies source and package
infrastructure to Helix Forge and the wider federation. Origin:
RESOURCE-WP-0003-T04 delegated evidence gap.
Measure the live Gitea-compatible Helm workload
(deployment/forgejo-gitea on reef-railiance). Forgejo is the
migration target, not a second live product. Keep the resource id
resource:railiance:forgejo.
This id uses the historical RAILIANCE-WP- prefix (collides with other
ownership repos). New forge workplans use FORGE-WP-. Do not change
this file's id or hub UUID.
Do not add a public metrics or economics endpoint (ADR-0008). Collect
in-cluster or via the operator tunnel. Existing public Forgejo HTTPS is
a separate granted surface, not this plan. Do not treat
environment: production in resource-control as ADR-0006
production-approved.
T01 — Measure Forgejo demand and utilization
id: RFORGE-WP-0002-T01
status: todo
priority: high
state_hub_task_id: "7048e354-0844-4f6c-aeaa-acf188b04ce2"
Record resource requests/limits and observed CPU/memory, repository and package storage use/growth, database storage, runner capacity/activity, backup volume, and material network traffic using stable units and timestamps.
Done when resource-control can forecast capacity and identify saturation or idle capacity without accessing repository content or credentials.
T02 — Declare service objectives and operations labor
id: RFORGE-WP-0002-T02
status: todo
priority: high
state_hub_task_id: "643c2393-2ee5-4264-972c-04c3b358dc86"
Record availability, recovery, retention, and performance requirements plus setup and recurring operator activities. Separate forge, registry, runner, database, backup, upgrade, and incident labor where evidence permits.
Done when total-cost and optimization cases can preserve the forge's service constraints and labor assumptions.
T03 — Publish shared-consumer allocation evidence
id: RFORGE-WP-0002-T03
status: todo
priority: medium
state_hub_task_id: "498cc0c7-ba07-4e7f-a0ef-2e6b34bef04c"
Define explainable candidate drivers for source, package, and runner use across Helix Forge, Coulomb, Railiance, and future tenants. Preserve shared overhead and unattributed residuals; do not implement customer billing.
Done when a versioned driver report can feed resource-control allocation without making the forge repository authoritative for booked cost.
Acceptance
- Demand and utilization include storage, compute, runner, and backup axes.
- Service objectives and labor assumptions are explicit.
- Shared allocation evidence exposes residuals and provenance.