# Beta Model

## Purpose

This document defines how `whynot` uses closed betas and early access experiments.

## Beta Principles

- Keep betas small.
- Be explicit about what is being tested.
- Do not promise production maturity.
- Capture feedback in a structured way.
- Avoid payment or investment mechanics unless Binky and Plenitude are ready for the legal/commercial implications.

## Beta Types

| Type | Purpose |
|---|---|
| Conversation Beta | Test concept in discussion |
| Concierge Beta | Deliver value manually before automation |
| Prototype Beta | Let users interact with a rough implementation |
| Community Beta | Test whether a group wants to gather around a topic |
| Offer Beta | Test whether a service/package has buyer interest |

## Beta Entry Criteria

A beta should have:

- a named prototype;
- a target audience;
- a clear learning question;
- a feedback capture method;
- a defined end condition.

## Beta Exit Outcomes

- Promote.
- Iterate.
- Park.
- Reject.
- Convert to offer exploration.