跳转至

Changelog

This section documents the versioning policy and change history for the AIMO Standard.

Versioning Policy

AIMO Standard follows Semantic Versioning (SemVer):

Version Format: MAJOR.MINOR.PATCH

Change Type Version Bump Examples
MAJOR X.0.0 Breaking schema changes, code removal, required field changes
MINOR 0.X.0 New codes, new optional fields, new dimensions (optional)
PATCH 0.0.X Documentation fixes, definition clarifications, validator bug fixes

Breaking vs. Compatible Changes

Breaking Changes (MAJOR):

  • Removal of codes (after deprecation period)
  • Changes to required fields in schemas
  • Structural changes that invalidate existing documents
  • Changes to code format patterns

Backward Compatible Changes (MINOR):

  • Adding new codes to existing dimensions
  • Adding new optional fields to schemas
  • Adding new optional dimensions
  • Adding new evidence templates

Non-breaking Changes (PATCH):

  • Documentation corrections
  • Clarification of existing definitions
  • Translation improvements
  • Validator bug fixes

Deprecation Policy

Deprecation Process

  1. Mark as Deprecated: Code or feature is marked with status: deprecated and deprecated_in: X.Y.Z
  2. Deprecation Period: At least one MINOR version must pass before removal
  3. Provide Replacement: If applicable, replaced_by indicates the replacement
  4. Remove in MAJOR: Removal occurs in the next MAJOR version

Example Lifecycle

v0.0.1: FS-007 introduced (status: active)
v0.1.0: FS-007 deprecated (status: deprecated, replaced_by: FS-008)
v0.2.0: FS-007 still available with deprecation warning
v1.0.0: FS-007 removed (status: removed)

Using Deprecated Codes

  • Deprecated codes remain valid for validation
  • Validator SHOULD emit a warning for deprecated codes
  • New implementations SHOULD use replacement codes
  • Existing documents MAY continue using deprecated codes until migration

Release Artifacts

Each official release includes:

Artifact Description
Versioned site snapshot https://standard.aimoaas.com/0.0.1/
PDF specification trust_package.pdf
Asset package (ZIP) Schemas, templates, dictionary
Checksums SHA-256 hashes for integrity
Changelog This document

Change History

Version 0.1.2 {#version-012}

Summary: PATCH release (non-breaking). Normalizes EU AI Act references in docs/SSOT (informative mapping only; not legal advice). Improves Annex IV sample bundle completeness (signatures, hashes, payload). Adds optional JNC schema and validator check. Adds validator audit report outputs (audit-json, audit-html). See repository changelog/CHANGELOG.md for full entry.

Repair-deploy addendum (docs + mappings) — 2026-02-15

  • Added ISO/IEC 42006 coverage map page.
  • Expanded Conformance into AIMO Conformity Framework aligned to ISO 42001 (informative); levels Foundation, Operational, Audit-Ready.
  • Added ISO 42001 certification readiness toolkit (artifact).
  • Added EU AI Act timeline (02 Feb / 02 Aug 2025–2027), harmonised standards notes, and 2026 AI Office guidelines (informative).
  • Added new profiles and schema enum additions (ISO_42006, EU_AI_ACT_HIGH_RISK, EU_GPAI_COP, NIST_AI_600_1, UK_ATRS, JP_GOV_GENAI_PROCUREMENT); no version bump.
  • No version bump: repair-deploy updates the already released v0.1.2 snapshot.

Version 0.1.1 {#version-011}

Summary: PATCH release. Optional signature metadata for verification, Coverage Map audit_questions, Normative/Informative and governance clarifications, v0.2 roadmap. See repository changelog/CHANGELOG.md for full entry.

Version 0.1.0 {#version-010}

Summary: Normative Evidence Bundle structure, ID namespace (EV/LG), Profiles, Validator. Breaking: EV→LG for taxonomy. See repository changelog/CHANGELOG.md for full entry.

Unreleased (namespace and normative fixes)

Summary: Resolves EV code collision, clarifies EV (index) vs Evidence Pack (payload), and hardens /dev against audit miscitation.

Changed

  • Evidence Pack document types (EP namespace): Evidence Pack file types use EP-01..EP-07 (document type). Taxonomy LG-001, LG-002, … are Log/Event types (Request Record, Review/Approval, etc.). EV- reserved for Evidence artifact IDs only. See Evidence Pack Template and ID Policy / Namespace. Schema: evidence_files[].file_id pattern is ^EP-\\d{2}$; ev_type uses LG-xxx.
  • Normative relationship: Evidence Bundle now states normatively: EV records (JSON) are the index/ledger; Evidence Pack files are the payload; EV records SHOULD reference payload by evidence_file_ids (e.g. EP-01) and/or hashes; minimum submission set = EV JSON + Dictionary + Summary + Change Log + Evidence Pack.
  • /dev anti-miscitation: Development preview pages show a red banner: "Development Preview — Not for audit citation. Use /latest/ or a versioned URL." Canonical for /dev/ pages points to /latest/; noindex remains in place.

Version 0.0.1 (2026-02-02)

Summary: Initial release of AIMO Standard with 8-dimension code system, Evidence Pack templates, and comprehensive governance documentation.

Added

Code System (8 Dimensions)

Dimension Codes Added Description
FS FS-001 to FS-006 Functional Scope
UC UC-001 to UC-010 Use Case Class
DT DT-001 to DT-008 Data Type
CH CH-001 to CH-006 Channel
IM IM-001 to IM-005 Integration Mode
RS RS-001 to RS-005 Risk Surface
OB OB-001 to OB-005 Outcome / Benefit
LG LG-001 to LG-015 Log/Event Type

Schemas

  • taxonomy_pack.schema.json: Taxonomy pack definition
  • changelog.schema.json: Changelog entries
  • evidence_pack_manifest.schema.json: Evidence Pack manifests
  • shadow-ai-discovery.schema.json: Shadow AI discovery evidence
  • agent-activity.schema.json: Agent activity evidence

Evidence Pack Templates (MVP)

  • EP-01 (legacy EV-01): System Overview
  • EP-02 (legacy EV-02): Data Flow
  • EP-03 (legacy EV-03): AI Inventory
  • EP-04 (legacy EV-04): Risk & Impact Assessment
  • EP-05 (legacy EV-05): Controls & Approvals
  • EP-06 (legacy EV-06): Logging & Monitoring
  • EP-07 (legacy EV-07): Incident & Exception Handling

Documentation

  • Taxonomy documentation with 8-dimension definitions
  • Code System format specification
  • Dictionary CSV format specification
  • Versioning and change policy
  • Validator MVP requirements
  • Human Oversight Protocol
  • Coverage Map (ISO 42001, NIST AI RMF, EU AI Act, ISMS)
  • Trust Package

Backward Compatibility

This is the initial release; no backward compatibility concerns.

Machine-Readable Changelog

A machine-readable changelog is available:

  • changelog/changelog.json

This file follows the changelog.schema.json schema and can be parsed programmatically.

References