---
agent: scope-analyst
last_updated: "2026-06-21"
session_count: 1
---

# scope-analyst memory

## Accumulated Findings

### the-custodian (2026-06-21)
- **Central boundary decision:** the-custodian is the *governance/continuity
  substrate*, NOT the State Hub service. The service (DB/API/MCP/dashboard) lives
  at `/home/worsch/state-hub`; `the-custodian/state-hub/` is only a pointer. Any
  SCOPE that claims state-tracking / SBOM / MCP-tool-registration as this repo's
  own "Provided Capabilities" is conflating the two — the prior SCOPE did exactly
  that. New SCOPE reframes capabilities to governance canon / session protocol /
  append-only memory.
- **Authoritative boundary source:** `INTENT.md` (updated 2026-05-17) has the
  cleanest "What it is not" ownership table — state-hub, activity-core, issue-core,
  repo-scoping, domain repos, human-approval. SCOPE was missing issue-core and
  repo-scoping; now added.
- **Domain count is dynamic, do NOT hard-code.** Live `list_domains()` returned
  14 active on 2026-06-21. Old SCOPE said 6/7 (and was self-contradictory). README
  still says "seven"/"six" — also stale. Treat `list_domains()` as authoritative.
- Prior stale SCOPE archived to `history/20260621-SCOPE.md`.

## Session Log
2026-06-21 · the-custodian · Rebuilt SCOPE.md from repo+INTENT+live domains; archived stale version; fixed state-hub/custodian conflation and domain-count drift.