Publish Forge resource economics evidence

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa

SCOPE.md

@@ -3,7 +3,7 @@
 This file defines what `railiance-forge` owns, when to use it, and where its
 boundaries stop.
 
-Last reviewed: 2026-06-13
+Last reviewed: 2026-08-22
 
 ---
 
@@ -113,14 +113,15 @@ The Fabric graph declarations for forge capabilities and edges live in
 
 ## Current State
 
-- Status: active forge extraction.
+- Status: active forge operation with explicit S4 consumer-contract handoff.
 - Implementation: repository contract, registry docs, initial operating
   contracts, deploy-capable Gitea files, and operator targets are present.
 - Stability: emerging but now live-facing; forge owns the reviewed public
   Gitea HTTPS ingress for the web UI, package registry, and OCI registry. Raw
   node IP HTTP access is not part of the supported forge surface.
-- Usage: canonical reference point for forge and registry responsibilities
-  currently transitioning out of `railiance-apps`.
+- Usage: canonical operational reference for forge, registry, runner, retention,
+  recovery, and resource evidence. S4 owns reusable consumer templates; this
+  repo remains their provider and does not duplicate those templates.
 
 Known starting point:
 
@@ -128,8 +129,8 @@ Known starting point:
   ingress, operating contracts, and deploy/status entry points.
 - `railiance-apps` keeps app release ownership and transitional compatibility
   wrappers for old Gitea commands.
-- `railiance-enablement` owns the intent for delivery templates and developer
-  paved paths, but not forge runtime operation.
+- `railiance-enablement` owns delivery templates and developer paved paths,
+  but not forge runtime, registry, runner, retention, or recovery operation.
 - `railiance-forge` should absorb forge runtime and artifact infrastructure
   without moving S5 app release ownership.