railiance-forge/workplans
tegwick 59389f52eb
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Record forge placement: workload to rapp-forgejo, layer to S4
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
..
archived CUST-WP-0055 T07: add archive workplan terminology grandfather note 2026-07-08 20:26:37 +02:00
RAILIANCE-WP-0002-forge-resource-economics-evidence.md Record forge placement: workload to rapp-forgejo, layer to S4 2026-08-11 23:19:04 +02:00