Managed re-performance
We re-run the open verifier over the supplied population using explicitly pinned keys, profiles, clocks, and input digests. Runtime claims are compared, never trusted.
EMILIA ASSURANCE PLANE
Re-perform the evidence. Do not trust the dashboard.
Gate produces the operating evidence. The Assurance Plane independently re-runs the open checks under pinned inputs, records any drift, and assembles work a customer’s auditor, regulator, or underwriter can reproduce.
Protocol proves. Gate prevents. Assurance re-performs.
WHAT THE PAID PLANE DOES
Evidence operations above the open verifier.
Verification stays free and reproducible. Customers pay for disciplined execution: pinning the inputs, re-performing the population, preserving the record, monitoring drift, and preparing the handoff.
Versioned conformance records
A signed record binds the implementation, source revision, vector bundle, procedure, and result. Divergence remains visible instead of being rounded into a pass.
Continuous evidence
Scheduled evidence-head capture, repeatable checks, and drift reporting turn a point-in-time control test into a traceable operating record.
Audit and underwriter packages
Portable workpapers summarize the population, refusals, exceptions, integrity warnings, and control operation. The auditor or underwriter keeps the conclusion.
RUNNING ARTIFACTS
The service is grounded in code a third party can inspect.
ep-assureCLI for building and independently re-performing an assurance package.EP-ASSURANCE-PACKAGE-v1Content-addressed bundle of decisions, evidence, pinned profile, and stated runtime verdicts.EP-GATE-REPERFORMANCE-v1Independent hash-chain, receipt, signoff, quorum, and reported-count recomputation.EP-EXTERNAL-VERIFICATION-STATEMENT-v1Signed, input-pinned statement of what an outside verifier ran and where it diverged.Auditor workpaperReproducible technical procedure and evidence fields for a control test.EP-GATE-UNDERWRITER-ATTESTATION-v1Deterministic operating-control package with explicit exclusions and integrity warnings.OPEN VERIFICATION
The customer never has to trust an EMILIA-only verdict.
The package, verifier, vectors, and procedure are public. A customer, audit firm, insurer, regulator, or competitor can rerun the same inputs without an EMILIA account or server in the verification path.
Inspect the open Protocol# Build or re-perform a package locally npx -p @emilia-protocol/gate \ ep-assure evidence.json --strict # Machine-readable workpaper npx -p @emilia-protocol/gate \ ep-assure evidence.json --json
WHAT IT CAN ESTABLISH
A reproducible technical record.
- The supplied package digest matches its contents.
- Evidence verifies under the explicitly pinned keys and profiles.
- Recomputed results agree or drift from the runtime’s stated results.
- The named conformance procedure produced the recorded result on the pinned inputs.
- Exceptions and integrity warnings remain visible in the handoff.
WHAT IT DOES NOT ESTABLISH
No borrowed authority.
- No accredited certification or public certification mark is currently issued.
- No audit opinion, legal-compliance conclusion, insurance coverage decision, or regulatory approval.
- No proof that withheld events were included unless the population is bound to an external checkpoint.
- No judgment that an authorized action was wise, lawful, safe, or successful.
- No guarantee beyond the system boundaries and evidence actually examined.
INDEPENDENT CERTIFICATION
A partner path, not a claim we make today.
Independent certification belongs with qualified third parties and future multi-stakeholder governance. Any future EMILIA conformance program must use the same public vectors, published procedures, and uniform criteria available to every implementer. EMILIA can prepare and re-perform the technical record; the independent partner decides what conclusion, if any, it supports.