Home/Docs/Workflow, artifacts, and gates
Plan and build

Workflow, artifacts, and gates

The pipeline combines specialist teammates, deterministic checks, durable documents, and one decision that stays with you: production. The crew locks the plan and visual direction, then starts the build. Approving a plan is not approval to publish.

CURRENT PRODUCT CAPABILITIES
01

Plan

Planning covers market opportunity and competitor evidence, search feasibility, product strategy, monetization, trust/compliance boundaries, route and copy freeze, and a merged product plan. Pricing and compliance can run in parallel after the brief.

Studio market research view showing coverage, evidence counts, freshness, and lanes marked done, partial, or no data.
Missing or stale data is never written as zero demand. Partial and no-data lanes stay labeled.
02

Build and audit

After the crew locks the plan, Shipsite prepares infrastructure and design evidence, generates the site and required backend contract, publishes a managed preview, then runs deterministic and rendered-page quality checks. Static checks and model work are shown separately; not every stage spends model credits.

03

Your approvals

Protected transitions require a decision tied to the exact document or version under review. A rejection returns work to the responsible stage with your reason; it is not a dead end.

04

Documents are the handoff

Research packs, strategy and risk contracts, route/copy freezes, design handoffs, source versions, screenshots, quality-check reports, deployment manifests, usage receipts, and review verdicts remain versioned. Later agents and humans use them to see what changed and why.

Studio project library listing the current product plan, SEO copy, pricing contract, research, and design evidence.
Artifacts stay versioned in the library. Open the exact document behind an approval instead of deciding from a status badge.