AIEP — One Page Explainer
AIEP (Architected Instruction & Evidence Protocol) is a protocol that links instructions to evidence and publishes knowledge artefacts in a way machines can retrieve and verify.
The future of information retrieval is not search. It is evidence-backed knowledge retrieval.
The problem in one sentence
The web is full of assertions. Almost none of them carry their evidence. Machines retrieving from the web cannot tell the difference between a well-evidenced claim and a confident guess.
What AIEP does
| Capability | What it means in practice |
|---|---|
| Links instructions to evidence | Every claim carries a reference to the artefacts that support it — not as a footnote, but as a machine-readable, hash-verified field |
| Publishes structured artefacts | Knowledge is published as schema-conformant JSON under /.well-known/aiep/ so any AI system can retrieve and validate it |
| Makes provenance machine-readable | Who published it, when, what hash it carried at publication — all encoded in the artefact, not inferred from the page |
| Preserves dissent | Outlier claims are archived with their evidence intact rather than discarded — ready for recall when knowledge shifts |
| Gates execution on evidence | Before acting on a claim, a conformant AI system checks plausibility (registry-verified) and probability certification (fail-closed tail-risk bound) |
| Operates at hardware level | The GENOME kernel enforces four constitutional invariants at the execution substrate — evidence binding, hash parity, plausibility clearance, dissent completeness |
The stack at a glance
| Layer | What it does | Key patents |
|---|---|---|
| Web surface | Machine Mirror at /.well-known/aiep/ — discoverable by AI retrieval systems | GB2519711.2 |
| Evidence ecosystem | Normalisation, stitching, temporal gap detection, cross-domain evidence | P10–P30 |
| Admissibility gate | Plausibility matrix + probability certification + quantum alignment — fail-closed | P02, P03, P04 |
| Constitutional stack | GoalVector commitment, recall engine, compliance certification, chip governance | P22, P37–P94 |
| Cognitive continuity | Cross-session patterns, swarm coordination, moral substrate | P95–P103 |
The retrieval difference
| Without AIEP | With AIEP |
|---|---|
| Retrieve text from a page | Retrieve a structured artefact with schema conformance |
| Infer credibility from SEO rank | Verify provenance via issuer DID and hash |
| No evidence reference | Evidence chain encoded in the artefact |
| No admission control | Plausibility gate and probability certification before execution |
| No audit trail | Every action traceable to artefact, evidence, and GoalVector |
| Outliers discarded | Outliers archived with evidence for potential recall |
Adoption is layered
You do not need to implement everything at once. The three meaningful starting points:
| Starting point | What you publish | What you gain |
|---|---|---|
| Discoverable | index.json + metadata.json at /.well-known/aiep/ | AI systems can find and identify you |
| Verifiable | Artefacts with evidence references, hashes, schema conformance | Retrievers can validate your claims |
| Certified | Registry listing + certificate artefacts + compliance signals | Machine-verifiable “AIEP Certified” claim |
Open by default
- Protocol specification: public
- Canonical schemas: public
- P66 / P67 declaration formats: Apache 2.0
- Open-source codebase: Apache 2.0
- Open adoption: no registration, no fee, no permission required
- “AIEP Certified” claim: requires registered issuer and certificate artefact — fail-closed
The patents (9 filed November 2025; 9 filed 07 April 2026; 6 filed 08 April 2026 — 24 total, all GB numbers confirmed; UK IPO) protect the novel architectural layers. They do not restrict open adoption, the open-source tooling, or the schemas.
Where to go next
| Goal | Start here |
|---|---|
| Understand the full architecture | Architecture |
| See AIEP in practice | Use cases |
| Implement a Mirror | Quickstart |
| Understand the trust model | Security |
| See the patent coverage | Patents |
| Explore the access tiers | Access Tiers |