Roadmap · Living dashboard
EVERYONE Roadmap
What is live, what is in flight, what is planned through the late 2026 launch window and beyond. The when and how, alongside the why in /platform.
- v0.1 of the personal Roster shipped May 10, 2026 at /me/roster (gated). Live, operational, backed by an 11,518-person contact graph spanning five sources.
- Ring 0 burn-in. Two weeks of daily use by Zak with real data, surfacing bugs, friction, and surprising delights. Ring 1 (Stephen Brooks as User 1) opens after.
- v0.2 next 30 days. Externalized allowlist, Calendar enrichment in production, Ring 1 onboarding, optional Meta-export with Messenger when ready.
- v0.3 next 60-90 days. OAuth onboarding, embeddings for semantic search, daily intelligence loop, Constellation visualization, public-team bridge, streamlined Ring 3 onboarding for the first 100.
- Ring 4 Public launch. Target window: late 2026. (The World Cup runs November 14 to December 18, 2026, and the Biggest Team campaign is being developed against that window.) Includes anonymous-mode Roster preview, branded landing, free-plus-paid tiers with billing, multilingual (Spanish first).
- Eight risks tracked openly with current mitigations. Eight things we don't yet know.
What is live now
Everything below is verifiable in production today. Each item is operational, gated where appropriate, and serving real users (currently the core team) over real data.
In flight
Ring 0 burn-in is the headline. Two weeks of daily use by the founder with real data is the gate before Ring 1 opens. The advisor email opens the conversation with our closest collaborators about whether the breakthrough lands as intended.
Next 30 days
The bridge from v0.1 to Ring 1 readiness. Externalize the allowlist so adding users is a data change, not a code edit. Bring richer data into production. Open to the first non-founder user.
Next 60-90 days
Ring 2 (five core advisors) and Ring 3 (first 100). The product hardens for non-founder users at small but real scale. OAuth replaces file uploads. Embeddings unlock the next search-quality jump. The daily intelligence loop turns the Roster into a returning ritual.
Ring 3 horizon
The first 100. Friend-of-friend invitation graph. Most things will work; one will not. This is where the system either earns its spot in 100 daily workflows or surfaces what we missed.
Public launch (target: late 2026)
The largest single distribution moment available to EVERYONE in our planning horizon. Public team formation as the front door. Personal Roster as the second click. Conservative target: 5,000 to 25,000 Rosters within a year of launch. Aggressive target: 100,000. Specific timing depends on team and funding state; the World Cup window is what we are aiming for.
Post-launch
Marketplace activation. Public team mechanics. Partnership integrations. The connection engine moving from hand-curated matches to confident automation. The agent-era pitch becoming operational.
Risks and mitigations
Eight items where failure would meaningfully set back the project, with current mitigations. Where we are confident, we say so. Where we are still figuring it out, we say that too.
Risk. The Roster's selfish-benefit-on-day-one is sticky for a session. Without daily or weekly proactive surfacing, users do not return often enough for retention to compound.
Mitigation. Daily intelligence loop (M8). Weekly Roll Call ritual. "World got smaller today" notifications. Currently leaning toward the weekly Roll Call as the primary ritual hook.
Risk. The engine becomes useful at density. Until ~50 to 100 members exist in a metro or topic, matching is dormant.
Mitigation. Hand-curated matches in the early phase. Each match becomes a story. Stories become launch material. Local clusters activate at threshold.
Risk. Bad matches break trust. A wrong introduction is worse than no introduction.
Mitigation. Stay manual through the first phase. Build a labeled training set from manual matches. Then automate with confidence thresholds and human review at edges. Tracked to M25.
Risk. The "front door for positive technology" thesis works only with a real funnel of partners who pass our guardrails and deliver value to members.
Mitigation. Multiple partnership conversations active. Each is its own vetting cycle.
Risk. Six months from now to launch is short. Many things to ship. Risk of underestimating scope or trying to ship too much.
Mitigation. Disciplined ring-by-ring rollout. Ring 4 launch ships the operational essentials, not the full vision. Marketplace, full automation, the agent API can come after launch. Tracked by milestone slippage in this Roadmap.
Risk. Some advisors push toward a token model. Token model risks misaligned incentives, regulatory complexity, and the optics of "another crypto thing."
Mitigation. Defer the question. Ship without a token through launch. Revisit only if a token would serve the team in a way nothing else can.
Risk. Long-term vision includes EVERYONE as substrate for AI alignment, governance, and civic deliberation. Audience for that is unclear (foundations, governments, AI labs). Wrong positioning kills the long-tail value.
Mitigation. Treat the alignment substrate as Year 2-plus work. Build the network first. The substrate follows.
Risk. What we have not considered.
Mitigation. Closest-collaborator email and follow-up calls. Five Ring 2 advisors with explicit "tell me what we have not considered" mandate. Day-14 reviews per ring with honest "what surprised us" sections. Real-time canon writing so insights survive sessions.
Things we don't yet know
Eight unresolved questions where advisor and partner input is most useful. Naming them publicly is part of the discipline. The most useful thing an advisor can do is identify what we have not considered.