Optionalcontext?: Omit<Omit<{}, "bank">, "authentication"> & { authentication?: unknown }Optionalgovernance_context?: stringArray of accounts accessible to the authenticated agent. Each entry is the full Account object plus an optional authorization object describing what the calling agent is permitted to do on that account.
Optionalerrors?: {Task-specific errors and warnings
Optionalpagination?: { has_more: boolean; cursor?: string; total_count?: number }Whether more results are available beyond this page
Optionalcursor?: stringOpaque cursor to pass in the next request to fetch the next page. Only present when has_more is true.
Optionaltotal_count?: numberTotal number of items matching the query across all pages. Optional because not all backends can efficiently compute this.
Optionalext?: Omit<Omit<{}, "bank">, "authentication"> & { authentication?: unknown }Optionalsummary: string
Governance context token issued by the account's governance agent during check_governance. Buyers attach it to governed purchase requests (media buys, rights acquisitions, signal activations, creative services); sellers persist it and include it on all subsequent governance calls for that action's lifecycle. An account binds to one governance agent (see sync_governance); governance is phased across
purchase/modification/delivery, not partitioned across specialist agents, so the envelope carries a single token for the full lifecycle.Value format: governance agents MUST emit a compact JWS per the AdCP JWS profile (see Security — Signed Governance Context). Sellers MAY verify; sellers that do not verify MUST persist and forward the token unchanged. In 3.1 all sellers MUST verify. Non-JWS values from pre-3.0 governance agents are deprecated.
This is the primary correlation key for audit and reporting across the governance lifecycle.