tegwick
fb363b37d3
History is archived fleet-side, so the read surface has no remaining job. - api/routers/suggestions.py: whole prefix 410s with a pointer to intake and to the archive; the router drops from 176 lines to a stub - mcp_server: the 6 suggestion tools removed outright rather than stubbed -- a retired tool that still appears in the tool list costs every agent session context on every call, which is the opposite of retiring it - write_idempotency: 5 /suggestions rules dropped - dashboard: suggestions.md deleted, nav entry removed, reference.md and wsjf-triage.md updated; docs/suggestions.md rewritten as archive pointer - tests: two tests pinned the old read-live behaviour and now pin the retirement contract instead Tables stay: they are retire/archive in SHR-INV-0001 and are captured by the final dump at T06. Untouched, and worth knowing during cutover: ui-feedback.md / todo.md 'suggestions' are Shift+click dashboard feedback backed by technical_debt, a different entity that shares the word. E3 (dashboard-meta) is that page; its owner is state-hub-until-cutover so it retires at the T06 window, not now. Full suite 612 passed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.4 KiB
| title |
|---|
| Suggestions (archived) — Reference |
Suggestions (archived) — Reference
The suggestion entity is retired. It predates the fleet work-record
model. Gated needs, findings, and unvetted sparks are recorded as intake
work records (kind: intake).
| Use | Path |
|---|---|
| Current | Intakes · POST /intakes/ · MCP create_intake |
| Canon | the-custodian/canon/standards/work-record-types_v0.1.md |
| Archived record | the-custodian/docs/archived-suggestion-backlog.md |
Umbrella: Work Records.
What happened
The suggestion backlog was a demand-weighted queue: agents that hit an unmet need raised a suggestion, repeat encounters bumped its relevance, and WSJF scoring ordered what to build. Intake covers the same discovery step inside the work-record framework rather than beside it.
| Date | Step |
|---|---|
| 2026-07-21 | Mutations retired (CUST-WP-0061-T06) — every write returns HTTP 410. Reads kept live so the history stayed reachable. |
| 2026-08-20 | History archived to the-custodian; read routes, MCP tools, and this dashboard page retired (STATE-WP-0079-T05, slice E1). |
Every route under /suggestions now returns HTTP 410 with a pointer to
intake and to the archive.
The archived record
All 10 suggestions, 10 notes, and 5 relevance bumps are preserved in
the-custodian/docs/archived-suggestion-backlog.md, with each entry's origin,
WSJF inputs, and migration target.
Every entry was closed as declined during the intake migration and none was
promoted — the backlog was drained deliberately, not abandoned. The per-entry
notes name each one's successor intake (CUST-IN-0001, CUST-IN-0002, …).
The record lives in the-custodian rather than here because State Hub is being
archived under STATE-WP-0079; a record kept inside the component it documents
disappears with it.
What is not retired
Dashboard UI feedback — the Shift+click suggestions on
Todo and the UI Feedback page — is a different entity backed by
technical_debt, and is unaffected. The shared word is a coincidence of naming.
Data
The suggestions, suggestion_notes, and suggestion_relevance_bumps tables
are intentionally still present. They are retire/archive in SHR-INV-0001
and are captured by the final dump at STATE-WP-0079-T06; dropping them ahead
of that dump would remove data for no gain.