Routes
Every record and command a venture has is a route, generated from the data model and the kits. The CLI, the MCP server and the HTTP API share one route table, so they cannot disagree.
Routes follow the Next.js App Router. Layers stay in the path, so a route is its record’s folder path: purpose/validation/problem is purpose/validation/problem.json.
| Next.js | Here |
|---|---|
route | Record actions read, write, check and template; command routes run |
page | The view action: a Markdown page for a person |
layout | The context an agent gets before acting: kit purpose, skills, references, template, gate and need-now status |
not-found, loading, error | A missing record answers with its template; a waiting draft is reported; a failed check answers with how to fix it |
[id] | Collection items, such as purpose/product/kettle |
[...slug] | The venture, by id or by a nested venture’s path (studio/print) |
(group) | One group per phase |
@slot | system/overview: slots that render side by side |
_private | _drafts/, never routed |
proxy | Gates before every write |
robots | The routes a team-plan role may read and write |
| redirects | Route aliases for renamed routes |
Every route
| Route | Actions | Files or script | Decision class | What it is |
|---|---|---|---|---|
evidence/evidence | read, view, layout, check | evidence/results/*.json | Append-only results of running checks | |
evidence/evidence/[id] | read, view, layout, write, check | evidence/results/*.json | Append-only results of running checks | |
execution/handoff | read, view, layout, check | execution/handoffs/*.json | ||
execution/handoff/[id] | read, view, layout, write, check | execution/handoffs/*.json | ||
governance/board | read, view, layout, write, check | governance/board.json | ownership-or-control | Formal and advisory boards, their seats and reserved matters |
governance/decision-rights | read, view, layout, write, check | governance/decision-rights.json | strategy-or-constitution | |
governance/exit | read, view, layout, write, check | governance/exit.json | ownership-or-control | Exit paths kept open and sale values to model; payouts computed by payouts.mjs |
governance/founder-agreement | read, view, layout, write, check | governance/founder-agreement.json | ownership-or-control | What founders agreed: roles, commitment, IP, departure, deadlock; prose beside it |
governance/ownership | read, view, layout, write, check | governance/ownership.json | ownership-or-control | The cap table: share classes and their rights, holders, grants with vesting, option pool, SAFEs and notes (EE-022) |
governance/payouts | run, view, layout | schema/payouts.mjs | Who gets what at a sale value, from the cap table (EE-022); input value, else the scenarios in exit.json | |
governance/pillar | read, view, layout | pillars/*.md | The product, brand and business pillars: teams, roles and deliverables. The template holds the guides; a venture holds one-line stubs that link to them | |
governance/pillar/[id] | read, view, layout | pillars/*.md | The product, brand and business pillars: teams, roles and deliverables. The template holds the guides; a venture holds one-line stubs that link to them | |
governance/publication-policy | read, view, layout, write, check | governance/publication-policy.json | strategy-or-constitution | Where the venture publishes and who may publish what there: channels, guidelines, checks, preview and approvers; every publication passes this gate (EE-025) |
knowledge/venture-profile | read, view, layout | profile.md | The venture's story and thesis in prose, beside venture.json | |
operations/mad-answers | read, view, layout | operations/systems/*.answers.json | Answers to the MAD questions for one system; MAD repo has record.schema.json, not yet folded in | |
operations/mad-answers/[id] | read, view, layout | operations/systems/*.answers.json | Answers to the MAD questions for one system; MAD repo has record.schema.json, not yet folded in | |
operations/team-plan | read, view, layout, write, check | operations/team-plan.json | Who the venture needs, agent or person, when, with what authority, and where a human stays in the loop; recruiting briefs for open person roles (EE-029) | |
purpose/account | read, view, layout, check | accounts/*/account.json | A named party the venture keeps a record for: client, customer, user, member or partner (EE-021). Optional | |
purpose/account/[id] | read, view, layout, write, check | accounts/*/account.json | A named party the venture keeps a record for: client, customer, user, member or partner (EE-021). Optional | |
purpose/anatomy-answers | read, view, layout | purpose/anatomy.answers*.json | Scores per product per question; the matrix is rendered from them | |
purpose/product | read, view, layout, check | products/*.json | ||
purpose/product/[id] | read, view, layout, write, check | products/*.json | ||
purpose/telos | read, view, layout, write, check, template | purpose/telos.json | strategy-or-constitution | The end the venture exists to reach: statement, end state, measures, owner outcome, exit criteria per phase (EE-023) |
purpose/validation/go-to-market | read, view, layout, write, check, template | purpose/validation/go-to-market.json | Validation sub-score: path, motion, channels and evidence a channel works; the path sets the weights (EE-026) | |
purpose/validation/operations-readiness | read, view, layout, write, check, template | purpose/validation/operations-readiness.json | Validation sub-score: per MAD tier evidence; grades as the weakest tier (EE-026) | |
purpose/validation/pricing | read, view, layout, write, check, template | purpose/validation/pricing.json | Validation sub-score: price model, points, buyer and evidence they pay (EE-026) | |
purpose/validation/problem | read, view, layout, write, check, template | purpose/validation/problem.json | The problem sub-score of validation: the claim and its cited evidence, each item graded (EE-026). Shares schema/validation-evidence.schema.json with every sub-score | |
purpose/validation/product-market-fit | read, view, layout, write, check, template | purpose/validation/product-market-fit.json | Validation sub-score: retention cohorts, Ellis survey and evidence that a segment keeps using it (EE-026) | |
purpose/validation/score | run, view, layout | schema/check-validation.mjs | The validation score from graded evidence (EE-026) | |
purpose/validation/solution | read, view, layout, write, check, template | purpose/validation/solution.json | Validation sub-score: how it solves the problem and the evidence people choose it (EE-026) | |
purpose/validation/team | read, view, layout, write, check, template | purpose/validation/team.json | Validation sub-score: skills needed, held and the gaps; cofounder sought (EE-026) | |
system/need-now | run, view, layout | schema/need-now.mjs | What the venture needs now, soon, or should hold back (EE-028) | |
system/overview | run, view, layout | router | The venture at a glance: telos, validation, need-now, time to ready, team and recent provenance, rendered as parallel slots | |
system/provenance | read, view, layout, check | provenance.jsonl | Who or what wrote each record, how, from what and under which decision: one append-only line per write, hash-chained, after W3C PROV (EE-031) | |
system/robots | run, view, layout | router | Which roles may read and write which routes, from the team plan | |
system/time-to-ready | run, view, layout | schema/time-to-ready.mjs | Time to running, and to ready per layer and MAD tier |
Last updated on