Commit graph

2 commits

Author SHA1 Message Date
fd7046c7fe 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-.
2026-08-15 20:52:04 +02:00
59389f52eb 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>
2026-08-11 23:19:04 +02:00