◈︎

AIOSchema Provenance Record

Purpose: This page documents the founding provenance anchor and version chain for the AIOSchema specification itself. AIOSchema uses its own mechanisms to establish the provenance of the standard.

What This Page Records

Each version of the AIOSchema specification is:

  • Hashed over its canonical bytes
  • Signed with the founder’s Ed25519 key
  • Anchored via RFC 3161 or equivalent
  • Linked to its predecessor via previous_version_anchor

This creates a cryptographic chain of custody for the standard. The chain is independently verifiable: any party can verify that each version existed at the claimed time and has not been modified since anchoring.

Version Chain

Version Authored Anchor URI Previous anchor
v0.1 Jan 2026 (genesis : no previous anchor) :
v0.2 Feb 2026 (to be published) v0.1 anchor
v0.3 Feb 2026 (to be published) v0.2 anchor
v0.3.1 Feb 2026 (to be published) v0.3 anchor
v0.4 Feb 2026 (to be published) v0.3.1 anchor
v0.5 Feb 2026 (to be published) v0.4 anchor
v0.5.1 Feb 2026 (to be published) v0.5 anchor
v0.5.5 Mar 2026 (to be published) v0.5.1 anchor
v0.5.6 May 2026 (to be published) v0.5.5 anchor

Anchor URIs will be published here once each version’s anchor record is finalised.

Verification

To verify the chain:

  1. Obtain the specification file for the version you want to verify.
  2. Recompute core_fingerprint using the canonicalization procedure in Specification §5.6.
  3. Resolve the anchor_reference URI via the registered anchor service.
  4. Compare asset_id and core_fingerprint from the anchor record against the manifest values using timing-safe equality.
  5. If both match: the specification existed in that exact form at or before the anchor timestamp.

Reference implementations with anchor_resolver support are at /implementations/.

The Standard Practices What It Preaches

Using AIOSchema’s own mechanisms to establish provenance of the specification is a deliberate design principle. The standard does not ask implementers to do anything that the standard itself does not do.

© 2026 Ovidiu Ancuta. AIOSchema™ and ◈™ are trademarks of Ovidiu Ancuta Specification: CC-BY 4.0 · Reference Implementations: Apache 2.0 · https://aioschema.org