# Custodian Brief — repo-registry **Domain:** capabilities **Last synced:** 2026-04-30 14:36 UTC **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)* ## Active Workstreams ### Rename to repo-scoping and Full Custodian Integration Progress: 0/6 done | workstream_id: `9daccfee-bcfc-49c5-bf68-36ea8c205a09` **Open tasks:** - · T01: Rename the Gitea repository `55341e24` - · T02: Update state-hub registration and repo path `8a803b12` - · T03: Update all references in the-custodian `4b630593` - · T04: Run first full ecosystem SCOPE.md refresh `3f25317f` - · T05: Validate full DoI C5 pass and run consistency sync `860bbc02` - · T06: Update SCOPE.md for repo-scoping itself `1f5ecca9` ### SCOPE.md Generation Feature Progress: 1/5 done | workstream_id: `5da7ddd9-b192-4271-ba86-c5365405a685` **Open tasks:** - ► T02: Build SCOPE.md generator `39feb7ea` - · T03: Build SCOPE.md validator and differ `0c9c1347` - · T04: API endpoints `a2d1937b` - · T05: Register capabilities in custodian `e1bd4a4f` --- ## MCP Orientation (when available) If the state-hub MCP server is reachable, call: `get_domain_summary("capabilities")` This provides richer cross-domain context. If the MCP call fails, use this file as your orientation source.