tegwick
59389f52eb
This repo described itself as 'the forge layer' while the OAS Stack dimension defines five levels and forge is not one, leaving it unplaced. Placement decided 2026-08-11 (d151d817): the Forgejo workload becomes rapp-forgejo; the layer responsibility - runner placement, registry retention, artifact lifecycle, package credentials - folds into S4 railiance-enablement, which already declares the handoff contract. Notes that the retirement hypothesis was tested and rejected: this repo and helix-forge are different lineages, operational versus methodological. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
78 lines
2.4 KiB
Markdown
78 lines
2.4 KiB
Markdown
---
|
|
id: RAILIANCE-WP-0002
|
|
type: workplan
|
|
title: "Publish Forgejo resource economics evidence"
|
|
domain: financials
|
|
repo: railiance-forge
|
|
status: ready
|
|
owner: codex
|
|
topic_slug: railiance
|
|
created: "2026-08-11"
|
|
updated: "2026-08-11"
|
|
related:
|
|
- RESOURCE-WP-0003
|
|
state_hub_workstream_id: "72f935a5-d921-48a4-96e4-2365556c7374"
|
|
---
|
|
|
|
# RAILIANCE-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.
|
|
|
|
## T01 — Measure Forgejo demand and utilization
|
|
|
|
```task
|
|
id: RAILIANCE-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
|
|
|
|
```task
|
|
id: RAILIANCE-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
|
|
|
|
```task
|
|
id: RAILIANCE-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.
|