docs(intent): center workload operations and bound rein-*

State that Railiance organizes workload operations along the four repo
axes, and that glas-harness reins are adjacent rather than a fifth family.
Keep the ADR-0007 coverage fact in SCOPE so intent stays aspirational.

Assistant: grok
Assistant-Session: 01a04c9f-cd6b-7741-bce0-f1d9d1b3c3bc

SCOPE.md

@@ -18,7 +18,10 @@ framework ADRs, declaration schemas, and cross-repo architecture workplans.
 `railiance-master` currently owns the Railiance-specific meaning of the four
 repository axes: ownership repos (`railiance-*`), execution contracts
 (`rail-*`), managed workload packages (`rapp-*`), and substrate boundaries
-(`reef-*`).
+(`reef-*`). **Workload**, in that Railiance-specific sense, is a managed
+running deployable under rapp coverage (`ADR-0007`); human acts, credentials,
+broker actions, and non-deployable infrastructure resources remain outside
+that meaning.
 
 The current implementation includes:
 
@@ -62,6 +65,8 @@ not own every implementation implied by them.
   `reef-*` repository
 - Platform services, application releases, forge runtime, and Fabric graph
   implementation owned by their concrete repositories
+- glas-harness `rein-*` harness contracts and agentic session semantics; a
+  deployed rein is a workload on the four axes, not a fifth Railiance family
 
 ---
 
@@ -98,6 +103,8 @@ publication addressing are completed.
 - Work belongs entirely inside one implementation repository
 - Work is operational execution of an already-settled boundary
 - A workload-specific decision has no framework-wide consequence
+- The request is about glas-harness session, tool, or rein-backend semantics
+  rather than how a deployed rein is packaged, executed, or bound as a workload
 - The request is raw demand that has not yet been reviewed for purpose and scope
   fit