# CAIN VIGIL — 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_v18.py`).

## Value classes (kept separate)
- **OBSERVED** — code, tests, live stages, measured benchmarks 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 certification (none today).

## VIGIL incremental IP (modeled)
12 net-new, evidence-backed families (V-01..V-12), deployed discount, no arbitrary multipliers:

| Scenario | Prompt 6–17 base | VIGIL gross | Net | **Total net** |
|---|---|---|---|---|
| LOW | $1,753,450 | $368,000 | $165,600 | **$1,919,050** |
| BASE | $4,374,850 | $830,000 | $456,500 | **$4,831,350** |
| HIGH | $8,103,750 | $1,245,000 | $809,250 | **$8,913,000** |

Incremental VIGIL contribution (BASE): **≈ $456,500** net standalone.

## Development replacement value (rough)
≈ 13 modules + tests + lab + docs ≈ a few engineer-months; the modeled IP base is far larger because it prices the
*mechanisms*, not the hours — treat the modeled figure as scenario input, not money.

## Company scenario (projected)
Investor/strategic premiums and founder paper equity are in the recalc JSON; all require customers/validation.

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

## Limits
No patent; pre-revenue; no incorporation; prediction heuristic; physical SIMULATED.
