Roadmap

AIEP is designed to be adopted in phases. Each phase adds capabilities without invalidating earlier adoption. The protocol must remain usable while the ecosystem grows.

PhaseWindowStatusFocus
Phase 1Q4 2025CompleteHub live, machine endpoints published, protocol public
Phase 2Q1–Q2 2026ActiveMirror adoption, first publisher integrations
Phase 3Q3 2026PlannedVertical exemplars in production
Phase 4Q4 2026 onwardsPlannedEcosystem growth and governance maturity

Phase 1 — Q4 2025 — Complete

The first milestone is a clear public Hub that explains the vision, publishes the governance stance, and exposes the machine endpoints under /.well-known/aiep/. This phase makes AIEP discoverable and lets AI systems inspect the protocol from the source itself.

Delivered: Hub live · machine endpoints published · protocol specification public · 9 GB patents filed · 21 open-source repositories published under Apache 2.0


Phase 2 — Q1–Q2 2026 — Active

The second milestone is adoption. Organisations publish Mirror endpoints and knowledge artefacts start to exist in the places where they originate.

Delivered in Phase 2:


Phase 3 — Q3 2026 — Planned

With Phase 2 delivering complete end-to-end reference implementations across Piea (AI knowledge), Forecast (construction intelligence), QARDL (verifiable identity), and AIEP Miner (hardware governance), Phase 3 is the ecosystem shift: from controlled reference implementations to independent third-party adoption. The protocol moves from demonstrated to adopted.

Target: First third-party certified publisher · regulated sector deployments · Piea enterprise programme launch


Phase 4 — Q4 2026 onwards — Planned

Once the publication pattern is demonstrated, the ecosystem can expand. More publishers, more artefacts, more validated schemas. Developers build tools that validate and retrieve artefacts. Institutions and enterprises adopt AIEP for their own domains.

The roadmap remains open because AIEP is open: open use is always permitted. The goal is not to control the web. The goal is to make verifiable knowledge publishing normal.


Extension layer repositories — Phase 3 targets

These open-source repositories implement extension layers above the frozen kernel. Each is independently adoptable. None is required for core AIEP adoption. All are targeted for Phase 3 release (Q3 2026).

RepositoryPatentLayerWhat it adds
aiep-reasoning-traceP221TraceStructured record format for deterministic replay of reasoning sessions
aiep-reasoning-lifecycleP227LifecycleFull session lifecycle management — including partial completion and cancellation records
aiep-governance-policyP228GovernanceMachine-readable policy declarations and audit records for regulated deployments
aiep-federatedP229FederationCross-organisational evidence sharing and jointly auditable reasoning
aiep-epistemicsP231EpistemicsThree-state knowledge model — consensus, outlier, radical outlier — maintained in parallel
aiep-proof-engineP233ProofFormal causal proof records linking conclusions to evidence bases
aiep-compute-attestationP244AttestationCryptographic proof of computational conditions for regulated deployments
aiep-replay-kernelP245ReplayBit-identical output reproduction from reasoning traces — independently verifiable
aiep-dev-toolsP257ToolingDeveloper utilities: schema validation, evidence trail inspection, conformance harnesses

Already live (Phase 2):

RepositoryStatusWhat it is
@aiep/kernelLive — frozenR1–R8 canonical primitives. The load-bearing foundation.
aiep-genome-sdkLivePython SDK implementing the full protocol constitution
aiep-hub-validatorLiveValidates AIEP machine mirror endpoints against canonical schema v2.0.0
aiep-well-knownLiveGenerates and validates .well-known/aiep/ manifests for publisher domains
aiep-minerLiveOpen-source reference implementation — AIEP applied to hardware control
aiep-dissent-engineHOLD (P126)Advanced dissent arbitration — releasing after patent publication window

See also: /piea · /aiep-miner · /explainer · /builders · /certification

Get involved · Get started · Talk to us · Contact · GitHub ↗