Conformance

Profile	Depends on	Covers
`core`	-	Parsing and validating manifests, step graph, budgets, permissions, secrets, `workflow.*` events
`governance`	`core`	Ownership, data policy, model policy, approvals, risk levels, separation of duties, environments, policies
`audit`	`core`	Event envelope and types, integrity modes, decision and reproducibility records
`security`	`core`	Digests, signatures, image pinning, isolation, secret redaction
`mcp`	`core`	MCP servers as tool sources, action identifiers per tool call
`a2a`	`core`	Remote agents, agent card verification

A runtime that claims conformance publishes a statement:

implementation:
  name: example-runtime
  version: 0.4.0
  url: https://runtime.example.org
conformance:
  awp: v1alpha1
  profiles:
    - core
    - governance
    - audit
  limitations:
    - "audit: integrity mode signed is not supported; hash-chain only"

The conformance suite in the repository tests validators and manifest rules. Until a public runtime test suite exists, conformance statements are self-declarations. No implementation is conformant to v1alpha1 today.

Normative text: Conformance.