Changelog
All notable changes to this repository are documented in this file.
The format is based on Keep a Changelog, and this
repository adheres to Semantic Versioning. Specification
API versions (v1alpha1, …) are versioned separately, see GOVERNANCE.md.
Changed
Section titled “Changed”- AEP process adopted (
docs/aep-process.md, owner decision of 2026-10-10, in force with the merge after the 5-working-day discussion period): AEPs need a reviewer who is not an author and, while all maintainers belong to one organisation, an external one (new section 5.1); no self-acceptance, also during alpha. New section 7.0 defines when an implementation may say “AWP<version>schema conformant (alpha)”: the conformance suite passes against its validator and its real exports in public CI; until then the wording is “built to the AWP schema, conformance in progress (alpha)”. - The JSON Schema is normative for document structure; the specification text stays normative for semantics and runtime behaviour (
schema/README.md, specv1alpha1section 2,GOVERNANCE.md). - AEPs 0001-0011 moved from
DrafttoReviewwith reviewer roles and the owner’s decisions; targets: 0001-0007, 0010, 0011 forv1alpha2, 0008 and 0009 forv1alpha3. AEP-0007 rewritten around Model Context Protocol terms (tool definitions and definition digests, resources, OAuth 2.1 authorization with resource indicators) within themcpprofile; AEP-0008 requires theModelCatalogdigest; AEP-0009 makescontentRetentionmandatory with the documented default7d. None is accepted. - OpenAgentix wording on the implementations pages and README: “built to the AWP schema, conformance in progress (alpha)”; not conformant to any profile.
- Docs:
GOVERNANCE.md,CONTRIBUTING.mdand the AEP process describe how changes are really reviewed (independent review agent, no guarantee of a human read before merge). - Website: restyled as a documentation site (introduction page at
/, sidebar with version label, on-this-page table of contents, prev/next links, mobile drawer, scrollable tables and code blocks); the marketing homepage was removed and its content moved into the docs pages.
-
Decision log for the AWP and OpenAgentix alignment (
docs/alignment/decisions.md): the owner’s decisions of 2026-10-10 with consequences, conflicts and a path to a conformance statement for OpenAgentix. -
Informative, implementation-neutral list of extension prefixes (
docs/registry/extension-prefixes.md), open to every implementation. -
OpenAgentix alignment documents (
docs/alignment/, informative, not adopted): field-by-field alignment matrix v2 against the currentagents.mdsource and examples with a prototype converter evaluation (no example converts cleanly; all produce valid AWP manifests only in lossy mode), a proposal for thex-openagentix-*extension namespace, a single-source-of-truth workflow (schema pin, drift test, conformance CI) and a phased plan with open decisions. OpenAgentix remains not conformant; no conformance claim is made. -
Proposed (Draft, not accepted) AWP Enhancement Proposals
aep/0001toaep/0011: conditional steps, argument constraints and call limits in permissions (no prefix wildcards), typed handoffs, event references, kindPrompt, kindPlaybook, MCP connection catalog, model and provider catalog, audit payload levels, digest canonicalisation and required extensions. They do not changev1alpha1. -
Website (
site/): Astro Starlight site with homepage, concept, governance, security, integration, example and implementation pages, the specification rendered fromspec/, offline Pagefind search, dark/light themes, link check, size budget and accessibility check, and a GitHub Pages workflow (.github/workflows/pages.yml). -
Website: Quickstart page and
llms.txt/llms-full.txtgenerated at build time. -
Repository scaffold: README, licenses (CC BY 4.0 for specification text, Apache-2.0 for code), Code of Conduct, contributing guide with DCO, governance, security policy, issue and pull request templates,
CNAMEforagenticworkflowprotocol.org. -
Draft specification
v1alpha1(spec/v1alpha1): document model, kindsWorkflow,AgentandPolicy, governance, policy evaluation, supply chain integrity, audit and traceability, conformance profiles, glossary and nine examples. -
Documentation site plan (
docs/site-plan.md). -
JSON Schema (draft 2020-12) for manifests of
v1alpha1(schema/awp.v1alpha1.json) with entry points forWorkflow,AgentandPolicy, and a catalogue of the semantic validation rules that JSON Schema cannot express (schema/README.md). -
Conformance suite for validators (
conformance/): 28 valid and 141 invalid manifests (one rule per file, named after the specification section), a machine-readable test index (conformance/index.json) and a reference checker (npm test) with pinned development dependencies (ajv,yaml). -
Command-line output formats for
awp validate,awp lint,awp simulate,awp plan,awp runandawp audit, including diagnostics, exit codes and the plan output (docs/cli.md). -
Mapping of the OpenAgentix
agents.mdsyntax to AWPv1alpha1(docs/mapping-agents-md.md): field-by-field table, converter design, round-trip expectations and the work needed per conformance profile, plus a website page on the OpenAgentix implementation status (not conformant). -
Draft proposal for AWP Enhancement Proposals (
docs/aep-process.md, not adopted): AEP lifecycle, numbering, template (aep/0000-template.md), versioning rules for API versions and repository releases, and rules for a future conformance mark (self-certification, test suite, revocation). No mark or certification exists.
Changed
Section titled “Changed”- Specification section 11.4 links to the CLI output format document instead of announcing it.