Skip to main content
PUBLIC DILIGENCE · PRIMARY SOURCES

Check the product, proof, and boundary yourself.

EMILIA sits before configured consequential actions and asks whether this exact action is within customer-controlled authority. This page points buyers, investors, security teams, and machines to the public evidence, including what the evidence does not prove.

Inspect the repositoryReproduce the evidenceReview security
CURRENT CHECKED-IN SNAPSHOT · August 24, 2026
10,013
automated tests
620 test files
35
executable security claims
259 evidence files
332
conformance vectors
21 suites
26
TLA+ invariants
20 verified Tamarin obligations

These values are read from the repository's generated proof summary. They move only when the underlying evidence changes and the generation check passes. They are not customer adoption or certification counts.

THE PRODUCT SHAPE

Proof, control, and assurance stay separate.

Open Protocol

The Apache-2.0 evidence and verification substrate. The posted documents are individual Internet-Drafts, not RFCs or IETF endorsement.

Read the protocol path →

EMILIA Gate

The enforcement product for configured, completely mediated action paths. It checks authority and evidence before an admitted executor attempt.

Inspect the Gate boundary →

Assurance

The evidence-facing layer that packages and re-performs a bounded record. A report or certificate never becomes action authority.

Inspect assurance →
CLAIM BOUNDARY

What we do not ask you to assume.

01EMILIA does not protect an action path that bypasses its configured enforcement boundary.
02It does not claim exactly-once physical execution. Durable admission can bound a protected path to at most one admitted provider attempt, while uncertain outcomes remain INDETERMINATE until authenticated reconciliation.
03Repository-generated tests, models, and security-case evidence are engineering evidence, not an external certification or a guarantee that every deployment is correctly mediated.
04Reference ports maintained by the same team are not independent implementation adoption. The current clean-room acceptance field remains false.
05Individual Internet-Drafts are work in progress. Publication on the IETF Datatracker does not make them RFCs or imply IETF adoption.
RERUN, DO NOT TRUST

The diligence path is executable.

Clone the public repository and run the checked-in evidence gates. The security case and machine context fail when their source artifacts drift.

git clone https://github.com/emiliaprotocol/emilia-protocol.git
cd emilia-protocol
npm ci
npm run check:proof-stats
npm run check:security-case
npm run check:public-conformance-claims
npm run check:llm-context
CANONICAL EVIDENCE SURFACES
Engineering evidenceCurrent proof summary, artifact hashes, and rerun instructions.
ConformancePublic vectors and reference behavior for consequence admission.
Product securityDisclosure, threat boundaries, and current security material.
Repository snapshotA public view of the current verification snapshot.
Machine contextStructured, source-pinned context for agents and diligence systems.
LLM context indexA compact text index that points models to canonical public sources.

Need a source that is not listed?

Ask for the exact artifact or a scoped technical review. EMILIA Protocol, Inc. will distinguish what is public, what is customer-specific, and what does not exist yet.

Request a sourced answer