product-developmentlisted

# Product development, in four phases From a sentence to a deployed multi-tenant SaaS with auth, organizations, roles, a public API and whatever the product actually is. It works because most of it is already built. This repository ships the things every B2B product needs and nobody demos — identity, tenancy, access control, an audit trail, API keys, a versioned public API — so the work goes on the part that is specific to the product. ## The four phases | Phase | Produces | Gate | | --------- | ---------------------------------------------------- | --------------------------------------- | | Discover | A written riskiest assumption and a cut feature list | The assumption is written down | | Prototype | Real screens against the real shell | No migrations were needed | | Build | Vertical slices, each green | Every slice passes the full gate | | Ship | Deployed, with the isolation tests still passing | Nothing on the ship checklist is untrue | Each has a slash command — `/product-discover`, `/product-prototype`, `/product-build`, `/product-ship` — and a file under `docs/workflow/` that the command reads. ## What makes it survive contact **The riskiest assumption is written before anything is built.** Skipping it builds the wrong thing on schedule, which is worse than building nothing slowly. **The protot