| doc | README | ||
|---|---|---|---|
| audience |
|
||
| status | living | ||
| owner | product | ||
| last_reviewed | 2026-07-30 |
The company-wide priority board: what we are building now, next, and later.
So humans and agents share one view of intent and order. Avoids “everything is urgent” and keeps work moving through clear horizons.
- Founders / product / eng leads setting priority
- Engineers picking up work
- Agents that need to know what matters right now
Living — active priorities are maintained in NOW.md / NEXT.md /
BACKLOG.md. Update when priorities shift.
| File | Meaning |
|---|---|
NOW.md |
Active work (1–3 items) |
NEXT.md |
Committed, not started |
BACKLOG.md |
Queued, prioritized |
IDEAS.md |
Unprioritized |
MILESTONES.md |
Major outcomes + dates |
RELEASES.md |
What shipped |
Now: Engineering Kernel MVP · RFC-0001 · data model
Next: AI Context Engine · Engineering Rules
Backlog: Agent Runtime · MCP Toolkit · Product Brain
Edit the relevant horizon file and open a PR. Keep NOW.md to 1–3 items —
promote from NEXT.md / BACKLOG.md as work completes. Link RFCs/ADRs when a
priority implies a design decision.