Definition: The changelog tracks all changes to the Attested AI specification and glossary. Mechanism: Each version includes dated entries with added, changed, deprecated, and removed items. Value: Implementers can track specification evolution and migration requirements. Output: Versioned history with semantic versioning.

Changelog

Version history for the Attested AI specification and glossary.

Versioning Policy

The Attested AI specification follows Semantic Versioning 2.0.0:

  • MAJOR version for incompatible changes to artifact schemas or verification rules
  • MINOR version for backwards-compatible additions (new fields, new terms)
  • PATCH version for clarifications, typo fixes, and documentation improvements

Each glossary term includes introducedIn and optionally deprecatedIn version references.

v1.0.0

2025-01-01CURRENT

Initial public release of the Attested AI specification.

Glossary: v1.0.0Spec: v1.0.0

added

  • Policy Artifact schema with versioning, subject binding, and enforcement mapping
  • Enforcement Receipt schema with hash-chained continuity
  • Evidence Bundle specification for offline verification
  • Canonicalization rules (JCS-compatible, UTF-8, sorted keys)
  • Cryptographic requirements (SHA-256, Ed25519)
  • Verifier contract with deterministic PASS/FAIL output
  • Test vectors for canonicalization, hashing, and signing
  • Standards mapping for NIST AI RMF, SP 800-53, ISO/IEC 42001

v0.9.0

2024-12-15SUPERSEDED

Release candidate with core artifact definitions.

Glossary: v0.9.0Spec: v0.9.0

added

  • Core glossary terms: Policy Artifact, Enforcement Receipt, Evidence Bundle
  • Draft specification for canonicalization and hashing
  • Initial learning path documentation

changed

  • Renamed 'Attestation Object' to 'Policy Artifact' for clarity
  • Refined enforcement action semantics (CONTINUE, QUARANTINE, KILL)

v0.5.0

2024-11-01SUPERSEDED

Initial internal draft with foundational concepts.

Glossary: v0.5.0Spec: v0.5.0

added

  • Foundational concepts: drift detection, continuity chains, offline verification
  • Draft threat model and claim boundaries
  • Internal review documentation

Editorial Policy

Term Stability

Once a term is published in a MAJOR or MINOR release, its termCode (URL slug) and core definition are considered stable. Changes to meaning require a new version with migration notes.

Deprecation Process

Terms are deprecated for at least one MINOR version before removal. Deprecated terms include migration guidance and alternative term references.

Breaking Changes

Breaking changes to artifact schemas, verification rules, or cryptographic requirements trigger a MAJOR version increment. Each breaking change includes explicit migration steps.

Questions or feedback on the specification?

Contact Attested Intelligence
Previous← Standards MappingReferenceSpecification →