Prepare State Hub retirement baseline

INTENT.md

@@ -9,6 +9,26 @@ updated: "2026-05-17"
 > This file explains why State Hub exists, where its authority begins and ends,
 > and why it is now separate from the-custodian.
 
+## Retirement status
+
+State Hub is a legacy service in active retirement planning. It remains
+operational during the migration, but it is not the target home for new
+cross-domain capabilities.
+
+The replacement program is coordinated in
+`/home/worsch/prj-state-hub-retirement`, whose `GOAL.md` defines the migration
+and retirement gates. Repository representation, file-backed record indexing,
+consistency reconciliation, and governed repository changes are moving toward
+`/home/worsch/repo-manager`. Cross-domain identity, communication, interaction,
+state projections, telemetry, and domain-extension composition are moving
+toward the consolidated `hub-core` framework.
+
+Until the retirement gates are met, State Hub remains authoritative only where
+the current contracts and repository-backed workflows require it. Changes made
+during this period should preserve compatibility, enable extraction, reduce
+scope, or address operational risk; they should not establish new permanent
+architectural ownership here.
+
 ---
 
 ## Why it exists
@@ -126,4 +146,3 @@ visible rather than fail opaquely when one component is unavailable.
 
 **Narrow authority.** State Hub coordinates and exposes state; it does not make
 irreversible human decisions or become the owner of every adjacent system.
-