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

Add staged deployment lifecycle spec

Browse source
This commit is contained in:
tegwick 2026-06-16 08:01:25 +02:00
parent f30d901758
commit 45e57b0a11
3 changed files with 344 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/RAIL-BS-WP-0006-staged-promotion-lifecycle.md
View file

@ -10,7 +10,7 @@ topic_slug: railiance
repo_goal_id: "6ea441f7-7fe3-4598-922b-38baf20c0580"
state_hub_workstream_id: "cb72d3ba-1863-43c2-a2a5-49ac75fc2603"
created: "2026-02-24"
updated: "2026-05-03"
updated: "2026-06-16"
---
# Staged Promotion Lifecycle
@ -54,7 +54,7 @@ Expected cross-repo handoffs:
```task
id: RAIL-BS-WP-0006-T01
status: todo
status: done
priority: high
state_hub_task_id: "fbfc341f-8ccb-4950-a85d-3e59c4f5b87f"
```
@ -72,6 +72,13 @@ The spec should define:
**Done when:** the lifecycle is clear enough to apply to Forgejo as a later
production workload.
2026-06-16: Added `docs/deployment-lifecycle.md` and linked it from
`docs/README.md`. The specification defines Stage 1 local validation, Stage 2
production canary, Stage 3 production promotion, required checks and evidence,
canary acceptance gates, rollback expectations, human approval gates for
production-critical workloads, and the Forgejo readiness questions that must be
answered before cutover.
---
### T02 - Define railiance directory schema and app.toml contract