Builders Programme

The Builders Programme is for developers and organisations that implement the AIEP protocol in their own systems and want to demonstrate independent conformance.

The fastest path in:

  1. Read the Integration Guide — start to AIEP-COMPLIANT badge in 30 minutes
  2. Run aiep-verify --vectors AIEP-VECTORS/v1.1.0/ — 15 vectors, all must pass
  3. Publish your CONFORMANCE.md — template here
  4. Contact to be listed in the AIEP conformant registry

What it means to be AIEP-COMPLIANT

A conformant system:

  • produces pack_hash values that match the reference Python kernel on all 15 core vectors
  • rejects NaN, Infinity, and −0 inputs (malformed-input suite, 6/6)
  • enforces constitutional constraints CC-001–CC-005 on every decision record
  • can be verified by any third party with pip install aiep-genome-sdk

Conformance is independent of the commercial products (Forecast, PIEA, Qardl). You do not need a commercial relationship to be conformant. You do not need an NDA.

The conformance badge

When you pass the conformance suite, you can display:

[![AIEP-COMPLIANT](https://img.shields.io/badge/AIEP-v1.1.0-green)](CONFORMANCE.md)

This badge is a claim. The claim is verifiable: any engineer can run your evidence through aiep-verify and confirm the hash. If the hash doesn’t match, the badge is false. The protocol does not rely on trust — it relies on replication.

Reference implementations

AIEP Miner (Apache 2.0)

The open-source reference implementation of the AIEP protocol applied to autonomous hardware control. Demonstrates verifiable decision-making, Negative Proof records, and append-only evidence chains on physical ASIC mining hardware.

→ AIEP Miner reference implementation

Minimal Service

A minimal Python service demonstrating the complete evidence → commit → pack_hash → record cycle. Starting point for any new implementation.

→ examples/minimal_service in genome-sdk

Who this is for

Developers building systems that produce AI-governed outputs and need those outputs to be verifiable by external auditors, regulators, or counterparties.

Organisations in regulated industries — construction, financial services, healthcare — that need AI decisions to be legally defensible. A pack_hash-bound decision record is verifiable without access to model weights or internal systems.

Research institutions implementing or evaluating AI governance mechanisms. The conformance suite and CANON_SPEC.md are sufficient to implement the protocol in any language.

Sector priorities

The protocol was designed in the construction sector. The unsolved problem there is specific: AI-generated specifications, cost estimates, and instruction documents that cannot be legally defended because they have no auditable evidence trail.

Any construction firm — quantity surveyor, structural engineer, main contractor — that deploys an AIEP-conformant system and binds every cost plan to a pack_hash creates the first regulated-sector proof. That proof is what attracts the next ten implementations.

Construction is the priority. Financial services and healthcare follow the same logic.

Commercial programme

If you are building a vertical product on AIEP and want to discuss a deeper commercial relationship, the partner programme still applies:

  • Builders who materially contribute to a specific vertical may be offered participation (up to 10%)
  • Subject to proof and written agreement. No partnership exists until a contract is executed
  • Some restricted materials are shared under NDA. Application implies acceptance

These terms apply only to the commercial layer. Protocol conformance itself is open and unrestricted.

Get started

→ Integration Guide — the complete step-by-step walkthrough
→ GENOME SDK — SDK documentation
→ Downloads — schemas, open-source repos, build manifests
→ Contact — to discuss the partner programme or register conformance