From ebf82e50ffdb2bd31a59cf817ca365730678e20a Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 5 Jun 2026 17:10:32 +0200 Subject: [PATCH] Close forge fabric task --- .../RAILIANCE-WP-0006-railiance-forge-extraction.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md b/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md index 9b04c58..42684d2 100644 --- a/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md +++ b/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md @@ -343,7 +343,7 @@ and a possible future observability repo. ```task id: RAILIANCE-WP-0006-T09 -status: todo +status: done priority: medium state_hub_task_id: "fd231acc-fe55-417f-a27b-797e1f520e1d" ``` @@ -369,6 +369,16 @@ Declare dependencies such as: Done when State Hub or local Fabric tooling can show the new forge layer's provider and consumer edges without relying only on prose docs. +Completed 2026-06-05: `railiance-fabric` now declares the forge layer as a +graph contract with source hosting, Git SSH, OCI registry, Python package +registry, workflow runner substrate, and artifact promotion evidence +capabilities. It also declares forge dependencies on Railiance Kubernetes, +CNPG PostgreSQL, OpenBao runtime secrets, and planned object storage, plus S5 +and S4 consumer edges from `railiance-apps` and `railiance-enablement` to forge +capabilities. The S4 template relationship is modeled as enablement consuming +forge runner substrate, not forge depending on templates, to avoid a false +cycle. Validation passed with `0 error(s), 0 warning(s)`. + --- ## T10 - Decommission compatibility pointers after migration