Skip to content

Latest commit

 

History

History
139 lines (114 loc) · 5.7 KB

README.md

File metadata and controls

139 lines (114 loc) · 5.7 KB

AWP – Agentic Workflow Protocol

AWP - Agentic Workflow Protocol

An open, declarative standard for defining, governing, executing and auditing agentic workflows.

MCP connects agents to tools. A2A connects agents to agents. AWP defines how agents work.

Status: draft / alpha. The specification has three draft versions: v1alpha1, v1alpha2 (v1alpha1 plus step iteration, forEach) and the proposed v1alpha3 (v1alpha2 aligned with the Kubernetes resource model, built from Draft AEPs). All are working drafts: fields, semantics and conformance profiles may change incompatibly before v1. Do not rely on them for production interoperability yet.

What AWP is

AWP is a specification, not a platform. It describes, in a vendor-neutral and machine-readable way:

  • what an agentic workflow does (agents, tools, steps, triggers, inputs),
  • within which limits it may run (budgets, resources, tool permissions, environments),
  • under which governance it runs (ownership, data classification, data residency, model governance, human approval, risk levels, separation of duties, supply-chain integrity),
  • what it leaves behind (audit events, decision traces, reproducibility records).

AWP complements existing protocols instead of replacing them:

Protocol Scope
MCP Agents ↔ tools and resources
A2A Agent ↔ agent communication
AWP Definition, governance, execution and audit of agentic workflows

A minimal manifest:

apiVersion: awp.agenticworkflowprotocol.org/v1alpha1
kind: Workflow
metadata:
  name: vulnerability-fixer
  version: 0.1.0
  owner:
    team: security-team
  classification: internal
spec:
  triggers:
    - type: manual
  budget:
    maxCostUsd: 2.00
    maxSteps: 30
    maxDuration: 15m
  mcpServers:
    - name: github
      transport: streamable-http
      url: https://mcp.example.com/github
  agents:
    - id: fixer
      model:
        provider: ollama
        name: qwen3
      tools:
        - type: mcp
          server: github
          tools: [get_file_contents, push_files]
  workflow:
    - id: fix
      agent: fixer
    - id: test
      type: command
      command: npm test
      dependsOn: [fix]
  permissions:
    default: deny
    tools:
      github.get_file_contents:
        allow: true
      github.push_files:
        allow: true
      shell.execute:
        allow: true

Compliance

AWP provides machine-readable governance primitives that can help organizations implement and enforce their own compliance requirements. AWP itself does not make any system compliant with any law or regulation. Compliance depends on the implementation, organizational controls and applicable regulatory requirements.

Validate, view and edit a manifest

Implementations

Implementation Status
- No implementation has published a conformance statement yet.

Call for implementations: AWP is not tied to any runtime. If you build a runtime, validator or tool that implements AWP, open an issue or pull request to be listed here. Listing requires a public statement of the supported conformance profiles.

Repository layout

Path Content
spec/ Normative specification text (planned for v1alpha1)
docs/ Concept documentation and website plan
site/ Website (Astro Starlight), see site/README.md
CNAME Custom domain for GitHub Pages (agenticworkflowprotocol.org)

Contributing

Contributions are welcome. Please read CONTRIBUTING.md (DCO sign-off, Conventional Commits) and the Code of Conduct. How decisions are made is described in GOVERNANCE.md. Security issues: see SECURITY.md.

Questions and ideas: GitHub Issues and Discussions. Contact: info@agenticworkflowprotocol.org

License

  • Specification text and documentation: CC BY 4.0
  • Code, schemas, conformance tests and tooling: Apache-2.0