> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adcontextprotocol.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Task reference

> Task reference for AdCP campaign governance — sync_plans, check_governance, report_plan_outcome, and get_plan_audit_logs.

# Campaign Governance tasks

Campaign Governance has four tasks.

| Task                                           | Direction                    | Description                                                                                                                                                      |
| ---------------------------------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`sync_plans`](./sync_plans)                   | Orchestrator → Gov           | Push campaign plans with budget, channels, flight dates, and authorized markets                                                                                  |
| [`check_governance`](./check_governance)       | Orchestrator or Seller → Gov | Universal governance check. Orchestrator calls with `binding: "proposed"` before sending to a seller. Seller calls with `binding: "committed"` before executing. |
| [`report_plan_outcome`](./report_plan_outcome) | Orchestrator → Gov           | Post-action report: "here's what happened." Gov updates state and returns any findings                                                                           |
| [`get_plan_audit_logs`](./get_plan_audit_logs) | Orchestrator → Gov           | Read governance state, budget burn, and audit trail                                                                                                              |

`sync_plans` configures the rules. `check_governance` is the universal governance gate — both the orchestrator (proposed) and the seller (committed) call it to validate actions against the plan. `report_plan_outcome` closes the loop after execution. `get_plan_audit_logs` is read-only, for monitoring and reporting.