The build map. Where we are, where we're going, and why it matters.
The Core: NowPage is a live proof weapon. You sit across from someone, demonstrate value in real-time, and the page IS the demo. No pitch deck. No follow-up email. The page speaks for itself.
Everything below serves this. Each phase unlocks a multiplier on the one before it. Vault unlocks team independence. Teams unlock Derek and Will running their own pipeline. MCP unlocks speed. Mobile unlocks the coffee shop moment — the one where someone watches you build their page while they're still talking.
The order matters. You can't do Mobile without Vault (BYOK keys for transcription). You can't do Teams without Vault (shared secrets). But each phase ships independently and delivers value on its own.
Why this was first: Every API key lived in Vercel env vars that only Jason could touch. Derek wanted to run Reveal with his own Anthropic key. Will wanted to test with a different model. They couldn't — bottlenecked on one person's credentials.
The Vault fixed this with two encrypted functions (encrypt/decrypt) that become the entire swap surface for MasteryOS later. Today it's a Supabase table with AES-256-GCM. Tomorrow it's a MasteryOS API call. Zero other code changes.
Shipped March 6, 2026. AES-256-GCM encryption, full CRUD API, VaultManager UI, resolveKey() integrated into all 6 studio routes. Migration pending Supabase application.
Internal first, product later. Derek, Will, and Jason need to share domains without stepping on each other's pages. Derek should edit pages but not manage team membership. Will should have full admin. Viewers (future clients?) see dashboards and analytics but can't break anything.
The same tables and RLS policies that serve the internal team today become paid team seats tomorrow. We're not building billing or onboarding — just clean tenant isolation that happens to be exactly what a SaaS product needs.
Claude Code is the daily driver. Right now, publishing a page means running a node script with 6 flags. The /publish skill makes it one command. MCP makes the entire platform programmable — list pages, move them between domains, check analytics, read vault secrets — all from Claude Code or any AI tool.
This is where the workflow compounds. Today: edit file → compile → publish → open browser → verify. Tomorrow: "publish this to ideas.asapai.net" and it's done. The AI handles the compile, the slug detection, the domain lookup, the URL opening.
This is the headline demo. You're at a networking event. You pull out your phone, record the conversation. 30 seconds later, you show them a QR code. They scan it. They see a page with their name, their pain points, their opportunities — built while you were talking to them.
Page 1 generates fast with links to deeper pages already baked in. Background loop builds pages 2, 3, 4 while they're reading the first one. Full depth, but the wow moment is instant. Before an event, preset your template, CTA, and domain — then the flow is: record, name, generate. Three taps to QR.
Depends on: Phase 1 (Vault) for BYOK transcription API keys. Reveal pipeline already exists — Mobile is a new frontend for it.
Everything below is live in production. This is the foundation the build phases extend.
Not on the critical path, but captured and scoped. These get built when the primary phases create breathing room.
Self-service infrastructure. Managing Vercel env vars and running Supabase migrations requires switching to external dashboards that only Jason can access. This creates a bottleneck.
Three layers: Vercel env var sync (read/write/push-pull with vault), SQL editor with read-only mode, and migration runner with schema browser. All admin-only with full audit logging.