exoDocs

Decisions and roadmap

Roadmap

What Exo is building now, next, and later, rendered from roadmap/items.

The roadmap lives in the repository as one Markdown file per item in roadmap/items/. scripts/build-roadmap.mjs compiles those files into roadmap/roadmap.json, and the board below renders that file, so this page never restates roadmap content by hand. Items link to their Entire trail for execution evidence.

To change the roadmap, edit or add an item file, run node scripts/build-roadmap.mjs (it fails loudly on invalid fields), and commit both the Markdown and the regenerated roadmap.json, as described in the roadmap README.

13 items · 7 planned · 5 in-progress · 1 done · generated 2026-10-05

Now

planned urgent · platform · gate: feature-branch · trail IV-170

Convex AI gateway with Jev intelligent model routing

All AI calls from Exo tools (help desk, Observatory chat) route through the Convex AI gateway — one credential, provider-neutral egress. A router using TypeSafe AI's Jev model picks the model per request, maximizing intelligence ÷ cost, with a small classifier layer on top. Model pool changes are config, not deploys.

roadmap/items/ai-gateway-jev-routing.md

planned high · platform · gate: planning · trail IV-170

Unified communications via Bird, owned by Exo

Replace Resend (and any one-off messaging integrations) with Bird as the single communications provider — email, SMS, WhatsApp, Apple Messages, and voice behind one platform-owned layer. Apps never hold provider keys; they call Exo's send function with their tenant ID.

roadmap/items/bird-communications.md

in-progress urgent · security · gate: staging · trail IV-170

Convex Auth across the platform

Replace Clerk with Convex Auth — free, open source, and native to the Convex database. One auth stack for every app instead of a Clerk application per environment.

roadmap/items/convex-auth.md

done urgent · platform · gate: released · trail IV-170

Convex backend for the Exo platform

Exo's data layer moves from Payload/Postgres to Convex: tenants, content, roadmap, billing, releases, delivery targets, and observations as Convex tables with typed functions. Deployed to staging (`frugal-eel-930`) and production (`befitting-bullfrog-619`).

roadmap/items/exo-convex-backend.md

in-progress high · platform · gate: staging

exo-verify — code verification as a platform service

Decision: [ADR 0005](../../docs/adr/0005-exo-verify-verification-service.md).

roadmap/items/exo-verify.md

in-progress high · platform · gate: planning

Foundation — one-click foundation-as-a-service for Trump Accounts

Foundation lets would-be donors (families, founders, companies, community groups) launch their own charitable vehicle that makes qualified general contributions to Trump Accounts (IRC 530A) for a class of children they define. Classes are statutory: all children, one or more states, or one or more birth years (IRS Notice 2025-68 Q&A H-3). We connect donors to the infrastructure; the product owns formation, compliance, and money movement.

roadmap/items/foundation-app.md

in-progress urgent · release · gate: staging

Portfolio delivery guardrails — gated deploys, smoke checks, drift detection

Source: the September 2026 portfolio scorecard (Construct, Exo, Observatory, Rampart). The same failure showed up in every repo: **nothing runs automatically between "merged" and "live"**, so production quietly falls behind staging and breaks without anyone noticing. At scoring time, four public production routes across the portfolio were broken or unreachable and none had been caught.

roadmap/items/portfolio-delivery-guardrails.md

in-progress high · platform · gate: staging · trail IV-170

Roadmap as repo files with a public board

The roadmap lives in the repository as markdown files (this directory) — not in a TypeScript seed, not in a database. Entire trails own live status; these files own intent and scope. A generator produces `roadmap.json` at build time and the public site renders it as a board anyone can read.

roadmap/items/roadmap-as-repo.md

Next

planned high · platform · gate: planning

AI-native help desk and knowledge base

Customer support architecture we own: conversation threading, a searchable knowledge base trained from our own content (site pages, docs, changelogs), and AI triage through the gateway router with human escalation. No managed black-box brain — training data and routing logic live in Exo.

roadmap/items/ai-help-desk.md

planned medium · security · gate: planning

Edge security and WAF

Provider-neutral edge protection in front of the deployment layer: DDoS mitigation, WAF rules, bot filtering, and per-tenant rate limits. An adapter (Cloudflare or lighter alternatives) following the same provider-neutral pattern as email and billing — tenant-configurable without per-site setup.

roadmap/items/edge-security-waf.md

planned high · migration · gate: planning

Every venture's marketing site is a Construct Page on its custom domain

Owner directive (2026-09-26): the public, marketing, and landing surface of every venture is a Construct Page served on the venture's custom domain. Exo hosts the app itself and its fundamentals: identity, data, and delivery. One Page platform means one design system, one editor, one intake/Surface model, and no marketing code living in app repos.

roadmap/items/marketing-pages-on-construct.md

planned high · infrastructure · gate: planning

exo-deploy — web and mobile release toolkit (was exo-mobilize)

Decision: [ADR 0007](../../docs/adr/0007-exo-mobilize-mobile-release-toolkit.md).

roadmap/items/mobile-delivery-pipeline.md

planned high · platform · gate: planning

exo-analyze — Exo-owned product analytics and unit economics

Decision: [ADR 0006](../../docs/adr/0006-exo-analyze-product-analytics.md).

roadmap/items/product-analytics.md

Staging vs. main

This board reflects the staging copy of roadmap/. The main branch also carries an exo-verify item and updated items that accompany ADRs 0005–0007. They will appear here once the branches are reconciled.

Source: content/docs/roadmap.mdx