Product model

Choice: A Workspace is the company's access and billing boundary. A Product is a durable thing built and operated; it can span many repos, which act as one. A Team is people who own work and set their own rules. A Space is a knowledge area for a team, the company or several products, such as Billing, HR or Marketing; it links to pages, which stay in their source repos. Work: Problems, ideas, experiments, plans, features and bugs are work items. Work moves through stages; a Product has no lifecycle of its own. Shipped and failed work is kept, with its outcome. Workflow: one default pipeline per Product. Add a named pipeline only for recurring work with different steps; each piece of work follows one, and a pipeline is assigned to work, not to a Space. Rule layers: Canon, organization, product, team, repo, machine; the closest wins unless locked. Why: a small product stays simple, while one company can hold many products, teams and shared knowledge without treating every business function as a product. Rejected: Space means Product · Product status mixing Problem, Ideas, In Progress, Live and Discarded · copied docs across Spaces · multiple pipelines by default. Now: canon-cli 0.27.0 has products, teams, named pipelines and rule layers. Cloud still uses Workspace → Space-as-product → Repo until its refactor. Revisit: when onboarding shows a repo shared by products, or teams needing separate access inside one Space.