Record forge placement: workload to rapp-forgejo, layer to S4
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

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>
This commit is contained in:
tegwick 2026-08-11 23:19:04 +02:00
parent 88e24630c2
commit 59389f52eb
3 changed files with 118 additions and 1 deletions

14
WORK-RECORDS.md Normal file
View file

@ -0,0 +1,14 @@
# Work Records — railiance-forge
> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
> stage 3). Do not edit by hand — edit the source file/block listed for
> each record and re-run fix-consistency to refresh this index. Archived
> workplans are omitted; closed decisions/intakes/engagements stay listed
> so recently-resolved work is still visible. [auto]
| Kind | ID | Status | Lane | Source |
| --- | --- | --- | --- | --- |
| workplan | RAILIANCE-WP-0002 | ready | — | workplans/RAILIANCE-WP-0002-forge-resource-economics-evidence.md |
| task | RAILIANCE-WP-0002-T01 | todo | — | workplans/RAILIANCE-WP-0002-forge-resource-economics-evidence.md |
| task | RAILIANCE-WP-0002-T02 | todo | — | workplans/RAILIANCE-WP-0002-forge-resource-economics-evidence.md |
| task | RAILIANCE-WP-0002-T03 | todo | — | workplans/RAILIANCE-WP-0002-forge-resource-economics-evidence.md |