docs(roadmap): prioritize backlog into now-soon-later

This commit is contained in:
zap
2026-03-11 19:22:35 +00:00
parent 1c2b051b23
commit 27211f9325
3 changed files with 120 additions and 1 deletions

View File

@@ -72,6 +72,16 @@
- eval / regression harness
- Reflected the same direction in `memory/projects.md` under `Local service expansion` and `Workflow quality and trust improvements`.
## Roadmap
- Added `memory/roadmap.md` to rank the growing backlog into `Now / Soon / Later`.
- Current `Now` focus:
- subagent reliability
- eval / regression harness
- calendar access/backend
- alert ingestion
- standard operating playbooks
- Mirrored the same prioritization in `memory/projects.md` for quick skimming.
## Follow-up intent
- Be more disciplined about using the daily note as the default inbox and promoting only durable truths into `MEMORY.md`.
- Avoid adding new one-off memory files unless the topic is truly long-lived.

View File

@@ -83,7 +83,29 @@ Lightweight registry of active multi-session work.
- `memory/plans/flynn-council-fix.md`
- `memory/tasks.json`
## Current roadmap focus
### Now
- subagent reliability
- eval / regression harness
- calendar access/backend
- alert ingestion
- standard operating playbooks
### Soon
- email/inbox access
- meeting-prep / briefing pipeline
- notification routing
- local docs/manuals RAG
- broader personal doc search
- local code indexing
- external action audit log
### Later
- broader integration and tooling expansion from `memory/tasks.json`
- lower-priority workflow polish and optional context layers
## Notes
- Use this file for cross-session project state humans may want to skim quickly.
- Keep detailed steps/checklists in `memory/plans/` or `memory/tasks.json`.
- Keep detailed steps/checklists in `memory/plans/`, `memory/tasks.json`, or `memory/roadmap.md`.
- Dont create a project entry for every tiny task; this is the bigger-picture map.

87
memory/roadmap.md Normal file
View File

@@ -0,0 +1,87 @@
# Improvement Roadmap
A practical priority view over the current backlog.
## Now
These are the highest-leverage next improvements.
1. **Fix subagent reliability and completion-event spam handling**
- Why now: it directly affects trust, delegation reliability, and daily usability.
- Related task: `task-20260304-2215-subagent-reliability`
2. **Add eval / regression harness for core assistant behavior**
- Why now: prevents regressions in memory recall, messaging, search routing, and subagent behavior.
- Related task: `task-20260311-1917-eval-harness`
3. **Add calendar access/backend for proactive scheduling help**
- Why now: biggest functional capability gap and prerequisite for the calendar-first daily brief direction.
- Related task: `task-20260311-1908-calendar-access`
4. **Add monitoring / alert ingestion**
- Why now: improves signal routing so important failures reach attention without manual checking.
- Related task: `task-20260311-1917-alert-ingestion`
5. **Add standard operating playbooks for recurring workflows**
- Why now: converts repeated ad-hoc ops/debugging into consistent, low-noise workflows.
- Related task: `task-20260311-1917-operating-playbooks`
## Soon
Strong follow-ups once the Now layer is healthier.
1. **Add email/inbox access for triage and briefing**
- Related task: `task-20260311-1908-email-access`
2. **Add meeting-prep / briefing pipeline**
- Depends partly on calendar/docs access.
- Related task: `task-20260311-1917-meeting-prep-pipeline`
3. **Improve notification routing policy**
- Related task: `task-20260311-1917-notification-routing`
4. **Add local RAG over docs and manuals**
- Related task: `task-20260311-1917-local-docs-rag`
5. **Add broader personal document/search corpus**
- Related task: `task-20260311-1908-doc-search-corpus`
6. **Add local code search / indexing across more repos**
- Related task: `task-20260311-1917-local-code-indexing`
7. **Add change / audit log for external actions**
- Related task: `task-20260311-1917-external-action-audit-log`
## Later
Useful, but lower urgency or more dependent on other foundations.
- stronger GitHub tooling
- Google Workspace access
- local OCR / PDF extraction
- notes-system connector
- structured data connectors
- package / update intelligence
- dependency / credential inventory
- safer sandboxed execution helpers
- stronger local media pipeline
- lightweight decision log
- lightweight people-context layer
- Home Assistant / smart-home integration
- password-manager / secret lookup integration (high trust surface; do carefully)
- Flynn council pipeline follow-up
- council personality depth / council naming revisit
## Guiding principle
Prefer improvements that increase:
- reliability
- trust
- signal quality
- repeatability
- leverage across many workflows
Prefer lower priority for:
- shiny integrations with narrow payoff
- high-trust additions without clear need
- tools that add maintenance burden before they add daily value