# Scoring Rubric

Use this only after the crypto necessity gate passes.

## Scoring Dimensions

Score each idea from 0 to 3 on each dimension:

- `founder_fit`
  - 0: no edge
  - 1: weak adjacency
  - 2: real domain fit
  - 3: unfair advantage
- `mvp_speed`
  - 0: multi-month build
  - 1: 3-4 weeks
  - 2: 2 weeks
  - 3: under 1 week
- `distribution_clarity`
  - 0: "anyone"
  - 1: broad segment
  - 2: specific reachable community
  - 3: first ten users are obvious
- `market_pull`
  - 0: no real signal
  - 1: weak anecdotal signal
  - 2: active complaints or ugly workarounds
  - 3: clear usage or people paying bad alternatives
- `revenue_path`
  - 0: no monetization story
  - 1: hand-wavy monetization
  - 2: credible pricing path
  - 3: clear buyer and pricing logic

## Ranking Logic

Prioritize in this rough order:

1. founder fit
2. speed to MVP
3. distribution clarity
4. market pull
5. revenue path

Do not let a high market size score rescue a weak wedge.

## Shortlist Diversity Rule

The top three should not all be the same product shape.

When possible, vary across:

- infra vs app-layer
- B2B vs consumer
- protocol-facing vs end-user-facing
- fast tactical wedge vs deeper platform play

If all three finalists land in the same bucket, say why the category forced that outcome.

## Required Bear Case

For each shortlisted idea, write:

- one sentence on why it could fail
- one sentence on why it still survives the cut
