docs: accept repository classification boundary

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0230c-b06c-7641-808a-e191b6d1da49

INTENT.md

@@ -2,8 +2,8 @@
 
 **Project:** `hub-core`  
 **Domain:** `infotech`  
-**Status:** Active — surviving hub framework and runtime (`HUB-WP-0004`)
-**Updated:** 2026-08-21
+**Status:** Active — production hub framework and runtime
+**Updated:** 2026-08-22
 
 ---
 
@@ -24,7 +24,7 @@ three-repo hub stack:
 | --- | --- |
 | `hub-core` | Shared Python package plus target framework/runtime — this repo |
 | `state-hub` | Legacy coordination host; capabilities move or retire incrementally |
-| `core-hub` | Current `/api/v2` runtime; routes are absorbed, then the repo is archived |
+| `core-hub` | Previous `/api/v2` runtime; retained temporarily as rollback before archive |
 
 Canon: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
 
@@ -109,6 +109,7 @@ models where extended, and workflow callbacks.
 | Concern | Owner |
 |---|---|
 | Repository-owned workplans, tasks, decisions, and consistency | `repo-manager` over Git authority |
+| Repository classification validation and repository projection | `repo-manager` over `.repo-classification.yaml` authority |
 | Domain-specific business data and APIs | Domain hubs and specialized services |
 | Custodian canon, constitution, domain charters | `the-custodian` |
 | Event-triggered maintenance task creation | `activity-core` |
@@ -127,7 +128,7 @@ acceptance flows) stay in the host hub.
 | Consumer | Relationship |
 |---|---|
 | `state-hub` | Compatibility source during incremental capability cutover |
-| `core-hub` | `/api/v2` route/runtime source to absorb before archival |
+| `core-hub` | Rollback source during stabilization; archive after CORE-WP-0010 closes |
 | `ops-hub`, `fin-hub`, future hubs | Domain/aspect extensions using versioned hub-core ports and manifests |
 
 Extraction boundary and migration status:
@@ -145,6 +146,7 @@ Extraction boundary and migration status:
 - the surviving runtime exposes versioned `helixforge.hub-extension` ports and projections
 - schema changes to shared primitives are versioned through hub-core migrations, not ad hoc forks
 - repository work authority and domain-specific business models never migrate into hub-core
+- cross-domain navigation is rebuilt from versioned owner projections with provenance
 
 ---