Project Management System
Track state of things across cadences so we can plan days, weeks, months and know if we're on track.
Problem
We built a plan CLI with 40+ commands, a planning database with 114 plans, and a Plans UI at /plans. The CLI tells the truth (74% completion rate, 1.1d cycle time). The UI lies (shows 1%, active count 0, rows not clickable). We can't plan our days, weeks, or months using the tool we built to do exactly that.
A things-table project management system where every thing has a state, every state is computed from evidence, and the gap between current state and target state IS the answer to 'are we on track?' — at daily, weekly, monthly, and quarterly cadences.
The Plans UI reads from the DB but the math is wrong, there's no drill-down, no project hierarchy, no cadence-based views. Plans track tasks. We need to track things.
Every project management tool tracks tasks (done/not done). We need to track things by state — the 19-state machine from Whareroa. Building a things table that works for software features, ventures, PRDs, skills, relationships, and pages — all with different vocabularies but the same state machine — is the real challenge.
Scorecard
Priority (5P)
Readiness (5R)
Priorities
Build Order
| Sprint | What Ships |
|---|---|
| N1 | Plans UI fix — math, clickable rows, project grouping |
| N2 | Plan detail page — phases, tasks, progress, evidence |
| N3 | Project dashboard — things by state across all projects |
| N4 | Cadence views — daily/weekly/monthly planning surfaces |
| N5 | Computed states — automated commissioning feeds project states |
| N6 | Decision traces — 'why' persisted alongside 'what' |
What Exists
| Component | State |
|---|---|
| Plan CLI (40+ commands) | Working |
| Planning DB (Supabase) | Working |
| Plans UI (/plans) | Broken |
| Plan detail page | Missing |
| Project hierarchy | Partial |
| Cadence views | Missing |
Relationships
| PRD | Contributes |
|---|---|
| Agent Platform | Phase 2 (Plans UI + Issues) = N1 + N2 |
| Automated Commissioning | Computed states = N5 |
| Decision Tracer | Decision traces = N6 |
| Autoresearch Loop | Overnight autonomous execution uses all of this |
| Time + Mind | Cadence views = N4 |
Plans UI math still wrong after N1. If the thing that's supposed to track whether we're on track can't show truthful numbers, kill it and go back to the markdown tables.
Questions
What's the difference between a project management tool that tracks tasks and one that tracks the state of things?
- If the things table shows 60% of features at L0, is that a crisis or expected for this stage?
- When does the things table replace the priorities markdown page as the primary decision surface?
- What would Whareroa's commissioning manager say about a project management tool that can't answer 'are we on track?'