# E24 — Frontier-20 IP Composition Graph

**Engineering analysis only. No patentability or valuation determination. Counsel required for legal conclusions.**

The defensible assets are **system-level compositions**, not the count of 20 products. Each mechanism
below is implemented, tested, and evidenced in this repository.

## Composition map

| # | Mechanism | Composes | What it does | Evidence | Difficulty |
|---|---|---|---|---|---|
| IC-01 | Governed state as a verifiable object | E20 state × E21 transitions × Merkle roots | every state change is a signed, replayable, witness-bound object | `artifacts/e21/E21_STATE_PROOF.json` | HIGH |
| IC-02 | State-bound execution authorization | E21 state × E22 binding × E8 | authorization is invalid the moment state is stale/rolled back | `artifacts/e22/E22_GATE_RESULTS.json` | HIGH |
| IC-03 | Single-use governed execution permits | E22 permits × E8 permission × MCPGate | one permit, one target, one state root, consumed exactly once | `artifacts/e22/E22_GATE_RESULTS.json` | MEDIUM |
| IC-04 | Compositional authority conservation | E23/E24 authority × product chain | `AUTHORITY_OUT ⊆ AUTHORITY_IN` across the whole chain, machine-checked | `artifacts/e23/E23_FRONTIER_PROOF.json`, `E24_SUBSTRATE_PROOF.json` | HIGH |
| IC-05 | Governance lineage graph | E23 lineage × product transitions | every execution traceable AGENT→…→STATE_UPDATE; orphan/expansion detected | `E23_COMPOSITION_RESULTS.json` | MEDIUM |
| IC-06 | Live E8↔E22 shadow divergence engine | E23 shadow × live gateway | non-blocking quantification of the gap before enforcement | `E23_SHADOW_LIVE.json`, `GET /frontier/e23/shadow` | MEDIUM |
| IC-07 | Real TCP Byzantine transport + fault taxonomy | E21 replay × E23 transport | N=4/Q=3 signed messages; drop/partition/forge/equivocation detected | `E23_DISTRIBUTED_RESULTS.json` | MEDIUM |
| IC-08 | Deterministic replay envelope | E23 replay × E22 external nondeterminism | separates logical / cryptographic / external determinism | `E22_EXECUTION_PROOF.json`, `E23_FRONTIER_PROOF.json` | MEDIUM |
| IC-09 | Shared Frontier substrate envelope + state root | E24 substrate × 20 products | one envelope, attenuation-only; domain-separated state dimensions | `E24_SUBSTRATE_PROOF.json` | MEDIUM |
| IC-10 | Machine-validated composition graph | E24 graph × architecture | rejects observation/evidence/reputation→authority and product→execution bypass | `E24_GRAPH_RESULTS.json` | MEDIUM |
| IC-11 | Policy composition with deny dominance | E24 policy × multi-product policy | intersection + deny dominance + contradiction/shadow/gap detection | `tests/e24/test_e24_core.py` | LOW-MEDIUM |
| IC-12 | Epistemic risk fusion | E24 risk × VIGIL/Twin/Cartel | segregates observed/predicted/simulated; never averages into authority | `tests/e24/test_e24_core.py` | MEDIUM |
| IC-13 | Frontier conformance engine | E24 conformance × 20 products | common governance contract test, machine-readable | `E24_CONFORMANCE_RESULTS.json` | MEDIUM |
| IC-14 | Zero-CAIN-import clean-room verification | verification/e2{1,2,3,4} | independent recomputation of state/authority/lineage/certificate proofs | all proof bundles | HIGH |

## Why composition matters
Individually, each mechanism is a well-understood building block (state roots, permits, Merkle proofs).
The defensible difficulty is in making them **agree**: the state root that E21 commits must be the one
E22 binds, the one E23 conserves authority across, and the one an independent verifier recomputes.
Divergence anywhere invalidates the whole proof — which is precisely what the invariants and
clean-room verifiers check.

## What remains unproven
- Multi-host (independent failure domains) behaviour — NOT_MEASURED.
- ENFORCING promotion — NOT_DEPLOYED.
- Full 20-product execution matrix — NOT_EXECUTED.
- Independent third-party verification — NOT_MEASURED.
