generated from coulomb/repo-seed
tegwick
f2e042a278
Add persisted Suggestion entities with WSJF ranking, relevance bumps, REST/MCP write surfaces, /suggestions dashboard page, and daily triage digest integration. Document the cluster operating model, archive the completed migration workplan, and seed WARDEN-WP-0012 routing scenarios.
50 lines
1.6 KiB
Markdown
50 lines
1.6 KiB
Markdown
# SCOPE
|
|
|
|
## One-Liner
|
|
|
|
State Hub is the local-first coordination service for repo-anchored workplans,
|
|
tasks, decisions, progress events, repo classification and metadata, MCP
|
|
tooling, and dashboard telemetry.
|
|
|
|
## In Scope
|
|
|
|
- State Hub FastAPI service
|
|
- PostgreSQL schema and Alembic migrations
|
|
- FastMCP server and tool reference
|
|
- Observable dashboard
|
|
- repo registration (classification-driven) and consistency synchronization
|
|
- repo classification spine (14 market domains, `.repo-classification.yaml`)
|
|
- task-flow engine and flow definitions
|
|
- SBOM, contribution, capability, demand-weighted suggestion backlog, TPSC, DoI,
|
|
token, and interface-change tracking
|
|
- State Hub tests, operational docs, policies, prompts, and local infra
|
|
|
|
## Out Of Scope
|
|
|
|
- Custodian canon and constitution content
|
|
- non-State-Hub domain implementation work
|
|
- external publication or legal/financial commitments
|
|
- plaintext secrets
|
|
- generic hub-core extraction unless a dedicated workplan owns it
|
|
- renaming State Hub to Dev Hub unless a dedicated workplan owns it
|
|
|
|
## Extraction Note
|
|
|
|
This repo is the standalone State Hub home. It was extracted under
|
|
`CUST-WP-0043` from:
|
|
|
|
```text
|
|
/home/worsch/the-custodian/state-hub
|
|
```
|
|
|
|
This repository is authoritative for State Hub implementation work. The
|
|
embedded path in `the-custodian` is now a pointer only.
|
|
|
|
## Workplan Convention
|
|
|
|
New State Hub-local workplans use `STATE-WP-####`.
|
|
|
|
Migrated legacy State Hub workplans may temporarily retain `CUST-WP-####`
|
|
identifiers when preserving existing State Hub workstream and task IDs is the
|
|
least confusing path.
|