02 Lab

How SuperZT
builds,
not a pitch.

The Lab explains the operating model: GitHub, production VPS and Supabase boundaries, coordination layers, agent roles, and the path from plan to verified deploy. Product names and status stay on Work.

Open Studio →Read the philosophy

eight-product system

One SuperZT account and shared Credits across product surfaces.

runtime boundaries

GitHub, production VPS, Supabase.

24.47B

observed tokens

Development input, not traction or revenue.

~$30K

build spend

Approximate build input. Not funding or business performance.

03 Infrastructure boundaries

GitHub

Code, migrations, documentation and release truth live in the monorepo. Production deploys from an exact commit SHA.

Production VPS

Public applications, workers, edge and TLS, and release management run on the production VPS.

Supabase

Durable database, auth and storage stay on Supabase. Product runtimes do not invent a second source of truth for identity or records.

04 What the system is made of

Products

Studio, LoudAuto, Clipping, Exam, AnswerShift, Usage Panel, LoudForm and ZTC AI. Status lives on Work, not here.

Platform capabilities

Connect Social is a live account permission boundary for Instagram, Facebook and X. It is not counted as a product.

Agents and infrastructure

Agents help plan, implement, review and verify. Infrastructure must keep serving if every agent is offline.

05 Coordination layers

01 / Layer

Buzz

Buzz is a coordination layer for channels, threads, projects and agent activity. It is not a production runtime dependency. Production deploy, rollback and recovery must work without it.

02 / Layer

Hermes

Hermes retains context, routes work packs, and verifies evidence against acceptance criteria. It coordinates the job. It does not replace human release ownership.

06 Plan to verified deploy

01PlanHuman owner sets the outcome. Hermes plans, keeps context and packages a bounded job.

02ImplementWork runs in an isolated Git worktree with explicit acceptance criteria and skills as procedural dependencies.

03Test and reviewTests come before behavior changes. An independent reviewer checks the change. Required CI must pass at the exact commit.

04Deploy and verifyExact-SHA deploy to the production VPS, then health, route and regression verification. Agent summaries are not proof of completion.

Completion controls.

Skills are procedural dependencies for agents. Worktrees keep changes isolated. Regression checks exist so a polished summary cannot replace health, route and product verification.

WriterOne accountable owner per work unit

IsolationWorktree and bounded job pack

False completionBlocked by tests, review, CI and live checks

ReleaseHuman decision after evidence

07 Development inputs

24.47B

Observed tokens

Cumulative model traffic observed during development. This is a build input measurement, not users, customers, revenue, valuation or funding.

~$30K

Approximate build spend

Conservative label for build and infrastructure spend as a development input. Not a funding round or business performance figure.

→ Next

The operating beliefs live in Philosophy.

Build notes also land in Discord

Open Studio →Read Philosophy

How SuperZTbuilds,not a pitch.