Type a brief.
Watch the runtime orchestrate it.
VZU OS is the agent operating system that powers every VZU capability. Pick a brief below — or type your own. Twelve agents wake up, route, and execute. The audit trail is on from the first character.
What kind of brief?
Brief
Pattern ·
Agents 0/0 active
- 01
ATLAS
engineering
- 02
VEGA
engineering
- 03
KAI
engineering
- 04
NOVA
design
- 05
PIXEL
design
- 06
ECHO
design
- 07
SKETCH
design
- 08
LAUNCH
design
- 09
SENTINEL
review
- 10
ORACLE
review
- 11
QUILL
data
- 12
HUNTER
automation
Live trace
Brief complete
The runtime shipped your brief.
Brief
Route
Trace tail
The network
The orchestrator. The 12 agents. The brief.
Tap any agent to see its trace. The orchestrator sits at the center. Particles flow on the connections. The network breathes.
Chapter 01 · The brief
A real brief, decomposed into a runtime plan.
Every VZU OS run starts with a brief. Not a request. Not a ticket. A real brief — a real problem from a real operator, with a real deadline, against a real budget. The brief is the contract. The work is the work. The audit trail is the record.
When the orchestrator receives a brief, it decomposes the brief into subtasks. Each subtask is routed to a specialized agent. The agent's toolset, memory schema, and audit posture are pre-configured. The MCP servers it can call are pre-registered. The agent runs. The orchestrator observes. The orchestrator replans. The work ships.
The runtime is a closed loop. Brief in, ship out. Every step is auditable. Every step is replayable. Every step has a reason. The reason is in the audit trail. The audit trail is the regulator's form. The audit trail is the operator's record. The audit trail is the work.
Chapter 02 · The execution
The agent runs. The runtime observes. The audit trail seals.
When the orchestrator routes a subtask to an agent, the agent activates. The agent reads its memory. The agent calls its MCP servers. The agent observes the result. The agent replans. The agent ships a result. The orchestrator receives the result. The orchestrator records the result in the audit trail. The orchestrator moves to the next subtask.
Every step the agent takes is recorded. The audit trail includes: who (the agent), what (the action), when (the timestamp), why (the agent's reasoning), with which model, against which data, with which result. The audit trail is on from the first character of the brief. The audit trail is the regulator's form. The audit trail is the operator's record.
Three orchestration patterns. Relay — A hands off to B hands off to C. The cleanest pattern. The most auditable. Parallel — A and B and C run independently, results combined. Used when the brief has independent subtasks. Supervisor — A delegates to B and C, observes, re-delegates. The most powerful pattern. The most audited. The right pattern depends on the brief.
“Brief in, ship out. Every step is auditable. Every step is replayable. Every step has a reason. The reason is in the audit trail.”
— The VZU OS, runtime contract
Chapter 03 · The result
The work ships. The audit trail seals. The runtime resets.
When all subtasks are complete, the orchestrator reviews the work. The orchestrator checks the audit trail. The orchestrator checks the operator's RBAC. The orchestrator signs the result. The result is sealed. The result is delivered.
The operator owns the goal. The runtime owns the work. The audit trail is the regulator's form. The brief is the contract. The brief sets the boundary. The work is the work. The audit trail is the record.
8s
median brief · 12 agents · 1 runtime
Chapter 04 · Live demo
Run a brief. Watch the runtime ship.
Tap "Run trace" below. The Atlas agent will execute a real brief — the multi-tenant booking platform that powers BookFlow. Every step will light up. The audit stream will fill in.
Brief
Build a multi-tenant booking dashboard for service businesses. Calendar views, customer management, Stripe Connect integration.
The Atlas agent. A real brief. In motion.
- 01
read brief
- 02
thinking: brief is "build a multi-tenant booking dashboard". scope: 2 weeks.
- 03
mcp.data.schema > generate schema: tenants, services, customers, bookings, payments
- 04
thinking: stripe connect requires 2-day payout. need to scope webhook handler.
- 05
mcp.code.generate > next.js 15 + prisma + stripe-connect-express
- 06
mcp.code.generate > component library: Calendar, CustomerList, BookingForm
- 07
mcp.deploy.staging > ship to staging.atlas.vzu.ca
- 08
mcp.test.run > 47 integration tests passing
- 09done
ship. 14 days. 4 deploys. audit trail: 23 entries.
Audit stream · 0/8
- 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 audit trail
Every step. Every reason. Every result.
- 01atlas › read brief
read brief
- 02atlas › thinking: brief is "build a multi-tenant booking dashboard". scope: 2 weeks.
thinking: brief is "build a multi-tenant booking dashboard". scope: 2 weeks. : brief is "build a multi-tenant booking dashboard". scope: 2 weeks.
- 03atlas › mcp.data.schema
generate schema: tenants, services, customers, bookings, payments : tenants, services, customers, bookings, payments
- 04atlas › thinking: stripe connect requires 2-day payout. need to scope webhook handler.
thinking: stripe connect requires 2-day payout. need to scope webhook handler. : stripe connect requires 2-day payout. need to scope webhook handler.
- 05atlas › mcp.code.generate
next.js 15 + prisma + stripe-connect-express
- 06atlas › mcp.code.generate
component library: Calendar, CustomerList, BookingForm : Calendar, CustomerList, BookingForm
- 07atlas › mcp.deploy.staging
ship to staging.atlas.vzu.ca
- 08atlas › mcp.test.run
47 integration tests passing
- 09atlas › ship. 14 days. 4 deploys. audit trail: 23 entries. done
ship. 14 days. 4 deploys. audit trail: 23 entries. : 23 entries.
Audit trail · 8 entries
- T+00:00:00 brief.received 01
- T+00:01:12 orchestrator.decomposed 02
- T+00:04:33 mcp.data.schema.generated 03
- T+02:18:07 mcp.code.generate.api.completed 04
- T+05:42:19 mcp.code.generate.ui.completed 05
- T+08:11:55 mcp.deploy.staging.completed 06
- T+11:33:48 mcp.test.run.completed 07
- T+14:00:00 brief.completed 08
- KPI · 01 now
14 days
Median brief duration
43% - KPI · 02 now
12,400
Avg lines of code
32% - KPI · 03 now
8
Deploys per brief
31% - KPI · 04 now
100%
Tests passing
14%
Get in touch
Run your brief on the real runtime.
The runtime ships in your region. Cloud, hybrid, or air-gapped on-prem. The brief is the contract. The work is the work. The audit trail is the regulator's form.