chore: align forge economics workplan and adopt FORGE-WP- prefix
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Has been cancelled

Measure live Gitea-compatible forge. Keep historical RAILIANCE-WP-0002
id. New workplans use FORGE-WP-.
This commit is contained in:
tegwick 2026-08-15 20:52:04 +02:00
parent 59389f52eb
commit fd7046c7fe
2 changed files with 22 additions and 6 deletions

View file

@ -7,7 +7,7 @@
**Domain:** financials
**Repo slug:** railiance-forge
**Topic ID:** `ca369340-a64e-442e-98f1-a4fa7dc74a38`
**Workplan prefix:** `RAILIANCE-WP-`
**Workplan prefix:** `FORGE-WP-`
---
@ -169,10 +169,10 @@ get wrong.
Work items originate as files in this repo — not in the hub. The hub is a
read/cache/index layer that rebuilds from files.
**File location:** `workplans/RAILIANCE-WP-NNNN-<slug>.md`
**File location:** `workplans/FORGE-WP-NNNN-<slug>.md`
**Archived location:** finished workplans may move to
`workplans/archived/YYMMDD-RAILIANCE-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
`workplans/archived/YYMMDD-FORGE-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
the completion/archive date; the frontmatter `id` does not change.
**Ad Hoc Tasks:** small opportunistic fixes discovered during a session use
@ -184,7 +184,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
```yaml
---
id: RAILIANCE-WP-NNNN
id: FORGE-WP-NNNN
type: workplan
title: "..."
domain: financials
@ -208,7 +208,7 @@ derived health labels, not frontmatter statuses.
## Task Title
` ` `task
id: RAILIANCE-WP-NNNN-T01
id: FORGE-WP-NNNN-T01
status: wait | todo | progress | done | cancel
priority: high | medium | low
state_hub_task_id: "<uuid>" # written by fix-consistency — do not edit

View file

@ -8,9 +8,10 @@ status: ready
owner: codex
topic_slug: railiance
created: "2026-08-11"
updated: "2026-08-11"
updated: "2026-08-15"
related:
- RESOURCE-WP-0003
- ADR-0008
state_hub_workstream_id: "72f935a5-d921-48a4-96e4-2365556c7374"
---
@ -23,6 +24,21 @@ 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
```task