Skip to main content
05 / Re-perform / Assurance Plane

Later, rerun the evidence and make drift visible.

The Assurance Plane implements procedures for checking many packets over time. It repeats chosen checks, exposes drift and unresolved cases, and prepares a scoped workpaper. Any deployment or service engagement must be separately scoped.

Provide implemented procedures for re-performance across a supplied deployment or population.

Discuss a scoped assurance pilotRun the open procedure
Claim boundary: EMILIA supports the procedure. It does not issue an audit opinion, accredited certification, legal conclusion, or insurance decision.
IMPLEMENTED PROCEDURES

Evidence operations above the open verifier.

Verification stays free and reproducible. The repository implements procedures for pinning inputs, re-performing a supplied population, preserving the record, exposing drift, and preparing a technical handoff. A pilot or service engagement must be separately scoped.

Independent re-performance

The procedure reruns the open verifier over a supplied population using explicitly pinned keys, profiles, clocks, and input digests. Runtime claims are compared, never trusted.

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.

Repeatable evidence checks

Repeated evidence-head capture, checks, and drift reporting can turn supplied point-in-time inputs 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 procedure is grounded in code a third party can inspect.

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.