Standards Changelog

Release history for the Operating Specification program.

The changelog is where the standards surface becomes a real release program. It records what changed, when it changed, and which builder-facing assets moved with each revision.

Release History

Each public artifact change should leave a readable trail.

This page tracks the early public release history for the standard, starter kit, reference packages, and standards site surface.

October 12, 2026
vexecution-provider.v1alpha1Public release

Open Execution Provider draft extension

Add four governed execution binding protocols beneath core v0.3.1, with a public guide and schema addendum. This is an opt-in draft extension; the core draft version is unchanged.

  • Native execution remains the default; A2A is preferred when supported, never mandatory.
  • Separate portable capability and policy references from tenant execution bindings and credentials.
  • Document installed Microsoft Foundry, ServiceNow Virtual Agent, Salesforce Agentforce, AWS AgentCore JWT, Google Agent Engine query and separately pinned MCP generations.
  • Clarify live acceptance, provider certification, Marketplace publishing and compiler/deployment readiness limits.
August 13, 2026
v0.3.1Public release

v0.3.1 committee pack published

Published the first curated committee-facing release bundle for the Operating Specification Standard with the current core draft, schema package, AI runtime policy guidance, TypeScript action annex, and upgraded reference paths.

  • Added the v0.3.1 core draft with runtime interpretation rules, conformance matrix, bounded action contract, and AI runtime policy.
  • Published the aligned v0.3.1 schema package for external builders and validators.
  • Added the AI runtime policy guidance brief and three upgraded reference operating paths for simple, non-security, and high-risk scenarios.
August 13, 2026
v0.1Public release

Builder draft published

First public builder-oriented draft of the Operating Specification Standard, reframed around package structure, validator responsibilities, runtime conformance, and external buildability.

  • Published the Operating Specification Standard builder draft as a downloadable Word document.
  • Defined the downloadable package model, minimum implementable contract, and conformance expectations.
  • Added committee and governance direction for public stewardship of the standard.
August 13, 2026
v0.1.0Public release

Starter kit released

Released the first downloadable Operating Package starter kit with a real path, schema, semantic artifact, rules artifact, validation artifact, and validator guidance.

  • Published a zip-distributable starter kit with repository-backed artifacts.
  • Validated the included critical vulnerability path with the existing CLI validator.
  • Added quickstart, compatibility, and validator guide material for external builders.
August 13, 2026
v0.1.0Public release

Identity onboarding reference package added

Published a second domain example to prove the format is reusable outside the initial security case and can validate in identity operations as well.

  • Added a lightweight identity onboarding reference package with schema and primary path.
  • Validated the employee onboarding path using the same CLI validation flow.
  • Positioned the package explicitly as a reference example rather than a full starter-kit equivalent.
August 13, 2026
v0.1Public release

Standards hub launched inside the Aegora site

Integrated the standard into the main Aegora website with a discoverable standards hub, downloadable assets, guided onboarding flow, status badges, and release metadata.

  • Added a top-level Standards navigation path and standards docs hub.
  • Exposed public downloads for the builder draft, starter kit, and identity onboarding reference package.
  • Added guided onboarding, maturity badges, file metadata, and release-hygiene strips to the standards experience.
Release Hygiene

Keep the standard legible as it evolves.

As more packages, schemas, validators, and committee outputs are published, the changelog should become the public record that ties version labels to concrete changes.