AI evidence infrastructure · Open protocol

We build AI that can
prove its work.

Phatfella is a small UK team building open evidence infrastructure for AI. Every product we ship runs on AIEP — the open protocol where every AI claim is backed by retrieved, hash-committed, independently replayable evidence.

phatfella.com · aiep.dev · piea.ai · aiepforecast.com
6Applicationsbuilt on AIEP
7Open reposApache 2.0
SHA-256Every recordhash-committed
0Hidden decisionsaudit trail on all

The protocol

AIEP — the open standard for verifiable AI records

Most AI systems produce answers you cannot verify. AIEP changes that structurally.

Every AIEP response carries a hash-committed evidence trail — sources retrieved, SHA-256 hashed and locked at answer time, then published at /.well-known/aiep/ on any domain. No retroactive changes.

The standard is open. Any system can publish conformant records. Any AI retrieval agent can discover, parse and trust them. Schemas, GENOME constitutional SDK, reference validator and mirror toolkit — all open source. Protocol IP patents pending.

Hash-committed

SHA-256 at publish time

Evidence-bound

Every claim links to sources

Machine-readable

/.well-known/aiep/

Replayable

Any session, from first principles

How it works

Six properties of every AIEP record

Evidence-bound

Every claim links to the artefacts that support it — as a machine-readable, hash-verified field, not a footnote.

Hash-verified

Every artefact carries a SHA-256 commitment at the moment of publication. Changes after the fact are detectable.

Machine-readable

Published at /.well-known/aiep/ on any domain. AI retrieval systems can find, parse, and trust the content directly.

Dissent-preserving

Outlier claims are archived with their evidence intact — ready for recall when knowledge shifts.

Replayable

Every reasoning chain is committed to ledger. Any session, any inference, replayable from first principles.

Fail-closed

The GENOME kernel suppresses execution if any invariant is unmet. It does not attempt to continue with degraded integrity.

What we have built

Applications built on AIEP

Six products sharing the same verifiable evidence substrate.

Piea

Evidence-governed AI

Professional-grade AI with a verifiable source rail. Every answer is backed by retrieved, hash-committed evidence. Four-model consensus on every inference.

AIEP Proof

Evidence management

Capture every quote, agreement and promise before it's disputed. Browser extension, Gmail, Outlook and mobile share target — SHA-256 tamper detection on every file.

Forecast

Construction intelligence

Contract admin and project control built on AIEP. Every instruction, variation, RFI and cost event — evidenced, timestamped and audit-ready.

AIEP Miner

Governed ASIC fleet control

Open-source ASIC fleet automation with a full AIEP evidence ledger. Every decision recorded, every suppression proven. No black boxes — Apache 2.0.

coming soon

Academy OS

Sports academy management

Members, gradings, billing and class scheduling. Evidence-backed attendance and belt progression records on the AIEP substrate.

Coming soon
coming soon

Qardl

Verifiable professional identity

Credential fraud is structurally harder when every claim is cryptographically anchored. For regulated industries, built on AIEP.

Coming soon

Mirror

Make your domain AI-discoverable.

AI systems retrieve content from the web. Without a structured machine interface, your domain is invisible to AI retrieval — or at best scraped and guessed at. An AIEP Mirror is the fix: five JSON files at a known path, published on any web server.

Without a Mirror

  • ✕  AI retrieval systems scrape or skip your domain
  • ✕  Content cited by name but not verified
  • ✕  No standard way to assert what you publish
  • ✕  Cannot participate in federated evidence networks

With a Mirror

  • ✓  AI systems discover and retrieve your artefacts directly
  • ✓  Every artefact is hash-bound — changes are detectable
  • ✓  metadata.json declares your identity machine-readably
  • ✓  Other Mirrors can federate with yours

Who should publish a Mirror

Regulators & government

Legislation, guidance, enforcement records — retrieved as structured artefacts, not scraped HTML.

Legal publishers

Case law and statutes retrieved by AI legal tools as verified, hash-bound documents.

Financial data providers

Rates, disclosures, and regulatory filings independently verifiable by AI finance systems.

Academic institutions

Papers and datasets with hash-bound citations — changes after publication are detectable.

Enterprise compliance

Policies and certifications verifiable by AI compliance tools without a phone call.

AI-native products

Publish evidence artefacts and response records — participate in federated evidence networks automatically.

Adoption tiers

Minimal < 30 min
  • index.json
  • metadata.json

Publisher identity and a basic discovery root. Enough for AI systems to find and recognise your domain.

Standard 1–2 hours
  • index.json
  • metadata.json
  • protocol.json
  • crawler-brief.json

Add capability declarations and a crawler brief. AI systems can understand what you publish and how to retrieve it.

Full Half day
  • All five files
  • + artefact entries
  • + federation config

Full artefact index with hash-bound entries. Participate in federated evidence networks. Verifiable by any AIEP-compliant system.

phatfella.com publishes a Mirror

Discovery artefacts are live at /.well-known/aiep/. AI retrieval systems can verify our identity without scraping.

/.well-known/aiep/index.json ↗ /.well-known/aiep/metadata.json ↗

Build on AIEP.

The protocol is open. The infrastructure is public. Start with the GENOME SDK or fork any repo.