# Product thesis

## Position

Web Studio is a process product for people using Claude Code to create
marketing, portfolio, launch, dashboard, or editorial websites. It is not a
template library and not a claim that one agent can replace a studio.

Its thesis is simple:

> Model quality matters less when the order of decisions is wrong. Commit
> direction before production, constrain execution with artifacts, separate
> aesthetic authority from mechanical review, and make completion auditable.

## The user problem

AI website generation commonly collapses briefing, art direction, production,
and review into one conversational stream. That creates predictable failure:

- the model starts building before choosing a point of view;
- the visual system rationalizes output instead of governing it;
- the builder reviews its own assumptions;
- optional media spend happens before a coherent plan survives review;
- “done” means locally rendered, with no receipt of what ran.

## The product answer

Web Studio divides work into nine stages and three authority classes:

1. Art direction owns the concept, visual system, and final craft judgment.
2. Production owns execution against the signed system.
3. Mechanical review owns cost, links, measurable defects, and consistency.

Artifacts—not conversational memory—carry truth between those seats. The
direction brief, `DESIGN.md`, project gate, JSONL run log, browser findings,
job log, deploy URL, and cost receipt each make a particular claim inspectable.

## Value

The workflow is designed to improve differentiation, cost control,
recoverability, and trust without requiring a custom runtime. Its value is the
discipline of the seams: creative authority does not leak into review, optional
tools do not become silent prerequisites, and a failed late stage does not
erase earlier assets or decisions.

## Maturity

The current repository is an experimental workflow with a witnessed core.
Gate, run-ledger, installer, and browser-report behavior have automated tests;
live Claude deny/allow, served-browser, separate-model mechanical review, and one
complete deployed Signal Desk recovery/release run have dated receipts. The nine-stage runner
remains an instruction and audit contract rather than a durable state machine.
Paid-media integration and unrelated-operator adoption remain unclaimed.

## Success criteria

Web Studio should be considered adoption-ready when an unrelated operator can:

- independently install it from a clean environment;
- reproduce the witnessed direction-gate boundary;
- complete a separate real project through all nine stages;
- understand every degraded mode from the receipt alone;
- reproduce the measurable review;
- recover from a failed render, build, review, or deploy without restarting.