Schema Catalogue
Schemas are how AIEP becomes deterministic. They allow different systems to agree on whether an artefact is structurally valid before it is relied upon. Schemas do not prove truth - they prove structure. A machine that validates structure can fail closed when required fields are missing. A machine that validates nothing can be manipulated by malformed inputs.
All canonical schemas are versioned, Merkle-anchored, and published under the well-known path. The protocolVersion field on every artefact pins it to a specific schema version.
Canonical schema entries
| Schema file | Record type | Required primitives | Patent reference |
|---|---|---|---|
instruction.schema.json | AIEP_INSTRUCTION | instruction_id, claim_text, evidence_refs[], issuer_id, timestamp, canonical_hash | GB2519711.2 (R1-R4) |
evidence.schema.json | AIEP_EVIDENCE | evidence_id, source_uri, retrieval_timestamp, hash, normalisation_profile, record_type | P10, P14 |
goal.schema.json | AIEP_GOAL_VECTOR | goal_id, goal_hash, goal_artefact_ref, committed_at, drift_state, genome_lockfile_version | P37 |
divergence.schema.json | AIEP_DIVERGENCE_RECORD | divergence_id, divergence_type, branch_refs[], evidence_delta, plausibility_score, probability_envelope_hash, dissent_archive_ref | P16, P83 |
normalisation.schema.json | AIEP_NORMALISATION_MANIFEST | manifest_id, source_hash, target_hash, normalisation_profile, transforms[], canonical_output_hash | P10, P17 |
compliance.schema.json | AIEP_COMPLIANCE_CERTIFICATE | cert_id, output_artefact_ref, regulation_id, issuer_id, evidence_chain[], cert_hash, issued_at | P37 |
audit.schema.json | AIEP_AUDIT_EVENT | event_id, event_type, actor_id, artefact_ref, timestamp, signature, hash | GB2519711.2 |
swarm.schema.json | AIEP_SWARM_CONSENSUS_RECORD | swarm_id, node_refs[], consensus_hash, dissent_refs[], quorum_threshold, committed_at | GB2519803.7 |
plausibility.schema.json | AIEP_PLAUSIBILITY_DECLARATION | declaration_id, claim_type, plausibility_score, registry_version, merkle_proof, threshold_band, declaration_hash | P03, P67 |
probability.schema.json | AIEP_PROBABILITY_ENVELOPE | envelope_id, divergence_node_ref, epsilon, confidence, computation_method, canonical_commitment, recomputation_hash, envelope_hash | P04, P66 |
recall.schema.json | AIEP_RECALL_SCOPE | recall_id, archived_branch_ref, trigger_threshold_change, time_bounds, recall_initiator_id, reconstruction_hash | P22, P42, P83 |
certificate.schema.json | AIEP_CERTIFICATE | cert_id, issuer_id, subject_id, cert_type, issued_at, expires_at, cert_hash, scope | GB2519711.2 |
metadata.schema.json | AIEP_METADATA | publisher_id, domain, protocol_version, genome_lockfile_version, schema_set_version, metadata_hash | GB2519711.2 |
Where to find them
Schemas are published at /.well-known/aiep/schemas/ and are included in the downloadable schema bundle at /downloads.
Each schema has:
- a semantic version (
semverfield) - a canonical hash computed over the normalised schema text
- a Merkle inclusion proof linking it to the current schema set root
- a
deprecated_byfield (null if current)
Pinning to a schema version is done via the protocolVersion field on the artefact, which resolves to a specific schema set version in the registry. Artefacts validated against a deprecated schema version remain valid for historical records but are not execution-eligible under current registry rules.