v0.7.0

Changed

• Publish the next-phase interoperability delivery as repository v0.7.0:
  cumulative-layer migration/rollback guidance, the pinned non-normative
  OpenTelemetry companion, tested retry projections and hosted MkDocs docs.
• Align current documentation, sibling references, package metadata and the
  portable-suite snapshot with v0.7.0. Suite cases and expected outcomes are
  unchanged. Repository v0.6.2 was published with an undersized patch version;
  the incorrect v0.6.2 release and tag have been removed.
• Run/Workflow markers remain 0.4-draft and provenance remains 0.6-draft.
  This repository release introduces no 0.7-draft schema family and closes
  no independent-review gates. No sibling runtime dependency bump is needed.

v0.6.1

[0.6.1] - 2026-10-31

Added

• specification/v0.6/provenance.md: exploratory 0.6-draft provenance
  records — subjects (with optional sha-256/sha-384/sha-512 digests of
  exact bytes), source references (aios_object, artifact, document,
  dataset, log, tool_output, human_input), derived findings and
  evidence lineage (derived-from, supports, contradicts, supersedes).
• specification/v0.6/schemas/provenance.schema.json, reusing the
  0.4-draft common definitions, and the canonical
  examples/provenance/support-finding.provenance.json.
• specification/v0.6/provenance-rules.json: AIOS-0.6-R01–R07 producer
  rules, C01–C08 consumer rules (including a new cross_artifact check
  kind), D01, K01 and S01.
• specification/v0.6/conformance-suite/: 41 outcome cases with expected
  rule citations and 5 cross-artifact resolution cases, plus the expected
  validator behavior.
• specification/v0.6/naming-conventions.md and
  tests/test_naming_conventions.py.
• Decision D-006: provenance is a companion artifact under its own marker.
• .gitattributes keeps JSON fixtures LF-only so digests are reproducible.

Changed

• specification/v0.5/compatibility.json: every published schema set lists
  its artifact_types; a new 0.6-draft set validates provenance records and
  declares depends_on: ["0.4-draft"]. The 0.4-draft set is otherwise
  unchanged.
• Repository reference checks cite rule IDs. Step end-before-start timestamps
  are now checked under AIOS-0.4-P04, and missing endpoints and unmarked
  Workflow references cite AIOS-0.4-X01, matching deep-agentic-core-mcp.

Notes

• Run and Workflow artifacts stay 0.4-draft; no v0.4 schema, catalog or
  closed vocabulary changed, and no milestone's review status changed.
• Consumers that do not check 0.6-draft must keep rejecting provenance
  records under AIOS-0.5-V03. See docs/v0.6.1-ecosystem.md.

v0.6.0

[0.6.0] - 2026-10-19

Added

• Exploratory v0.6 canonical examples and extension model: minimal Workflow and
  Run, advanced support graph, retries and schema/semantic negative controls.
• Machine-readable fixture manifest and offline validation tests.
• Third-party extension placement, naming, preservation, versioning, publication
  and interpretation guidance, with sibling compatibility documentation.

Changed

• Included from the prior [Unreleased] section: reviews/framework-mappings/agentic-chaos.md: Agentic Chaos 0.6.0 addendum.
  Covers the additive native call log and unhandled_error, the two new members
  of the io.deepagentlabs.agentic-chaos extension, and why chaos contract
  verdicts are producer-native rather than AIOS evaluation objects. No schema,
  catalog or core object change.

Notes

• Artifacts remain 0.4-draft. No schemas, catalogs, closed vocabularies or
  prerequisite review status change. Portable conformance and provenance objects
  remain v0.6.x work. Sibling runtime dependencies and releases are not required.

v0.5.1 — Machine-readable conformance and compatibility catalogs

Added

• specification/v0.4/conformance-rules.json: machine-readable catalog that
  assigns a stable identifier to every MUST/MUST NOT/SHOULD obligation in the
  v0.4 conformance document: producer rules AIOS-0.4-P01–P12,
  external-reference rules X01–X02, consumer rules C01–C04, D-004
  closed-vocabulary rules U01–U02, extension naming E01, draft
  self-description D01, and claim format K01. Each rule quotes its
  normative sentence and says whether schema validation, semantic checks, or
  only a process obligation can decide it.
• specification/v0.5/compatibility.json: the spec_version marker grammar,
  the schema set published behind each marker (0.4-draft today), and
  identifiers AIOS-0.5-V01–V06 for each row of the consumer compatibility
  table.
• tests/test_conformance_catalogs.py: fails if either catalog drifts from
  the normative Markdown it mirrors.

Notes

• The Markdown documents remain normative; the catalogs only label what they
  already require. No schema, vocabulary, or milestone status changed.
• Released as a patch on the v0.5 line (v0.5.1) because it labels existing
  rules rather than adding normative content.

v0.5.0 — Versioning and Compatibility Rules

Exploratory draft. Defines spec_version grammar, editorial/additive/breaking change classification (decision D-005), the consumer compatibility matrix, deprecation policy, and extension-point stability for AIOS artifacts.

Status: Tests v0.1 concepts, v0.2 relationships, v0.3 semantic conventions, and v0.4 schemas; cannot freeze before them. Several v0.5-specific acceptance-criteria gates also remain open (see specification/v0.5/acceptance-criteria.md). Not a stable release; do not claim AIOS conformance from this artifact.

Asset: zipped markdown docs for the v0.5 milestone (README, versioning, examples, acceptance-criteria).

v0.4.0 — JSON Schemas (draft)

Exploratory draft. JSON Schema (Draft 2020-12) artifacts for AIOS: workflow.schema.json (reusable definitions), run.schema.json (runtime evidence and execution graphs), and common.schema.json (shared identifiers, references, relationships, events, measurements).

Status: Tests v0.1 concepts, v0.2 relationships, and v0.3 semantic conventions; cannot freeze before them. Every artifact currently uses spec_version: "0.4-draft". Draft alignment requires both schema validation and the semantic checks in conformance.md — validation proves contract alignment, not truth, quality, safety, or operational success. Not a stable release; do not claim AIOS conformance from this artifact.

Assets: the 3 schema JSON files, plus a zip of the v0.4 markdown docs (README, conformance, examples, acceptance-criteria).

v0.3.0 — Semantic Conventions (draft)

Exploratory draft. Defines stable, transport-neutral names and lifecycle meanings for AI operational events and their common attributes.

Status: Depends on v0.1 concepts and v0.2 relationships and cannot freeze before them. Not a stable release; do not claim AIOS conformance from this artifact.

Asset: zipped markdown docs for the v0.3 milestone (semantic-conventions, examples, acceptance-criteria).

v0.2.0 — Relationships and Execution Structure (draft)

Exploratory draft. Defines how runtime objects are connected without requiring a particular telemetry transport or programming language, so independent implementations can describe the same execution graph consistently.

Status: Depends on and cannot freeze before v0.1. Not a stable release; do not claim AIOS conformance from this artifact.

Asset: zipped markdown docs for the v0.2 milestone (relationships, examples, acceptance-criteria).

v0.1.0 — Core Concepts (draft)

Foundation draft. Defines a shared language for describing what exists during the operation of an AI system, establishing conceptual identity and boundaries before choosing JSON fields or APIs.

Status: Exploratory/foundation draft — independent-framework review remains open. Not a stable release; do not claim AIOS conformance from this artifact.

Asset: zipped markdown docs for the v0.1 milestone (core-concepts, terminology, examples, acceptance-criteria, decisions).