Add ArchitectureBlueprint.md as the structural backbone

Consolidates what this session established: the four orthogonal repo-family
axes and the separation rule that keeps Forgejo orgs, State Hub domains and
rapp contexts from being derived from each other; the stack levels plus the
concerns that sit beside the stack; the self-evidencing thread and its two
halves (evidence plane, now owned by railiance-telemetry, and the conformance
loop, still unowned); verified repository status including the two superseded
lineages; and the open placement decisions, each naming railiance-master as
the decider rather than settling them here.

Records that the railiance-forge retirement hypothesis was tested and rejected
- it and helix-forge are different lineages, one operational and one
methodological - so forge should be placed, not retired.

Also notes for tooling that the bootstrap/cluster/hosts/infra repos have
unrelated histories but near-identical content, so fleet inventories must
deduplicate by origin URL rather than by directory.

SCOPE.md gains the telemetry emission relationship and a pointer to the
blueprint.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

SCOPE.md

@@ -86,6 +86,12 @@ policy, and lane governance.
 - Upstream dependencies: railiance-cluster (S2) — k3s running, Helm available, smoke tests passing
 - Downstream consumers: railiance-enablement (S4), railiance-apps (S5) — all depend on platform services
 - Often used with: net-kingdom (identity services integration), railiance-cluster (prior layer)
+- Emits to: railiance-telemetry (evidence plane) — S3 services are expected to
+  emit health and readiness through the standard emission contract rather than
+  per-service bespoke integrations
+- Structural backbone: `ArchitectureBlueprint.md` in this repo records the four
+  repo-family axes, the stack, repository status, and the open placement
+  decisions that `railiance-master` owns
 
 ---