# CAIN EPICENTER — Value Model

**Internal analytical scenario. NOT an appraisal, NOT a financing valuation, NOT a guarantee.** Every figure maps to
implemented capability and the register method (`scripts/ip/recalculate_ip_value_v21.py`).

## Value classes (kept separate)
- **OBSERVED** — code, tests, live stages, lab/mutation/chaos/benchmark results that exist today.
- **MODELED** — the register-method IP base from those mechanisms.
- **PROJECTED** — company scenarios requiring customers/integration/validation.
- **UNVERIFIED** — anything requiring revenue, patents or third-party validation.

## Incremental IP (modeled)
15 net-new EPICENTER families (6 NOVEL, 5 UNUSUAL, 2 INTEGRATION, 2 ENGINEERING), deployed discount, no arbitrary
multipliers:

| Scenario | Prompt 6-20 base | EPICENTER gross | Net | **Total net** |
|---|---|---|---|---|
| LOW | $2,301,100 | $356,000 | $160,200 | **$2,461,300** |
| BASE | $5,885,700 | $805,000 | $442,750 | **$6,328,450** |
| HIGH | $10,843,500 | $1,275,000 | $828,750 | **$11,672,250** |

Incremental contribution (BASE): **≈ $442,750** net standalone (a breadth count before prior-art review).

## What raises value (evidence, not code)
a paying mission-assurance/outcome-proof customer; a third-party red-team; a real physical pilot; filed provisionals;
incorporation with IP assignment.

## Limits
No patent; pre-revenue (founder-attested $97); no incorporation; physical SIMULATED; mission reliability not a
guarantee; no third-party validation; benchmark is local.
