Roadmap and capability status
Evidence decides what comes next.
A roadmap is a sequence of evidence gates, not a promise of dates, production readiness, funding, or institutional authority.
This page is a typed, source-linked presentation of accepted public roadmap records. It does not replace the repository roadmap, create a release commitment, or convert planned work into live capability.
Controlled language
Four labels, one evidence rule.
The same status vocabulary applies across homepage, roadmap, Trust Center, Forge, support, and funding views.
Live
Publicly available and inspectable now.
Experimental
Available at a bounded evidence level with explicit unresolved limitations.
Planned
Accepted roadmap work that is not implemented yet.
Long horizon
A future direction behind later evidence and safety gates.
Evidence before claims
Current capability status
These labels describe what the public evidence supports today. They do not promise production readiness or independent certification.
Public repository
Governance, architecture, roadmap, public contracts, and synthetic evidence are inspectable now.
Inspect the repository (opens in a new tab)Public website
The accepted Next.js public gateway is deployed on the canonical domains with Git-triggered deployment returned to disabled.
Read current status (opens in a new tab)Trust Center and Open Forge
The source-backed Trust Center and Open Forge explanations are public. Forge itself remains bounded local public/synthetic contributor tooling, not a private or production service.
Read the Sprint 8 evidence (opens in a new tab)Roadmap, support, and funding transparency
Public roadmap, support, and canonical funding-transparency views are deployed without activating transactions, private support intake, or sponsor authority.
Inspect the integrated status (opens in a new tab)Phase 0 newsletter signup
The preserve-and-activate path uses the existing private server webhook and Google Sheet for email updates only. Gate #63 remains open until merged deployment and manual verification are accepted.
Review Phase 0 gate #63 (opens in a new tab)Public synthetic prologue
Sprint 9 remains unimplemented. Issue #64 is defining its public-only, no-account, no-real-health-data, temporary-state, refusal, and accessibility boundaries.
Review the pre-Sprint 9 gate (opens in a new tab)Private Living Chronicle product
Accounts, private Chronicles, production Aster, providers, connectors, and consequential workflows remain behind later gates.
Read current boundaries (opens in a new tab)Active public website sprint
Sprint 8 remains open.
Completed workstreams are implementation evidence inside the draft Sprint 8 pull request. The sprint does not close until 8.10 and explicit founding-steward acceptance.
Workstreams 8.1–8.6
The single-site boundary, App Router shell, navigation, homepage, Promise, guide family, Trust Center, and Open Forge were accepted, merged, and deployed through Sprint 8.
Read Sprint 8 completion evidence (opens in a new tab)8.7 — Roadmap, status, support, and funding transparency
Source-backed roadmap, public-safe support, and canonical funding-transparency views are deployed without creating a second ledger, transaction path, or sponsor authority.
Inspect current status (opens in a new tab)8.8 and Phase 0 — Newsletter disposition
Sprint 8 preserved the no-intake boundary. The post-merge preserve-and-activate path now restores the existing private webhook for email updates only, while issue #63 remains open through deployed verification and Phase 0 acceptance.
Review Phase 0 gate #63 (opens in a new tab)8.9 — Accessibility, performance, security, and route validation
Permanent source and isolated production-preview validation covers public routes, security headers, metadata, authority, contrast, and transfer budgets. Independent and affected-user evidence remains separate.
Review completion evidence (opens in a new tab)8.10 — Completion and Sprint 9 handoff
Sprint 8 was accepted and squash merged through PR #61. The production site is live, Git deployment is disabled again, issue #60 is closed, and the bounded Sprint 9 alignment gate is issue #64.
Read the reconciled status (opens in a new tab)Later evidence gates
Beyond the public website.
Later work remains subordinate to private-data protection, deterministic authority, provider independence, specialist review, and progressive institutional legitimacy.
Sprint 9 — Public synthetic prologue
A no-account, no-real-health-data playable explanation of the Promise and first public synthetic journey. Implementation has not started; issue #64 is defining application ownership, temporary data, deterministic completion, Aster fallback, refusal, accessibility, security, and release evidence.
Review the pre-Sprint 9 alignment gate (opens in a new tab)Sprints 10–13 — Game shell, Lanterns, and Chronicle recall
The universal game shell, first vertical slice, Fourteen Lanterns, and Memory Chamber remain sequenced future product work.
Read the design-to-build sequence (opens in a new tab)Sprints 14–16 — Connectors, Observatory, and Chronicle MCP
Provider-independent connectors, Athena’s Observatory, and private Chronicle MCP remain behind later data, permission, safety, and specialist gates.
Inspect later technical gates (opens in a new tab)Sprints 17–19 — Governance, beta evidence, and public launch
Clinical, safety, accessibility, beta, release, and open-source launch work requires evidence and authority that do not yet exist.
Inspect release sequencing (opens in a new tab)Institutional Phase 0 and progressive stewardship
The organization remains in Constitutional and open-source foundations until the explicit Phase 0 exit review and founder-independence gates are accepted.
Read the institutional roadmap (opens in a new tab)