Support cross-role governance enforcement

[bokelley]

Tracks Python SDK support for the cross-role governance enforcement bundle in adcontextprotocol/adcp#6214 and its notice-only companion adcontextprotocol/adcp#6213.

Required work

• Regenerate Pydantic models for typed target_agent, commitments, capability declarations, and outcome shapes.
• Add SDK-normalized verdict guards plus proposal/execution commitment and applicability helpers.
• Update server/governance.py, decisioning documentation, and dispatch so conditions are intent-only and services consume opaque signed context without plan access.
• Add issuer/verifier and service-enforcement hooks for JCS payload hashing, compact JWS, critical claims, audience/caller/task/amount/currency/expiry, and replay handling.
• Run the shared protocol fixture, including the 27 deterministic compact-JWS accept/reject cases published by feat(governance): define cross-role enforcement adcp#6214 (closing Add deterministic signed-JWS governance authorization vectors adcp#6215).

Acceptance

• Typed end-to-end intent, execution, and outcome flow.
• All binding mismatches and unknown critical claims fail closed.
• Non-governance and legacy capability flows remain compatible.

Feature remains experimental under governance.campaign; support should land for the 3.2 beta; the beta-to-GA period provides the experimental notice window.

[bokelley]

Triage

Classification: Feature request (tracking / epic)
Bucket(s): signing, validation, cross-repo (none of these labels currently exist in this repo — gap noted for maintainers)
Status: deferred

What the experts said:

Pre-classification as a tracking/blocked issue drives the outcome directly; expert consultation is deferred until the protocol PR publishes and implementation can begin.

My take: This issue is self-described as a tracking issue ("Tracks Python SDK support for...") and is explicitly blocked on two upstream events: publication of the implementation branch (accepted-vs-pending-start) and expiry of the notice window attached to the companion protocol PR. The body states "The draft implementation PR will be added after publication" — no SDK implementation work can start yet. When the protocol PR merges and the notice window closes, this epic covers significant surface area (codegen regeneration, typed verdict guards, signing/JWS hooks, protocol test vectors) and would benefit from being converted to a structured task list at that point.

Blocked-on: adcontextprotocol/adcp#6213 — resurfaces on merge.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_01CqSiDmGx4nMyXVZTAoSPcK

---

Generated by Claude Code