coulomb/railiance-forge
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

27
INTENT.md
View file

@ -9,7 +9,7 @@
## One-liner
**The forge layer - turning source hosting, registries, and automation runners into dependable Railiance release infrastructure.**
**The forge capability - turning source hosting, registries, and automation runners into dependable Railiance release infrastructure.**
---
@ -113,6 +113,31 @@ build, publish, automate, and consume releases.
---
## Placement
This repository previously described itself as "the forge layer". The OAS Stack
dimension defines five levels (S1-S5) and forge is not one of them, so that
description left it unplaced - which is how layer boundaries erode.
Placement was decided 2026-08-11 (hub decision `d151d817`):
* the **Forgejo workload** becomes `rapp-forgejo`, a managed workload package
* the **layer responsibility** - runner placement and labels, registry
retention, artifact lifecycle, package credentials - folds into **S4
`railiance-enablement`**, which already declares a handoff contract for
exactly these concerns
A retirement hypothesis was tested and rejected: this repo and `helix-forge` are
different lineages, not one maturing into the other. `helix-forge` is
methodological (capability-first ecosystem, OAS dimensions, VSM vocabulary);
this repo is operational. Retiring it would orphan responsibilities nothing
else owns.
Until the migration completes, this repo remains the operating home for forge
concerns. See `railiance-platform/ArchitectureBlueprint.md` section 5.2.
---
## Direction of Evolution
This layer is expected to evolve toward: