Vision
AIEP exists because every significant failure in modern organisations shares a structural flaw: a decision was made but the evidence behind it was not preserved with the decision. AIEP fixes this at the protocol level — not for one organisation, for the web.
What the web should be
The web is a publishing system. At its core it answers one question: where is this document? AIEP adds the question underneath: is this document true, current, and backed by evidence?
The goal: a web where every published claim answers four questions automatically — without a human intermediary:
| Question | How AIEP answers it |
|---|---|
| Who published this? | Signed issuer identity cryptographically linked to a registered publisher |
| Has this changed? | Hash binding — any alteration after publication breaks the hash |
| What evidence supports it? | Evidence references are part of the artefact, not a footnote |
| Is it still current? | Temporal validity — expiry and validity windows are machine-readable fields |
Three areas explored here
Vision — the full statement
The founding insight. Why the AI imperative changes the timing. The recall vision — why preserving dissent is not a technical feature but a philosophical commitment about how knowledge grows. The network effect.
A protocol that any publisher can implement, any retriever can use, and any auditor can verify — permanently, deterministically, and without permission.
Why now
The regulatory and technical moment: AI governance legislation, the model retrieval shift. The window in which protocol standards get established is narrow. Why the timing of AIEP’s launch is deliberate.
If AIEP succeeds
What the world looks like when AIEP is widely adopted: the web becomes verifiable, AI becomes more reliable, search becomes retrieval, compliance becomes automated. Concrete scenarios for regulated sectors, open knowledge infrastructure, and global governance.
The recall commitment
| Knowledge state | Meaning | What happens to it |
|---|---|---|
CONSENSUS | Supported by current evidence above threshold | Fully operative |
OUTLIER | Below consensus threshold | Preserved in dissent archive with full evidence chain |
RECALLED | Previously outlier — restored by new evidence | Re-enters operative state with recall record attached |
SUPERSEDED | Explicitly replaced by a later artefact | Preserved but marked inactive |
This is not a technical feature. It is a philosophical commitment about how knowledge grows. Many ideas that are wrong today will be correct tomorrow when new evidence arrives. AIEP preserves that possibility.
The long-term position
AIEP is designed to be the evidence layer of the web — as foundational as HTTP, as open as TCP/IP, as verifiable as cryptographic signatures.
Not owned by one organisation. Not controlled by one registry authority. Not restricted by geography or jurisdiction.
→ Read the full vision statement
The architecture is already working
The vision above describes a web that does not yet exist. Piea demonstrates that the substrate that would power that web already does.
Piea is a production AI assistant running on the complete AIEP Piea Surface architecture. Its Evidence Rail, Dissent Signal Engine, Replayable Reasoning Chain, and Semantic Branch Detection are not future capabilities. They are running now, on Cloudflare’s global edge, producing cryptographically committed outputs that are independently replayable.
The architecture is not theoretical. It is deployed.
Related
- Piea — the AIEP architecture in production
- About AIEP — what AIEP is and who governs it
- Architecture — the seven-layer technical stack
- The AIEP Canon — the eight primitives the web has been missing
- Use Cases — real-world deployment scenarios