# CAIN CRUCIBLE — Production Readiness

| Capability | Status | Evidence |
|---|---|---|
| ControlObject + effectiveness state | IMPLEMENTED, TESTED | `cain/crucible/control.py` |
| ProofOfControl | IMPLEMENTED, TESTED, LIVE | `proof.py`; `crucible_proof` stage |
| Effect-level validation | IMPLEMENTED, TESTED | `challenge.py` |
| Governance attack graph | IMPLEMENTED, TESTED | `attackgraph.py` |
| Challenge engine + adversarial agents | IMPLEMENTED, TESTED | `challenge.py` |
| Adaptive adversary | IMPLEMENTED, TESTED | `challenge.py` |
| Governance chaos | IMPLEMENTED, TESTED | `chaos.py` |
| Control regression registry | IMPLEMENTED, TESTED | `regression.py` |
| Continuous control validation | IMPLEMENTED, TESTED | `regression.py` |
| Evidence independence | IMPLEMENTED, TESTED | `evidence.py` |
| Canary effects | **SIMULATED** | `challenge.py` |
| 3 hosted stages | **LIVE** (RESTRICTION_ONLY) | `hosted_stages.py`; `default_stages_v18` |
| HTTP surface | IMPLEMENTED, TESTED | `platform-gateway/routers/crucible.py` |
| Real production control attacked | **NOT IMPLEMENTED** | canaries + harness only |
| Third-party red-team | **NOT IMPLEMENTED** | none |

## Known limitations / blockers
1. Challenges run against canary/harness paths, not live production effects.
2. No third-party red-team or independent validation; the lab and mutations are self-defined.
3. No long-duration continuous-validation soak.

## Deployment stages
OFF → OBSERVE → SHADOW → CANARY → RESTRICTION_ONLY (current) → ENFORCED. CRUCIBLE never attacks production effects
without an explicitly governed safe test mode; the hosted stages can only add a refusal and abstain otherwise.
