Installation
Step 1: Define your Alignment Card
An Alignment Card declares what your agent is, what values it holds, and what it will and won’t do autonomously. This is the unified card shape (SDK v2.0.0) — if you have a card from before mid-2026, see the migration note in the specification.Step 2: Generate AP-Traces for decisions
Every significant decision your agent makes should produce a trace.Step 3: Verify traces against your Card
Check that your agent’s behavior matches its declared alignment.similarity_score (0.0-1.0) measures how semantically similar the trace’s behavior is to the declared alignment. A trace can pass all structural checks but still receive a low_behavioral_similarity warning if similarity_score < 0.50.
Step 4: Check coherence before agent coordination
Before your agent works with another agent, verify their values are compatible.Step 5: Detect drift over time
Monitor your agent for behavioral drift from its declared alignment.Complete working example
Here’s a minimal but complete example you can run:Next steps
- Interactive Playground — Try verification in your browser with SSM visualization, no server required (runs client-side via WebAssembly)
- specification — Full protocol specification for implementers
- limitations — What AAP can and cannot guarantee (read this)
- calibration — How similarity thresholds were derived
- A2A integration — Adding AAP to existing A2A agents
- MCP migration — Adding alignment to MCP tools
- Examples — Complete working examples
Common patterns
Decorator for automatic tracing
AAP provides built-in decorators for automatic trace generation:Batch verification
Questions? See the specification or check out the examples.