generated from coulomb/repo-seed
feat(classification-spine): implement STATE-WP-0065 repo-anchored model
Replace the ad-hoc coordination-domain spine with the Repo Classification Standard: 14 market domains, classification columns on managed_repos, and workplans anchored by repo_id (topic_id optional). - Add Alembic migration d8e9f0a1b2c3 with data backfill and workstream→workplan rename - Add api/classification.py validation and register-from-classification tooling - Expose workplan-first REST/MCP surface with legacy workstream aliases - Add C-24 consistency rule and legacy domain frontmatter mapping - Update dashboard repos page with category/capability/stake filters - Update orientation docs; mark STATE-WP-0065 finished
This commit is contained in:
@@ -20,6 +20,29 @@ Do not use them as a substitute for formal work definition inside the domain rep
|
||||
|
||||
---
|
||||
|
||||
## Workplan terminology (STATE-WP-0065)
|
||||
|
||||
**Preferred terms:** workplan, `workplan_id`, `/workplans/…`
|
||||
|
||||
**Legacy compatibility:** `workstream`, `workstream_id`, `/workstreams/…`, and
|
||||
`create_workstream` / `update_workstream` MCP tools remain available as aliases.
|
||||
They call the same implementation as the workplan-named tools and endpoints.
|
||||
|
||||
| Preferred (workplan) | Legacy alias (workstream) |
|
||||
|---|---|
|
||||
| `create_workplan(repo_id, …)` | `create_workstream(repo_id, …)` |
|
||||
| `update_workplan` / `update_workplan_status` | `update_workstream` / `update_workstream_status` |
|
||||
| `list_workplans` | `list_workstreams` |
|
||||
| `create_workplan_dependency` | `create_dependency` |
|
||||
| `POST /workplans/` | `POST /workstreams/` (deprecated headers) |
|
||||
| `workplan_id` query/body field | `workstream_id` (accepted alias) |
|
||||
|
||||
Repo classification filters: `list_repos_by_classification(category?, domain?,
|
||||
capability_tag?, business_stake?)` and extended `list_domain_repos(...)` query
|
||||
params use `GET /repos/` classification spine fields.
|
||||
|
||||
---
|
||||
|
||||
## MCP/REST Parity and Failure Handling
|
||||
|
||||
The MCP server is a thin stateless HTTP client over the FastAPI service. On
|
||||
@@ -28,6 +51,10 @@ endpoint they wrap:
|
||||
|
||||
| MCP tool | REST endpoint |
|
||||
|---|---|
|
||||
| `create_workplan(...)` | `POST /workplans/` |
|
||||
| `list_workplans(...)` | `GET /workplans/` |
|
||||
| `update_workplan_status(...)` | `PATCH /workplans/{workplan_id}` |
|
||||
| `list_repos_by_classification(...)` | `GET /repos/?category=…` |
|
||||
| `create_workstream(...)` | `POST /workstreams/` |
|
||||
| `create_task(...)` | `POST /tasks/` |
|
||||
| `update_task_status(...)` | `PATCH /tasks/{task_id}` |
|
||||
|
||||
Reference in New Issue
Block a user