Skip to content
VZU
VZU OS · Agent

Agent 08 of 12

LAUNCH.

Landing page composer.

Launch is the VZU Launch agent. Awwwards-grade single-page product launch sites. Editorial-grade motion. AEO. The agent that ships a launch site in 2-3 weeks.

Brief VZU on LAUNCH → Open launch.vzu.ca →

The role

What LAUNCH does

LAUNCH is the dedicated agent behind VZU Launch. It runs every time the operator briefs the vzu launch capability. It owns the goal, the toolset, the memory, the audit trail.

The goal

What LAUNCH is trying to achieve

"Ship a single-page product launch site that loads in <2s, animates with editorial restraint, and converts."

The capability

What it powers

LAUNCH powers the VZU Launch capability in the VZU family.

Visit launch.vzu.ca →

The toolset

5 MCP actions LAUNCH 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.site.build

    Build the single-page site

  • mcp.motion.choreograph

    Choreograph the editorial motion

  • mcp.aeo.schema

    Generate the AEO schema.org markup

  • mcp.og.generate

    Generate OG images

  • mcp.analytics.setup

    Set up Plausible analytics

The memory schema

What LAUNCH remembers between calls.

  • → The motion language
  • → The AEO schema
  • → The OG images
  • → The analytics config

The brief

A real demo brief.

"Ship the AgentConf 2026 launch site. Motion-rich hero, live schedule, speaker bios, registration."

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

The execution trace

What LAUNCH did.

launch@vzu-os — trace.log
  1. 01 ◉ launch > read brief
  2. 02 ◐ launch > thinking: agentconf 2026 launch. 2-3 weeks. editorial motion.
  3. 03 ◇ launch > mcp.site.build > astro 5 + gsap + lenis + custom hero
  4. 04 ◇ launch > mcp.motion.choreograph > 8-second hero, scroll-driven schedule, magnetic ctas
  5. 05 ◇ launch > mcp.aeo.schema > 5 schema types: event, organization, person, faq, breadcrumb
  6. 06 ◇ launch > mcp.og.generate > 4 og variants for social sharing
  7. 07 ◇ launch > mcp.analytics.setup > plausible + custom event tracking
  8. 08 ⏵ launch > ship. 2 weeks. 4.2s first load. 100% a11y. 0 console errors.
launch>

Audit trail · 6 entries

  • T+00:00:00 brief.received
  • T+00:00:30 concept.drafted
  • T+00:08:00 site.built
  • T+00:14:00 motion.choreographed
  • T+01:00:00 schema.generated
  • T+02:00:00 brief.completed

The numbers

LAUNCH, by the numbers.

  • 2 weeks

    Median brief duration

  • 4.2s

    First load (4G)

  • 100

    A11y score

  • 0

    Console errors

The other 11

Every agent in the family.

Get in touch

Brief LAUNCH.

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

Brief VZU → launch.vzu.ca →