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

Inherit the forge layer responsibility (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 
Decision d151d817 placed railiance-forge: the Forgejo workload becomes
rapp-forgejo, and the layer responsibility - runner placement and labels,
registry retention, artifact lifecycle, package credentials - folds into S4,
which already declared a handoff contract with forge for exactly those concerns.

Also states plainly what the 2026-08-11 architecture assessment found about this
layer: it is almost entirely aspiration, with a rich Direction of Evolution and
25 commits and no workplans behind it. The gap should be read as open debt
rather than as a description of the present. The forge responsibility is S4's
first concrete owned accountability.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-11 23:19:34 +02:00
parent 146a2c0dd8
commit a2525a404c
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
INTENT.md
View file

@ -108,6 +108,26 @@ This layer is:
* a **promotion handoff** surface between source repos and S5 deployments
* a future **developer portal** and self-service entry point
* a place to codify delivery knowledge into **repeatable automation**
* as of 2026-08-11, the owner of the **forge layer responsibility**: runner
placement and labels, registry retention, artifact lifecycle, and package
credentials
---
## Inherited: the forge layer responsibility
Decision `d151d817` (2026-08-11) placed `railiance-forge`. The Forgejo
**workload** becomes `rapp-forgejo`; the **layer responsibility** folds into S4
— here — because this layer already declared a handoff contract with forge for
runner labels, package credentials, registry endpoints, and artifact evidence.
Owning the contract's other side is the natural resolution.
This is S4's first concrete owned responsibility. That is worth stating plainly:
until now this layer has been almost entirely aspiration — a rich Direction of
Evolution with 25 commits and no workplans behind it. The forge responsibility
gives it something real to be accountable for, and the gap between what this
INTENT promises and what the repo contains should be read as an open debt, not
as a description of the present.
---