Modularity, Durability, Universality, and Trust by Construction

AIOSchema was created to solve a fundamental problem: digital content needs a universal, durable, and verifiable provenance layer that works everywhere and depends on no single system, platform, or technology.

The design philosophy behind AIOSchema is what makes this possible. It rests on four pillars:

  • A stable, minimal structure
  • Modular, replaceable algorithms
  • Universal interoperability
  • Long-term durability and verifiability

1. Stable Core, Modular Algorithms

AIOSchema separates the shape of the standard from the algorithms used inside it.

The Core Block is intentionally minimal and stable. It defines only the fields required for deterministic identity and verification.

Everything else – hashing, signing, soft binding, anchoring – is treated as a module, not a fixed dependency.

This ensures that:

  • No single cryptographic primitive can compromise the whole standard
  • Algorithms can be replaced without redesigning the manifest
  • Implementations remain simple and predictable
  • The standard can evolve as new threats or technologies emerge
  • The structure of the manifest remains stable across versions

AIOSchema v0.5.x uses a small set of strong, modern algorithms (Ed25519, SHA-256, pHash) to keep implementations simple and interoperable. These are practical defaults, not permanent requirements.

Future versions (v0.6+) will introduce:

  • Algorithm registries
  • Deprecation paths
  • Pluggable signature algorithms
  • Pluggable soft binding algorithms
  • Pluggable anchoring mechanisms

The architecture already supports this – the specification language will evolve to express it.

2. Universality and Interoperability

A provenance standard is only useful if it works everywhere.

AIOSchema is designed to be:

  • Container-agnostic (JPEG, PNG, MP4, PDF, etc.)
  • Platform-agnostic (web, mobile, desktop, cloud)
  • Ecosystem-agnostic (works with or without C2PA)
  • Metadata-agnostic (sidecar, XMP, hybrid)

The standard integrates cleanly with existing metadata ecosystems:

  • XMP for embedded metadata
  • EXIF for camera metadata
  • schema.org for semantic metadata
  • W3C PROV for provenance modeling
  • C2PA for content authenticity frameworks

AIOSchema is not a replacement for these systems – it is a bridge.

It provides a universal, lightweight provenance layer that can be embedded inside or alongside existing metadata structures.

3. Durability and Survivability

Digital content is constantly transformed: recompressed, resized, transcoded, filtered, re-uploaded, stripped of metadata.

A provenance standard must survive these transformations.

AIOSchema achieves this through:

Multi-hash support Multiple hash algorithms can be included in the manifest. If one fails or becomes obsolete, others remain valid.

Detached signatures The manifest can be verified independently of the asset file.

Sidecar + XMP hybrid embedding Metadata survives both platform stripping and file transformations.

Soft binding (perceptual hashing) When hard hashes fail due to recompression or resizing, soft binding provides a fallback match.

Anchor chaining Each version of an asset or specification can be cryptographically linked to its predecessor.

Durability is not an afterthought – it is a core design requirement.

4. Verifiable Without Specialized Tools

A provenance standard must be easy to verify.

AIOSchema is designed so that:

  • A developer can implement a verifier in a day
  • Verification requires no proprietary tools or libraries
  • All algorithms used are open and well-documented
  • The manifest is plain JSON
  • The canonicalization rules are deterministic
  • The anchoring mechanism is public and independently verifiable

This ensures that anyone can verify content, no single system controls verification, and the ecosystem remains open and transparent.

This is essential for trust.

5. Anchoring: Pluggable, Public, and Independent

AIOSchema uses a simple, universal anchor URI scheme:

aios-anchor:<service-id>:<anchor-id>

This design allows anchoring via:

  • RFC 3161 trusted timestamp authorities
  • Blockchain-based timestamping systems
  • Hybrid or custom anchoring services
  • Any future mechanism that produces a public, immutable, independently verifiable timestamp

AIOSchema does not mandate any specific anchoring service. It mandates only that anchors must be publicly verifiable, independent of the author, immutable, and timestamped.

This ensures long-term trust without reliance on any single system.

6. Transparency and Provenance of the Standard Itself

AIOSchema uses its own mechanisms to establish the provenance of the specification.

Each version of the spec is hashed, signed, anchored, and linked to the previous version via previous_version_anchor. This creates a cryptographic chain of custody for the standard itself – transparency, accountability, immutability, verifiable authorship, and verifiable version history.

The standard practices what it preaches.

7. Evolution Without Fragmentation

AIOSchema is designed to evolve without breaking compatibility.

The stability policy ensures:

  • No breaking changes within a minor version increment
  • Clear versioning semantics
  • Backward compatibility for all v0.x manifests
  • Forward compatibility through algorithm agility

The goal is a standard that can grow without fracturing the ecosystem.

8. Why AIOSchema Exists

AIOSchema exists because the world needs a universal provenance layer that is lightweight, durable, open, modular, future-proof, and verifiable by anyone – one that works across all platforms and ecosystems.

It is designed to be the minimum viable standard for authenticity and provenance: simple enough to implement quickly, strong enough to trust, and flexible enough to last.

Read the specification → Getting Started guide →