OpenAgentix

OpenAgentix intends to implement AWP. It is one implementation effort; AWP is a specification, not a platform, and OpenAgentix has no special rights over it.

Status

AWP version	v1alpha1
Conformance profiles	None. OpenAgentix is not conformant to any profile (core, governance, audit, security, mcp, a2a).
Conformance statement	Not published.
Reads AWP manifests	No. OpenAgentix uses its own agents.md syntax (openagentix.io/v1alpha1).

This page makes no conformance claim. It will change only when OpenAgentix publishes a conformance statement for the profiles it actually meets, with every limitation listed (see Conformance).

Mapping from agents.md

A field-by-field mapping between agents.md and AWP v1alpha1, a converter design and the work needed per profile are in docs/mapping-agents-md.md. In short:

• Identity, classification, budgets, manual and cron triggers, agents with their models and instructions, exact tool grants and per-tool approval map cleanly or with small, documented losses.
• Conditional steps (when), tool argument constraints, prefix wildcards and typed handovers have no AWP v1alpha1 equivalent. An export that drops them would run with fewer restrictions on another runtime, so the proposed converter refuses to produce one by default.
• Many AWP features (typed inputs, step graphs, command and approval steps, data and model policies, environments, risk levels, Policy manifests, the audit event model, signatures, remote A2A agents) have no agents.md equivalent.

Compliance

AWP provides machine-readable governance primitives that can help organizations implement and enforce their own compliance requirements. Compliance depends on the implementation, organizational controls and applicable regulatory requirements.