Roadmap

Nothing is dated here. Order is what matters: the first release follows the runbook, and everything after it is sequenced by dependency. Status words are the five of the catalog; today every product is designed. The first release ran on 2026-09-13, so the four hosts answer, but no person can sign in until the identity provider is registered (runbook step 7).

Designed today

Surface	What exists	Status
API	117 designed routes under `/api/v1`, migration `0001` with 32 tables, 72 permissions, 10 personas, worker, fake agent runtime, four designed providers	`designed`
Web app	the shell (rail, panel, topbar), every product section, Setup and Organization, dev-identity mode, shots runner	`designed`
Agent runtime	container with bounded phases `compare`, `gaps`, `hypotheses`, `draft_protocol`, `draft_report`, `review_check`, redaction and attribution lint, fake agent and contract tests	`designed`
Docs	this site: two areas, code mirror, gates	`designed`
Site and deck	static marketing export and the fragment deck, both reading the same vocabulary	`designed`
Infra	Terraform stacks (bootstrap, dns, environment) applied to the dev account on 2026-09-13; see the deployment record	`designed`

What the first release needs

In runbook order (infra/RUNBOOK-first-release.md, summarised on the first release runbook page):

A git host and remotes for the seven repositories (org.gitHost and org.gitOrg are local and trovensa).
A cloud account, remote state, network, cluster, database, registries, secret shell, DNS zone and certificate, applied from the infra repository.
The runtime secret with DATABASE_URL, DEV_TOKEN_SECRET and AGENT_MODEL_ID; the model id is never a literal.
First images pushed with sha tags to an immutable registry.
DNS handover of trovensa.com and certificate validation; the domain is not verified today.
First release of api and web with the migration Job, health checks and the deployed tags committed.
Identity registration with the two /auth/bridge redirect URIs and the AUTH_* values.
Static deploys of the site and the docs, then their DNS records.
The agent runtime, optional on the first day, with FEATURE_AGENT_RUNS and the runtime ARN in the config map.

After the first release

Provider adapters that fetch data: literature search, electronic lab notebook, document library, analytical and design tools are designed stubs whose sync runs finish skipped.
Approved tools that execute: tool invocations return an explanatory summary today.
A real agent runtime behind AGENT_RUNTIME_URL or AGENT_RUNTIME_ARN in place of the fake.
Custom roles from the same permission catalog beyond the ten personas.
Recounting every number on this site on publish day: routes, tables, permissions, token pairs, contrast pairs.

Not planned

Compliance claims of any kind, market or productivity figures, and any capability sentence that presents a designed product as live. Agents prepare, compare, propose and flag; a person decides.