Product surfaces
The owner workspace — bounded before agents move.
Ship now starts from the product owner view: workspace, policies, knowledge, and evidence. Engineers still get reviewable contracts underneath, but the visible product is built for solo founders and owners first.
The workspace surfaces
Owner-readable · engineer-auditableWorkspace
Connect the product repo, tracker, owner, members, and integrations before automation starts moving work.
Policies
Standing rules for allowed actions, review gates, required evidence, and the moments where a human must decide.
Knowledge
Repo facts, product constraints, customer context, and review notes agents can use without stale chat archaeology.
Evidence
Tickets, pull requests, checks, comments, and Inbox decisions connected into a story a buyer or reviewer can follow.
Two words on policies
Policies are the guardrails, not the bureaucracy.
A policy says what an agent may do, what evidence it must leave, and when it must stop for a human. That is how Ship keeps founder speed without turning the repo into an unsupervised experiment.
Allowed scopeWhich repos, tracker states, files, and automations are in bounds for this workspace.
Review gatesWhich changes require owner approval, code review, test evidence, or a release note before they move.
Evidence rulesWhich ticket, PR, check, comment, or Inbox decision must exist before work can be considered done.
EscalationThe moments where automation stops and asks the founder, product owner, or reviewer to decide.
Looking for something else?
Related surfaces
The product surfaces above are the public entry point. Longer rationale, docs, and field proof live elsewhere on this site.