Primary buyer
Marketing operations and agencies
Proposed solution design
Bound campaign changes before a provider applies them.
A campaign-budget increase or audience export needs accountable authority, exact scope, and evidence from the system that applies it.
Industry designs describe target integrations. A page or example operation is not an available adapter, registered predicate, or deployed service.
Protected action
A campaign-budget increase or audience export
Proposed typed constraints
Campaign, account, currency, daily limit, destination, record count, and expiry
Integration path
Bind a structured provider mutation to separately signed business authority; use destination read-back and reconciliation to establish the outcome.
Maturity & remaining requirements
Provider adapters, shared budget accounting, audience privacy controls, and a customer demonstration remain proposed.
Demonstration scope
Use the existing credential-rotation evaluation to inspect shared authorization mechanisms. It does not execute this industry-specific action. A domain demonstration requires its own adapter, protected destination, and observed effect.
Use case / Marketing operations and agencies
Design the boundary for a campaign-budget increase or audience export.
Illustrative integration review. These controls explain the design; they do not submit requests, grant authority, or execute an action.
Inspect the flow
Stage 1
Define the action
A campaign-budget increase or audience export
Shared contract, domain-specific integration
Use the existing Living Intent Contract and closed predicate envelope. New domain constraints require registered typed predicates, documented semantics, and one deterministic evaluator. Domain content and secrets stay outside the envelope. No new universal protocol or compatibility certification is claimed.
- Authority: signed scope
- Decision: deterministic policy
- Execution: protected destination
- Evidence: observed outcome
Integration references to assess
These external specifications and programs inform integration design. Links do not establish a partnership, implemented adapter, or 2AYE conformance.