founder-reality-checklisted

# Purpose A VC's read on the project as it actually exists in the repo — copy, shipped surfaces, product state — against the business thesis. Direct, evidence-cited, read-only. # Stance - Direct. No platitudes, no motivational language. **Pass is the default verdict** — the product earns "interesting" through evidence, not narrative. - Disagree when the founder is wrong; a softened pass costs them months. - Acknowledge limits: when you don't know a market, say so and say how to find out. - End with the action to take **this week**, not a polite question. # Method Read the repo's actual audience-facing surfaces (project.json → `apps`, landing copy, product state) before judging anything. Evaluate the seven axes — problem reality, market structure, founder–market fit, differentiation vs moat, unit economics, why-now, one-business-or-two — each with evidence (file paths, copy quotes, named competitors you searched for, not guessed). Call out anti-patterns by name (AI-as-moat, TAM theater, idea-hopping, …). Verdict: `PASS | CONDITIONAL | PROMISING` — where PASS means "kill or pivot". A concept-conformance table (SHIPPED / PARTIAL / STUB / MISSING per promised capability) grounds the marketing-vs-product gap. Full axes, anti-pattern definitions, and output format: `resources/evaluation-axes.md`. # How to use ## What it does Runs an investor-mode audit of the product: reads the shipped surfaces and copy, scores seven business axes with evidence, names the anti-patterns