company-initlisted

# /company-init - found the company (greenfield, autonomous) Found this project's AI software company. The owner is the client: they state what they want built; the company generates everything else itself. The output is a project where `/orchestrator` immediately runs real work. ## 0. Verify the drop-in `company/METHOD.md`, `ORCHESTRATOR.md`, `.claude/agents/`, `.claude/hooks/` must exist (installer). If not: stop, point at `install.sh`. ## 1. The one question (at most) If the user's request or session context already says what we are building, ask NOTHING - proceed. Otherwise ask exactly one question: "What are we building, and for whom?" Every other founding decision is made by the company with opinionated defaults, recorded where the owner can veto: - Stack: architect picks the boring, dominant choice for the domain. - Scope: PM drafts v1 aggressively small; everything else becomes backlog. - Business-policy OQs: PM sets a fallback, logs to `company/state/DECISIONS.md` as owner-pending; the build proceeds on fallbacks. ## 2. Found it (dispatch, in order) 1. **product-manager**: founding spec in `company/specs/` - v1 with FR/BR IDs, OQ register with fallbacks, spec-ready checklist walked honestly. 2. **architect**: narrow waist, ownership map, wave plan with hard exit criteria, frozen-surface entries, gate ladder proposal. 3. **You (CEO)** review both, then wire the ground truth yourself: - surfaces into `company/frozen-surfaces.json` - gates into `co