# E26 — IP Forensic (engineering inventory)

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

| IP-ID | Name | Problem | Mechanism | Evidence | Difficulty |
|---|---|---|---|---|---|
| E26-IP-01 | Byzantine governance settlement | one process claiming "it happened" is not global settlement | cryptographically-bound settlement of the full lifecycle with authority-conservation + epistemic-safety construction laws | `E26_SETTLEMENT_PROOF.json` | HIGH |
| E26-IP-02 | Distributed control-loop certification | verifying a single control loop ≠ verifying it across nodes | settlement certificate binding state/authority/action/execution/outcome/deviation/authority-delta/settlement-root/quorum | `E26_SETTLEMENT_PROOF.json` | HIGH |
| E26-IP-03 | Authority double-entry accounting | authority must not appear from nowhere | debit/credit ledger with conservation proof (`credits == debits + remaining`) | `E26_ACCOUNTING_RESULTS.json` | MEDIUM |
| E26-IP-04 | Distributed authority conservation | Byzantine nodes / majority must not inflate authority | `authority_after ⊆ authority_before ∪ authority_granted`, enforced at settlement construction | invariant I133 | MEDIUM |
| E26-IP-05 | Cross-node causal lineage | an action must trace principal→…→settlement | 14-kind ordered lineage with deterministic hash; detects impossible/temporal/identity/authority gaps | `E26_LINEAGE_RESULTS.json` | MEDIUM |
| E26-IP-06 | Epistemically safe reconciliation | majority ≠ truth | conflict classification + evidence/independence ranking; ties escalate; non-observed never settles observed | `E26_RECONCILIATION_RESULTS.json` | HIGH |
| E26-IP-07 | Outcome-bound settlement | outcome must bind to execution | settlement refuses missing/contradictory outcome; predicted/simulated/unknown refused as observed | invariants I135/I137/I143 | MEDIUM |
| E26-IP-08 | Governance-state settlement roots | reproducible settlement identity | canonical settlement root over sorted fields; deterministic replay reconstructs it | `E26_SETTLEMENT_PROOF.json` | MEDIUM |
| E26-IP-09 | Composition authority envelopes | combining products must not expand authority | composition selection bounded by granted set (E24/E25 reuse) | invariant I151 | MEDIUM |
| E26-IP-10 | Clean-room settlement verification | don't trust the runtime | zero-import verifier reconstructs roots/quorum/lineage/certificate/epistemics; positive+negative | `tools/e26/e26_verify.py` | HIGH |
| E26-IP-11 | Negative-knowledge regression architecture | refusals are the asset | NK corpus mapped to regression tests | `docs/e26/NEGATIVE_KNOWLEDGE.md` | MEDIUM |
| E26-IP-12 | Distributed recovery without authority resurrection | recovery must not restore revoked authority | recovery suite + settlement refusal | invariant I160 | MEDIUM |

## Prior-art questions
Two-phase commit, quorum certificates, Merkle provenance, and BFT consensus are individually known.
The candidate is the **composition**: a settlement object whose construction is *refused* unless
authority is conserved, epistemics are separated, lineage is complete, evidence resolves, and quorum is
valid — and which an independent verifier can reconstruct without the runtime.

## What is NOT proven
Multi-host settlement, long-duration soak behaviour, and independent third-party verification.
