Strategic Access
AIEP is an open protocol. You can adopt it today — publish a Mirror, install the SDK, read the spec. No permission needed.
But the deep integration layer — source access, the Piea integration framework, funded sector pilots, and strategic partnerships — involves the team. This page is for that conversation.
What AIEP adds to your product
AIEP is not an AI product. It is the substrate under any digital system that needs to produce, retrieve, or validate records in a way that is machine-readable, hash-bound, and independently auditable.
The AIEP ecosystem includes:
| Product | What it does | Status |
|---|---|---|
| AIEP Core | Deterministic evidence and retrieval architecture — canonical records, artefacts, hashing, validation, and replay boundary | Open protocol |
| AIEP Mirror | Five JSON files. Your domain becomes machine-readable to any AI retrieval system. No backend. | Open — Apache 2.0 |
| GENOME SDK | Python integration kit: evidence ledger, canonical hashing, validation, divergence detection | Open — PyPI: aiep-genome-sdk |
| AIEP Validator | Validation layer for schemas, hashes, artefacts, and AIEP-compatible outputs | Open — Apache 2.0 |
| Piea | Evidence intelligence layer that plugs into your SaaS, database, or application | Controlled preview |
| Forecast | Construction management and commercial platform — instructions, variations, notices as audit-grade evidence records designed for legal and commercial review | Deployed |
| QARDL | Verifiable professional identity: cryptographically signed digital business card, job advertisements, and professional networking | Active |
| AIEP LRM | Cumulative evidence-bound reasoning — later steps commit to prior verified state | Controlled preview |
| AIEP Token | Side-by-side token comparison: standard LLM vs AIEP incremental reasoning with live efficiency metrics | Controlled preview |
| AIEP Live | Real-time operating index — tokens saved, reuse ratios, evidence artefacts, and session activity | Controlled preview |
| AIEP Miner | Governed compute research — proof-of-concept layer for constrained, repurposed or distributed compute environments | Open source |
Who we work with
Development partners
You have a SaaS product, a database-backed application, or a platform that would benefit from a verifiable evidence layer. Piea can plug into your existing stack — PostgreSQL, MySQL, REST, SharePoint, S3/R2 connectors, TypeScript SDK — without a rebuild.
Development partnerships involve: source-level access to Piea integration surfaces, early schema access, technical support during integration, and co-design of evidence governance workflows for your sector.
Academic and research partners
AIEP has genuine open research questions. Instruction-evidence linking at scale. Divergence detection in multi-model systems. Cumulative evidence-bound reasoning (LRM). Hardware-layer governance. Replay correctness under adversarial conditions.
If you are supervising research, seeking a study object, or exploring a collaboration, we want to hear from you. We can provide access to technical documentation, schema artefacts, and — where appropriate — integration environments under a research collaboration agreement.
We are especially interested in partners who can help validate AIEP in real deployed workflows, not only theoretical research. Build-out and deployment partnerships are as valuable as academic study.
Regulated-sector pilots
Construction, legal, financial services, healthcare, and government teams often face the same problem: records exist but can’t be verified by third parties or machines. Forecast demonstrates what a full AIEP evidence layer looks like in production for a regulated workflow.
Funded pilots bring together AIEP’s evidence governance architecture and your domain expertise. Talk to us about what a pilot looks like for your sector.
Investment and strategic acquisition
We don’t lead with this. AIEP is not offered as a commodity licence or piecemeal rights sale. Public components remain open under their stated licences. Deeper commercial access is handled through controlled evaluation, funded pilots, enterprise integration, development partnerships, and strategic discussions.
A serious, long-term strategic conversation with the right partner is always welcome. If you are considering a significant capital relationship or strategic position, write to us directly.
Commercial terms — what we’re open to
| Route | What it involves |
|---|---|
| Mirror adoption | Free. Apache 2.0. No contact required. |
| GENOME SDK | Free. Apache 2.0. PyPI install. |
| Development partnership | Agreed scope, source access under Development NDA |
| Academic collaboration | Research agreement, technical access |
| Sector pilot | Scoped jointly, typically funded |
| Investment / acquisition | Serious conversations only — contact directly |
What we’re looking for in a partner
Someone who understands the problem AIEP solves. Ideally: an existing product or workflow where evidence provenance matters, a team who will integrate rather than just evaluate, and a genuine intent to deploy rather than just explore.
We’re not looking for dependency. We’re looking for implementation.
Disclosure boundary
AIEP.dev publishes the open protocol layer, all public technical documentation, schemas, examples, and high-level roadmap categories.
Architecture from P300 onward — advanced reasoning governance, federated sovereignty, hardware enforcement, and longer-range capability design — is not in the public domain. Details are available to qualified partners under Development NDA. Contact us to find out whether this applies to what you’re interested in.
Full boundary: /public-disclosure-boundary
Request access
No form. Just email.
Tell us who you are, what you’re working on, and what kind of access you’re looking for. We’ll respond to every genuine enquiry, usually within a few days.
Access to restricted materials requires acceptance of the Development NDA (England & Wales governing law). We’ll tell you when and if that applies before anything is shared.