Skip to content
VZU
VZU OS · Agent

Agent 01 of 12

ATLAS.

Full-stack app builder.

Atlas is the VZU Build agent. It takes a brief and ships a production-grade web application in days. It owns the data model, the API surface, the frontend, and the deploy. The operator owns the code.

Brief VZU on ATLAS → Open build.vzu.ca →

The role

What ATLAS does

ATLAS is the dedicated agent behind VZU Build. It runs every time the operator briefs the vzu build capability. It owns the goal, the toolset, the memory, the audit trail.

The goal

What ATLAS is trying to achieve

"Decompose the brief into a data model, an API surface, a UI flow, and a deploy. Compose them into a production web app."

The capability

What it powers

ATLAS powers the VZU Build capability in the VZU family.

Visit build.vzu.ca →

The toolset

5 MCP actions ATLAS can call.

Every action is exposed as an MCP server (Model Context Protocol). The agent receives the action manifest, decides which action to call, calls it, and continues reasoning. The audit trail records every call.

  • mcp.file.read

    Read the brief and any prior decisions

  • mcp.data.schema

    Generate a data model from the brief

  • mcp.code.generate

    Generate the API + frontend code

  • mcp.deploy.staging

    Ship to staging on every commit

  • mcp.test.run

    Run integration tests before deploy

The memory schema

What ATLAS remembers between calls.

  • → The brief
  • → The data model
  • → The chosen libraries
  • → The deploy config

The brief

A real demo brief.

"Build a multi-tenant booking dashboard for service businesses. Calendar views, customer management, Stripe Connect integration."

Below is ATLAS's actual execution trace for this brief — every step, every MCP call, every observation, every audit trail entry.

The execution trace

What ATLAS did.

atlas@vzu-os — trace.log
  1. 01 ◉ atlas > read brief
  2. 02 ◐ atlas > thinking: brief is "build a multi-tenant booking dashboard". scope: 2 weeks.
  3. 03 ◇ atlas > mcp.data.schema > generate schema: tenants, services, customers, bookings, payments
  4. 04 ◐ atlas > thinking: stripe connect requires 2-day payout. need to scope webhook handler.
  5. 05 ◇ atlas > mcp.code.generate > next.js 15 + prisma + stripe-connect-express
  6. 06 ◇ atlas > mcp.code.generate > component library: Calendar, CustomerList, BookingForm
  7. 07 ◇ atlas > mcp.deploy.staging > ship to staging.atlas.vzu.ca
  8. 08 ◇ atlas > mcp.test.run > 47 integration tests passing
  9. 09 ⏵ atlas > ship. 14 days. 4 deploys. audit trail: 23 entries.
atlas>

Audit trail · 8 entries

  • T+00:00:00 brief.received
  • T+00:01:12 orchestrator.decomposed
  • T+00:04:33 mcp.data.schema.generated
  • T+02:18:07 mcp.code.generate.api.completed
  • T+05:42:19 mcp.code.generate.ui.completed
  • T+08:11:55 mcp.deploy.staging.completed
  • T+11:33:48 mcp.test.run.completed
  • T+14:00:00 brief.completed

The numbers

ATLAS, by the numbers.

  • 14 days

    Median brief duration

  • 12,400

    Avg lines of code

  • 8

    Deploys per brief

  • 100%

    Tests passing

The other 11

Every agent in the family.

Get in touch

Brief ATLAS.

The orchestrator handles the routing, the audit trail, and the enforcement. ATLAS handles the work. The operator owns the goal.

Brief VZU → build.vzu.ca →