From first visit to activated Canvas.

The path, end to end

A person lands, signs in, and — if they're new — walks a five-step wizard while a context pipeline runs in the background. Two transactional emails bracket that (welcome at sign-up, context-ready when the pipeline finishes), and a day-based cadence follows.

01Entry channels → what fires

There is one convergence point. Whether someone signs in with Google, email/password, or enterprise SSO, the very first server write is the same, and it's what kicks the whole funnel off.

The convergence: one bridge, one write

Every new Firebase Auth user (Google, email/password, or a workos_<id> account minted by the SSO callback) fires functions/src/authOnboardingBridge.ts. It writes users/{uid} with status:"created", onboardingStep:1, creditBalance:50. That single create fans out to two triggers:

02Which emails send — the real ladder

Two emails are triggered by status transitions on users/{uid} (emailTriggers.ts → emailOnUserUpdate). The rest are a day-based cadence scheduled at sign-up. Every subject and link below is verbatim from the template source. Brand base: platformUrl = https://aaas.love.

Every send passes an opt-out check (email-preferences-guard.ts): global emailOptIn, then a per-category flag (defaults to send). Two examples below are rendered straight from the template code — this is exactly what lands in the inbox.

03The onboarding wizard — five steps

Shown by AuthGate whenever onboardingStep < done. The steps are context → agents → first_task → vault → welcome; the parent persists the step index after each advance. Step 1 watches the context pipeline; steps 2–4 read what that pipeline produced.

Step 1 Context

Seed the business context every agent and dashboard reads. In the platform build this animates a live pipeline checklist; in the Canvas port it captures goal, company, mission, one-liner and ICP.

Reads	onSnapshot(context_pipelines/{uid}) — status + per-step status
Writes	the intake + context datapoints (goal / company / mission / one-liner / ICP)
Advance	auto when the pipeline completes (or “Continue anyway” after a stall)

Step 2 Agents

Pick the specialist you'll hand your first task to. Cards come from the context pipeline's suggestions — with a static fallback when it hasn't produced any (which, today, it usually hasn't).

Reads	context_pipelines.suggestedAgents → fallback list
Writes	favoriteAgents on the star toggle; selection held client-side
Advance	manual — “Continue with this agent”

Step 3 First Task

A pre-written brief for the chosen agent, with copy-to-clipboard and open-in-email.

Writes	nothing server-side — purely a client mailto: / clipboard
Advance	manual — any of three buttons; sending is never verified

Truth & gap: the wizard's “first task” never creates an agent_tasks doc — so the day-0 first_task cadence email (which fires on the first real agent_tasks write) will not trigger from finishing this step alone.

Step 4 Vault

A short tour of the skill vault plus up to five recommended skills matched to context.

Reads	context_pipelines.recommendedSkills (this field is populated for business emails)
Advance	manual — “Start using AaaS”

Step 5 Welcome

“You're all set” — a celebration with quick actions. Finishing writes the done step and reloads into the dashboard.

Writes	onboardingStep = DONE · platform done = 5; the Canvas gate exits at < 6, so completion writes 6
Advance	“Enter Dashboard” → finishOnboarding() → reload

04Where they land, and what's waiting

Onboarding and the app share one route — /select, gated by AuthGate. Once onboardingStep clears the threshold, the same gate renders the Canvas shell instead of the wizard. These are the surfaces a member lands in.

05Gaps vs the current /delivery-funnel page

The live aaas-design.web.app/delivery-funnel page describes a 10-stage pipeline — but much of it predates the current onboarding and has drifted from the code. These are the substantive gaps to close before that page is overwritten with this one.

06Human test plan

A quick end-to-end pass. Tick each; if the “expect” doesn't happen, that's the bug.

1. Open aaas.love.the “I am a …” radial hero and a Login button are visible.
2. Click Login and sign in (Google or WorkOS).you land on /select — either the wizard (new user) or the Canvas (returning).
3. As a new user, walk the wizard: Context → Agents → First Task → Vault → Welcome.the step counter climbs “1 of 5” → “5 of 5”; Back/Continue work.
4. On Agents, pick an agent; on First Task, click “Copy”/“Open in email”.the brief copies / your mail client opens — no error.
5. Finish (“Enter Dashboard”).the wizard closes and the Canvas dashboard renders; refreshing does not re-open the wizard.
6. Check your inbox.the welcome email arrived — subject “Welcome, … — your agents are one email away”, agent handles at @aaas.name, a working “Open the dashboard” link.
7. Open Account → Support → Submit a brief.each surface renders; the brief modal opens and accepts a submission.

07Handover — a click-only walkthrough

Front-end smoke test only. The agent just clicks and checks what appears — no login, no typing beyond the wizard fields, no back-end. Use the public Canvas showcase so nothing is gated.

1. Go to https://aaas-canvas-live.web.app.a page titled “Fleet — public showcase” with a grid of dashboard cards.
2. Click the “Member Home” card.the Canvas shell opens with a left rail and a home dashboard.
3. In the address bar, add #personal/onboarding and press Enter.the onboarding wizard appears, showing “Step 1 of 5 · Context”.
4. Click the primary “Continue” button (bottom-right).it advances to “Step 2 of 5 · Agents” and shows agent cards.
5. Click an agent card, then “Continue”.“Step 3 of 5 · First Task” with a Copy / Open-in-email pair.
6. Click “Continue” twice more.“Step 4 · Vault”, then “Step 5 · Welcome — You're all set”.
7. Click “Enter dashboard”.the wizard closes; a dashboard renders (no error overlay).
8. Back on the showcase, click each remaining card (Ops, Marketing Analytics, Content, Fleet, Soundboard).each opens its dashboard without a blank screen or console-blocking error.