feat!: sync_governance task, remove governance from sync/list#1644
Merged
Conversation
On explicit-account sellers, accounts are pre-created and sync_accounts is not used. This adds an optional governance_agents field to the list_accounts request so buyers can register governance endpoints against discovered accounts, enabling the check_governance round-trip. Closes #1643 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace top-level governance_agents array with account_governance object keyed by account_id. This mirrors the per-account pattern from sync_accounts and lets buyers assign different governance agents to different accounts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Changes account_governance from a flat map keyed by account_id to an
array of {account, governance_agents} entries where account is an
account-ref (either account_id or brand+operator). This supports both
explicit and implicit account types.
Updates docs with examples for both account reference styles and
clarifies replace semantics.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Add maxItems/maxLength bounds to governance_agents in sync-accounts and account.json to match list-accounts (maxItems: 10 agents, maxItems: 20 categories, maxLength: 64 on category strings) - Require HTTPS on governance agent URLs across all three schemas - Add authorization scoping guidance: seller MUST verify agent owns referenced accounts before persisting governance - Fix changeset field name (governance_agents → account_governance) - Wrap JSON examples in CodeGroup Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Governance agent registration is now a dedicated task rather than a side-effect on sync_accounts or list_accounts: - Add register_governance request/response schemas with account-ref support (account_id or brand+operator) - Remove governance_agents from sync-accounts-request.json - Remove account_governance from list-accounts-request.json - Add register_governance docs, nav entry, release notes - Update sync_accounts and list_accounts docs BREAKING CHANGE: governance_agents removed from sync_accounts request and list_accounts request. Use register_governance instead. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
account.json is a read/response schema — governance agent credentials are write-only and must not be echoed in list_accounts responses. Remove authentication from account.json governance_agents items, matching the pattern already used in register-governance-response.json. Also fix schema links to use /schemas/latest/ (unreleased) and tighten response governance_agents to additionalProperties: false. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Update 5 docs that still referenced governance_agents on sync_accounts: - governance/campaign/specification.mdx (setup example + multi-agent) - governance/campaign/tasks/check_governance.mdx (committed binding) - governance/campaign/index.mdx (seller-side overview) - learning/tracks/platform.mdx (learning track bullet) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
EmmaLouise2018
approved these changes
Mar 23, 2026
Aligns with existing protocol verb pattern: sync_accounts, sync_plans, sync_creatives. "Sync" communicates replace semantics naturally. Renames schemas, docs, nav entries, and all cross-references. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace residual "registration" language with "sync/configuration", update response status enum from "registered" to "synced", fix breaking changes table heading. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Add sync_governance to accounts overview tasks table - Add prerequisite note to campaign governance tasks index - Add sync_governance to governance specialist module (demo list, prereq card, lab exercise) - Add sync_governance to governance overview walkthrough (Step 0) - Update publisher track seller-side governance bullet - Fix stale sync_accounts reference in specification.mdx - Add pattern constraint (^[a-z][a-z0-9_]*$) to governance category strings across all three schemas to prevent injection Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sync_governancetask for syncing governance agent endpoints to specific accounts, supporting both explicit (account_id) and implicit (brand+operator) account referencesgovernance_agentsfromsync_accountsrequest schema (breaking change)account_governancefromlist_accountsrequest schema —list_accountsreturns to a pure read operationauthenticationcredentials fromaccount.jsonresponse schema (write-only viasync_governance)maxItems/maxLengthbounds and HTTPS requirement on governance URLsCloses #1643
Test plan
register_governanceorgovernance_agentsonsync_accounts🤖 Generated with Claude Code