# CAIN-42 — Master Frontier-20 Model

All 20 products are deployed on the live cluster and reachable at `/fabric/<prefix>/status`.
Evidence: `artifacts/e20/E20_FLEET_EVIDENCE.json` (20/20 reachable, 20/20 `operational`).

| # | Product | Route | Live |
|---|---|---|---|
| 1 | OpenShell Gateway | `/fabric/openshell/status` | 200 |
| 2 | MemVault | `/fabric/memvault/status` | 200 |
| 3 | VIGIL PRM | `/fabric/vigil/status` | 200 |
| 4 | SCITT Clearinghouse | `/fabric/scitt/status` | 200 |
| 5 | Hardware Sentry | `/fabric/hardware-sentry/status` | 200 |
| 6 | RIG Identity | `/fabric/rig/status` | 200 |
| 7 | Digital Twin | `/fabric/digital-twin/status` | 200 |
| 8 | Exploit Shield | `/fabric/exploit-shield/status` | 200 |
| 9 | Epistemic Quorum | `/fabric/epistemic-quorum/status` | 200 |
| 10 | Steganography Firewall | `/fabric/steganography/status` | 200 |
| 11 | Proof-Carrying Code | `/fabric/pcc/status` | 200 |
| 12 | Speculative Fast-Forward | `/fabric/speculative/status` | 200 |
| 13 | Cartel Detector | `/fabric/cartel/status` | 200 |
| 14 | PolicyForge | `/fabric/policy-forge/status` | 200 |
| 15 | Actuation Guard | `/fabric/actuation/status` | 200 |
| 16 | zkAgent | `/fabric/zk/status` | 200 |
| 17 | PathCorrection | `/fabric/path-correction/status` | 200 |
| 18 | LatentGuard | `/fabric/latent-guard/status` | 200 |
| 19 | SwarmGossip | `/fabric/swarm-gossip/status` | 200 |
| 20 | CXL-Sentry | `/fabric/cxl-sentry/status` | 200 |

## Honest hardware classification (per product self-report + prior forensic audit)

- **SOFTWARE_ONLY / KERNEL:** OpenShell (genuine `prctl`/RLIMIT), RIG, SCITT, MemVault, VIGIL,
  Exploit Shield, Epistemic Quorum, Steganography, PolicyForge, Cartel, PathCorrection, LatentGuard,
  SwarmGossip, Digital Twin, Speculative.
- **EMULATED / NO_HARDWARE:** Hardware Sentry (Linux netfilter, no DPU), CXL-Sentry (software range
  check, no CXL device).
- **SIMULATED:** Actuation Guard (kinematic model, no CAN bus), zkAgent (algebraic reference,
  not a zkVM), Proof-Carrying Code (bounded-arithmetic SMT, not arbitrary code proof).

A 200 from `/status` asserts none of the above; it asserts the route responds.
