# Operating Model

## Purpose

This operating model defines how `whynot-control` is used to explore prototypes, collect feedback, and identify market signals without creating premature commitments.

## Core Rules

### 1. Prototypes are questions

Each prototype should express a question about usefulness, desirability, feasibility, or willingness to pay.

### 2. Signal beats enthusiasm

An idea should not be promoted only because it is exciting. It should show some kind of signal.

### 3. Low-cost learning first

Before committing to production, prefer sketches, mockups, demos, landing pages, conversations, and small experiments.

### 4. Closed beta before broad launch

If an idea needs real users, use controlled participation before public exposure.

### 5. Promotion requires criteria

A prototype should move to Helix, Coulomb, Sloppers, Plenitude, Binky, or Tegwick only when explicit promotion criteria are met.

## Work Classes

| Class | Meaning |
|---|---|
| Raw Idea | Captured but not structured |
| Prototype Candidate | Worth shaping into a test |
| Experiment | Has a learning question and method |
| Signal | Evidence from users, behavior, feedback, or willingness to pay |
| Beta | Controlled test with selected users |
| Promotion Candidate | May deserve productization |
| Parked | Interesting but inactive |
| Rejected | Intentionally not pursued |

## Prototype Lifecycle

```text
Raw Idea
  → Prototype Candidate
  → Experiment
  → Signal Review
  → Park / Iterate / Promote / Reject
```

## Burnout Guardrail

A prototype can be interesting and still be parked.

`whynot` exists to reduce uncertainty, not to create more obligations.