From first visit to delivered solution — every stage of the AaaS autonomous execution pipeline.
The journey starts when a visitor lands on any of 14+ AaaS-owned domains. Each surface serves a specific role in the AaaS product architecture. Four core domains define the account and activation model: aaas.name (personal account), aaas.company (company account), aaas.select (agent activation via email + database), and aaas.builders (build and publish agents). The remaining domains are specialized views within the same Canvas platform.
output: "export"
or SSR via Cloud Run for blog)
@aaas/auth-core
package across all apps
@aaas/ui
design system — tokens, components
Sign up with Google or email — single click for most users. The system immediately begins building a behavioral profile. A persona label is detected from the first few interactions, shaping every subsequent touchpoint.
packages/auth-core/src/auth-provider.tsx
packages/auth-core/src/sign-in-panel.tsx
Every signup creates an aaas.name personal account — your identity, profile, preferences, and billing. For solo users, aaas.name and aaas.company are identical — one person, one workspace. The moment a second employee joins, aaas.company activates as a shared context layer: team management, shared projects, and unified billing across multiple aaas.name accounts.
accounts/{uid}
(personal) +
organizations/{orgId}
(company)
org.members.length === 1, aaas.company mirrors aaas.name
Invisible to the user, the system learns what they care about through article views, search terms, and channel follows. The 14-dimensional user vector grows more precise with every action, enabling hyper-personalized email and content.
14 dimensions tracked: 6 entity-type frequencies, search activity, channel engagement, and 5 persona one-hot labels. Cosine similarity powers collaborative recommendations.
apps/blog/src/lib/behavior.ts
— localStorage event tracking
apps/blog/src/lib/collaborative.ts
— 14D user vectors
user_behavior
collection
functions/src/contextPipeline.ts
At the right moment, the user receives a personalized email inviting them to describe their challenge. The subject line is tailored to their detected persona. Weekly digests keep them engaged with curated content matching their interest vector.
aaas.select is the agent activation domain. Email
{agent-id}@aaas.select
to activate a specific agent directly — no sign-up required for the initial
trigger.
Example subject lines by persona:
functions/src/lib/email-templates/
— template library
subscriptions
collection
digest-email-agent
— weekly vector-matched digests
The user describes what they need in plain language. No forms, no templates — just a prompt. The system creates a project immediately and a conversation thread is opened for any follow-up questions from the agent.
Example inputs:
POST /api/projects
on Cloud Run API service
services/api/src/routes/projects.ts
projects/{id}
in Firestore
conversations/{id}
thread
Agent Zero kicks off an autonomous research and planning phase. It breaks down the challenge, identifies required tools and resources, and produces a numbered execution plan with a credit estimate. The user reviews and approves before any billable work begins.
services/api/src/services/vm-provisioner.ts
data-root
on PD)
agent-zero-dispatch.ts
projects/{id}/plan_steps/
subcollection
Once approved, the agent executes — working through plan steps one by one. Users can watch real-time progress in the ZUI canvas: each step lights up as it completes. The agent has full access to 50+ built-in tools — web search, code execution, email, payments, and more.
functions/src/lib/foundry/tool-executors.ts
containerStatus:
running → running_async
Delivery arrives via email with links to review. Users choose their viewing mode: a shareable public portal, a deep-dive ZUI canvas with semantic zoom, or the full CRM workspace for managing multiple projects.
functions/src/agentZeroCallback.ts
running → review
project_portal
collection (no-auth read)
Every completed project makes the next one better. The system learns from research quality, user preferences, pricing accuracy, spec clarity, and agent performance — building a growing template archive that accelerates future deliveries.
Internal dashboards give the operations team a live view of pipeline health, agent performance, ecosystem surface status, and outstanding issues. Every phase of the funnel is observable.
aaas-design.web.app
design
firebase deploy --only hosting:design
design/agents/
directory
How the six major subsystems connect — from entry surface through auth, context, planning, execution, and delivery back to the monitoring layer.
@aaas/ui +
@aaas/auth-core.