venture-newlisted

# Venture New Target venture directory: `$ARGUMENTS` If no target was supplied, use the active workflow's explicit venture directory; only default to `ventures/<slug>/` when the context is unambiguous. Read `framework/methodology.md`, `framework/stages.md`, `framework/evidence-standard.md`, and `templates/venture.yaml`. ## Goal Create a minimal, falsifiable venture definition without pretending we know more than we do. ## Target directory Eval runs may intentionally use a directory under `evals/runs/<run-id>/venture/`; do not relocate them into `ventures/`. ## Workflow 1. Identify the target venture directory. 2. If it does not exist, create: - `research/` - `decisions/` - `experiments/` - `learning/` 3. Create or normalize `venture.yaml` using the version 2 template. 4. Convert the idea into: - problem hypothesis; - primary ICP hypothesis; - current alternatives hypothesis; - solution hypothesis; - business model hypothesis; - distribution hypothesis. 5. Before writing ICP-scoped assumptions, inspect whether the proposed primary ICP bundles two or more populations that could differ on the quantities the assumptions will turn on (for example buying process, campaign cadence, data availability, price sensitivity, regulation, operational workflow, or retention). If so, either split them into distinct segment labels or record in the thesis why treating them as one segment is causally justified. Do not use one broad `primary-icp` label merel