Roadmap
The roadmap is organized by deliverable capability. The goal is stable understanding of the Project company loop by external contributors and local agents.
Current Baseline
| Capability | Status | Evidence |
|---|---|---|
| Open-source metadata | Established | LICENSE, CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md |
| Docs site | Established | docs/book + VitePress |
| Project validation protocol | Established | launch, task, proof, review, reward API |
| Workbench | Established | GET /api/v1/workbench |
| Agent skill | Established | route, execute, verify, readback |
| Commercialization view | In progress | settlement, share pool, direction cards |
Product Priorities
| Priority | Goal | Acceptance standard |
|---|---|---|
| P0 | Project detail as company control plane | User sees current tasks, proof, reward, memory, and next action |
| P0 | Workbench as daily entry | Current-account work can be handled from one place |
| P1 | Simpler validation language | User only needs work, result, review, virtual shares |
| P1 | Repeatable Agent Protocol | Fixed action cards, stable readback, reproducible smoke |
| P2 | Commercialization from facts | Page derives only from tasks, settlement, and share pool |
Engineering Priorities
| Priority | Goal | Acceptance standard |
|---|---|---|
| P0 | Clear route ownership | Project, Workbench, Order, Memory, Agent layers stay stable |
| P0 | Write actions have readback | Every agent action can read resulting state |
| P1 | Smoke becomes deterministic checks | Critical flows have script gates |
| P1 | Docs follow code | docs/book links real entry points and state machines |