coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Close forge rescope task

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-05 15:43:14 +02:00
parent 27b4f3ca0d
commit 0eb90b1308
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md
View File

@@ -167,7 +167,7 @@ decryption, or Kubernetes apply was run.
```task ```task
id: RAILIANCE-WP-0006-T04 id: RAILIANCE-WP-0006-T04
status: todo status: done
priority: high priority: high
state_hub_task_id: "64ac73e7-abe5-47df-abbc-51aed25a7ce4" state_hub_task_id: "64ac73e7-abe5-47df-abbc-51aed25a7ce4"
``` ```
@@ -195,9 +195,12 @@ In `railiance-enablement`:
Done when a new operator can answer "is this S4, S5, or forge?" from the scope Done when a new operator can answer "is this S4, S5, or forge?" from the scope
documents without inspecting historical workplans. documents without inspecting historical workplans.
Progress 2026-06-05: `railiance-apps/SCOPE.md` now treats forge as an upstream Completed 2026-06-05: `railiance-apps/SCOPE.md` now treats forge as an upstream
service and keeps only compatibility wrappers. `railiance-enablement` still service and keeps only compatibility wrappers for moved Gitea operations.
needs the S4 handoff wording checked after the deploy move. `railiance-enablement/SCOPE.md` and `railiance-enablement/INTENT.md` now
separate reusable S4 workflow templates and paved paths from forge-owned
runtime, registries, runner substrate, labels, credentials, and artifact
evidence.
--- ---