RELIANCE RISK PLANE · GATE 0.20.0

Technical evidence for reliance decisions. Not an insurance decision.

Gate 0.20.0 adds a bounded risk plane around the exact authorization lifecycle: customer-owned responsibility terms, declared open-exposure custody, signed technical refusals, period population reconciliation, aggregate receipt census, and externally reported loss experience with correction lineage.

An insurer, auditor, or customer can re-perform those artifacts under independently pinned inputs. EMILIA does not supply the underwriting, legal, coverage, causation, completeness, solvency, adjudication, or payment conclusion.

Run the coverage lab Inspect the shipped proof Scope one protected workflow

WHAT SHIPPED

Five evidence surfaces. None can authorize an action by itself.

RP policy

Loss-allocation schedule

The relying party pins separately signed responsibility terms to the exact Reliance Program. Verification establishes the signed bytes, issuer, status, and program binding—not legal enforceability, coverage, solvency, or payment.

Live control

Open Exposure Ledger

Declared exposure is reserved before provider invocation against configured ceilings. INVOKING and INDETERMINATE stay open; only the configured independent reconciliation authority can close them.

Transaction evidence

Exact-action refusal

A signed refusal binds the action, program, failed requirements, challenge, nonce, custody, and time. It is technical exact-action evidence—not a legal denial, adverse-benefit denial, or coverage decision.

Period evidence

Coverage reconciliation

The attestation signs supplied system-of-record and receipt roots, counts, joins, exclusions, exceptions, and uncertainty for a bounded period. Here “coverage” means declared-population reconciliation, not insurance coverage.

Portfolio evidence

Receipt census + loss feed

The census emits governed aggregate buckets with coarse primary suppression. The signed loss feed preserves external provenance and correction lineage; its observations are not verified or adjudicated losses.

THE CONTROL BOUNDARY

Terms, authority, exposure, outcome, and recourse stay separate.

The loss schedule records customer-supplied terms. Authorization still comes from the existing exact-action evidence and local policy. The Open Exposure Ledger reserves a declared amount before provider entry and preserves uncertainty without granting a retry. Reconciliation accepts authenticated outcome evidence; it does not decide legal loss or policy coverage.

The reference artifacts are open and reproducible: read the architecture contract.

THE PILOT

Start with one exact action and one declared exposure boundary.

For the protected operator

Select one fully mediated action, pin the Reliance Program and authorities, define declared exposure ceilings, and test refusals, uncertainty, reconciliation, and bounded-period evidence before production use.

For the carrier or assurer

Re-perform the supplied artifacts under independently pinned inputs and decide what, if anything, they support for underwriting, control testing, or claims review. EMILIA supplies technical evidence; the relying party keeps the conclusion.

Start a conversation

FREQUENTLY ASKED

Does EMILIA provide insurance or decide coverage?

No. EMILIA is technical enforcement and evidence infrastructure. It does not insure, decide policy coverage, allocate or bear loss, establish liability, adjudicate a claim, or move money.

What does an exact-action refusal prove?

It proves that the signed technical statement binds the named action, program, failed requirements, challenge, nonce, custody, and time under the pinned verification inputs. It is not a legal denial, an adverse-benefit denial, or proof that a refusal was substantively correct.

Does the coverage attestation prove the population was complete?

No. It signs the supplied inventory roots and conserving counts for a bounded period. Completeness needs separate system-of-record evidence. The receipt census also uses only coarse primary suppression, not differential privacy.

Can a carrier verify the artifacts without an EMILIA callback?

Yes. The formats, verifier, vectors, and exact executable claim are public. The current stateful risk-plane and signed risk-artifact implementation is JavaScript; no insurer adoption or external deployment is claimed.

EMILIA does not insure, bear or allocate loss, adjudicate disputes or losses, establish legal enforceability, prove insurance coverage, causation, solvency, or source-population completeness, or move money. Refusal statements are exact technical evidence, not legal or adverse-benefit denials. No external deployment or insurer adoption is claimed.