@adcp/sdk 8.1.0-beta.6 → 8.1.0-beta.8

package/dist/lib/types/provide-performance-feedback.d.ts

@@ -0,0 +1,218 @@
+// AUTO-GENERATED — DO NOT EDIT.
+// Per-tool .d.ts slice for `provide_performance_feedback`. Built from the published
+// `tools.generated.d.ts` + `core.generated.d.ts` + `enums.generated.d.ts`
+// by `scripts/generate-per-tool-types.ts`.
+//
+// Self-contained: imports nothing from the broader SDK. Adopters who
+// import only this slice pay a fraction of the tsc cost of pulling in
+// `@adcp/sdk` root — useful when strict + skipLibCheck:false adopters
+// hit memory pressure on the full surface.
+
+/**
+ * Request payload for provide_performance_feedback task
+ */
+export interface ProvidePerformanceFeedbackRequest {
+    /**
+     * Release-precision AdCP version (VERSION.RELEASE, e.g. "3.0", "3.1", "3.1-beta"). On a request: the buyer's release pin — the seller validates against its supported_versions and returns VERSION_UNSUPPORTED on cross-major mismatch, or downshifts to the highest supported release within the same major. On a response: the release the seller actually served — clients SHOULD validate the response against that release's schema, not against their pin. Patches are not negotiated; surface them as build_version on capabilities for operational visibility. When omitted, falls back to adcp_major_version (deprecated) or server default. Buyers SHOULD emit both adcp_version and adcp_major_version through 3.x to remain compatible with sellers that only read the legacy field. NORMALIZATION: SDKs that read full-semver values from bundle metadata (e.g. ComplianceIndex.published_version = "3.1.0-beta.1") MUST normalize to release-precision ("3.1-beta.1") before emitting on the wire — meta-field values are NOT valid wire values.
+     */
+    adcp_version?: string;
+    /**
+     * DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.
+     */
+    adcp_major_version?: number;
+    /**
+     * Seller's media buy identifier
+     * @minLength 1
+     */
+    media_buy_id: string;
+    /**
+     * Client-generated unique key for this request. Prevents duplicate feedback submissions on retries. MUST be unique per (seller, request) pair to prevent cross-seller correlation. Use a fresh UUID v4 for each request.
+     * @minLength 16
+     * @maxLength 255
+     * @pattern ^[A-Za-z0-9_.:-]{16,255}$
+     */
+    idempotency_key: string;
+    measurement_period: DatetimeRange;
+    /**
+     * Normalized performance score (0.0 = no value, 1.0 = expected, >1.0 = above expected)
+     * @minimum 0
+     */
+    performance_index: number;
+    /**
+     * Specific package within the media buy (if feedback is package-specific)
+     * @minLength 1
+     */
+    package_id?: string;
+    /**
+     * Specific creative asset (if feedback is creative-specific)
+     * @minLength 1
+     */
+    creative_id?: string;
+    metric_type?: MetricTypeDeprecated;
+    feedback_source?: FeedbackSource;
+    context?: ContextObject;
+    ext?: ExtensionObject;
+}
+
+/**
+ * Response payload for provide_performance_feedback task. Returns either success confirmation OR error information, never both.
+ */
+export type ProvidePerformanceFeedbackResponse = {
+    /**
+     * Session/conversation identifier for tracking related operations across multiple task invocations. Managed by the protocol layer to maintain conversational context. Distinct from `context` (per-request opaque echo, see below).
+     */
+    context_id?: string;
+    context?: ContextObject;
+    /**
+     * Unique identifier for tracking asynchronous operations. Present when a task requires extended processing time. Used to query task status and retrieve results when complete.
+     */
+    task_id?: string;
+    status: TaskStatus;
+    /**
+     * Human-readable summary of the task result. Provides natural language explanation of what happened, suitable for display to end users or for AI agent comprehension. Generated by the protocol layer based on the task response.
+     */
+    message?: string;
+    /**
+     * ISO 8601 timestamp when the response was generated. Useful for debugging, logging, cache validation, and tracking async operation progress.
+     */
+    timestamp?: string;
+    /**
+     * Set to true when this response was returned from the idempotency cache rather than from a fresh execution. Set to false (or omitted) when the request was executed fresh. Buyers use this to distinguish cached replays from new executions — matters for billing reconciliation, audit logs, state-machine routing (cached state-tracking fields are historical snapshots, not current state — re-read via the resource's read endpoint), and any downstream system that assumes exactly-once event semantics. From 3.1 onward, `replayed` MAY appear on responses to any request that resolved via the idempotency cache, including read tools — universal `idempotency_key` (see security.mdx §Idempotency) means the cache holds read responses too.
+     */
+    replayed?: boolean;
+    adcp_error?: Error;
+    push_notification_config?: PushNotificationConfig;
+    /**
+     * 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.
+     */
+    governance_context?: string;
+    /**
+     * Conceptual grouping for the task-specific response data defined by individual task response schemas (e.g., get-products-response.json, create-media-buy-response.json). `payload` is a documentary construct — it is NOT a required wire field, and its on-the-wire shape depends on transport (see Transport serialization below). Task response schemas declare body fields without wrapping them in a `payload` object; the wire representation places those body fields per transport convention. On MCP the body fields appear as siblings of envelope fields at the root of the tool response; on A2A they appear inside `task.artifacts[0].parts[].DataPart`; on REST they appear at the root of the JSON body.
+     */
+    payload?: {};
+    /**
+     * Release-precision AdCP version (VERSION.RELEASE, e.g. "3.0", "3.1", "3.1-beta"). On a request: the buyer's release pin — the seller validates against its supported_versions and returns VERSION_UNSUPPORTED on cross-major mismatch, or downshifts to the highest supported release within the same major. On a response: the release the seller actually served — clients SHOULD validate the response against that release's schema, not against their pin. Patches are not negotiated; surface them as build_version on capabilities for operational visibility. When omitted, falls back to adcp_major_version (deprecated) or server default. Buyers SHOULD emit both adcp_version and adcp_major_version through 3.x to remain compatible with sellers that only read the legacy field. NORMALIZATION: SDKs that read full-semver values from bundle metadata (e.g. ComplianceIndex.published_version = "3.1.0-beta.1") MUST normalize to release-precision ("3.1-beta.1") before emitting on the wire — meta-field values are NOT valid wire values.
+     */
+    adcp_version?: string;
+    /**
+     * DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.
+     */
+    adcp_major_version?: number;
+} & (ProvidePerformanceFeedbackSuccess | ProvidePerformanceFeedbackError);
+
+/**
+ * Success response - feedback received and processed
+ */
+export interface ProvidePerformanceFeedbackSuccess {
+    /**
+     * Whether the performance feedback was successfully received
+     */
+    success: true;
+    /**
+     * When true, this response contains simulated data from sandbox mode.
+     */
+    sandbox?: boolean;
+    context?: ContextObject;
+    ext?: ExtensionObject;
+}
+
+/**
+ * Error response - feedback rejected or could not be processed
+ */
+export interface ProvidePerformanceFeedbackError {
+    /**
+     * Array of errors explaining why feedback was rejected (e.g., invalid measurement period, missing campaign data)
+     */
+    errors: Error[];
+    context?: ContextObject;
+    ext?: ExtensionObject;
+}
+
+/**
+ * Legacy authentication schemes for the webhook auth block. Bearer: token sent in Authorization header. HMAC-SHA256: legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit the authentication block and use the RFC 9421 webhook signing profile (applicable on schemas where authentication is optional). Removed in AdCP 4.0.
+ */
+export type AuthenticationScheme = 'Bearer' | 'HMAC-SHA256';
+
+/**
+ * Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.
+ */
+export interface ContextObject {
+}
+
+/**
+ * Time period for performance measurement
+ */
+export interface DatetimeRange {
+    /**
+     * Start timestamp (inclusive), ISO 8601
+     * @format date-time
+     */
+    start: string;
+    /**
+     * End timestamp (inclusive), ISO 8601
+     * @format date-time
+     */
+    end: string;
+}
+
+/**
+ * Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.
+ */
+export interface ExtensionObject {
+}
+
+/**
+ * Source of the performance data
+ */
+export type FeedbackSource = 'buyer_attribution' | 'third_party_measurement' | 'platform_analytics' | 'verification_partner';
+
+/**
+ * The business metric being measured
+ */
+export type MetricTypeDeprecated = 'overall_performance' | 'conversion_rate' | 'brand_lift' | 'click_through_rate' | 'completion_rate' | 'viewability' | 'brand_safety' | 'cost_efficiency';
+
+/**
+ * Push notification configuration for async task updates (A2A and REST protocols). Echoed from the request to confirm webhook settings. Specifies URL, authentication scheme (Bearer or HMAC-SHA256), and credentials. MCP uses progress notifications instead of webhooks.
+ */
+export interface PushNotificationConfig {
+    /**
+     * Webhook endpoint URL for task status notifications. The wire contract is unconstrained beyond `format: "uri"` — in particular, publishers SHOULD NOT enforce a destination-port allowlist by default, since buyers legitimately host receivers on non-standard TLS ports (`:9443`, `:4443`, path-routed multi-tenant gateways). The SSRF guard the protocol relies on is the IP-range check + DNS-rebinding-resistant connect pin defined in [Webhook URL validation (SSRF)](/docs/building/by-layer/L1/security#webhook-url-validation-ssrf), not port filtering. Operators who want a hardened destination-port allowlist as defense-in-depth (e.g., locked-down enterprise egress) opt in explicitly — see [Destination port: permissive by default](/docs/building/by-layer/L1/security#destination-port-permissive-by-default).
+     */
+    url: string;
+    /**
+     * Buyer-supplied correlation identifier for the operation that will produce webhooks against this registration. The seller MUST echo this value verbatim into every webhook payload's `operation_id` field (see [`mcp-webhook-payload.json`](/schemas/core/mcp-webhook-payload.json) and [Webhooks — Operation IDs](/docs/building/by-layer/L3/webhooks#operation-ids-and-url-templates)). Buyers SHOULD generate a unique value per task invocation (UUID recommended). This field is the canonical registration channel for `operation_id`; buyers MAY additionally embed the same value in the URL path or query as a routing aid for their own HTTP server, but the URL is opaque to the seller and the wire-level source of truth is this field. Sellers MUST NOT parse the URL to recover `operation_id`. Sellers that receive a webhook registration without `operation_id` MAY reject the task with `INVALID_REQUEST`.
+     * @minLength 1
+     * @maxLength 255
+     * @pattern ^[A-Za-z0-9_.:-]{1,255}$
+     */
+    operation_id?: string;
+    /**
+     * Optional client-provided token for webhook validation. The seller MUST echo this value verbatim in every webhook payload's `token` field (see [`mcp-webhook-payload.json`](/schemas/core/mcp-webhook-payload.json) for the receiver-side validation obligation). Length bounds give receivers a defensive range check on the echoed value; senders SHOULD generate tokens with at least 128 bits of entropy (≥22 base64url characters). This is a complementary authenticity mechanism that can layer on top of the RFC 9421 webhook signature — unlike the `authentication` block below, it is not on the 4.0 removal track. Receivers that registered both a signing key (RFC 9421) and a `token` MUST NOT treat a valid token echo as authorization to skip signature verification; both checks remain independent obligations.
+     * @minLength 16
+     * @maxLength 4096
+     */
+    token?: string;
+    /**
+     * Legacy authentication configuration (A2A-compatible). Opts the seller into Bearer or HMAC-SHA256 signing instead of the default RFC 9421 webhook profile. Deprecated; removed in AdCP 4.0. **Precedence is a switch, not a fallback:** presence of this block selects the legacy scheme; absence selects 9421. A seller MUST NOT sign the same webhook both ways, and a buyer MUST NOT attempt 'try 9421 first, fall back to HMAC' verification — signature mode is determined solely by whether this block was present at registration time. The seller's baseline 9421 webhook-signing key published at its brand.json `agents[]` `jwks_uri` does not override this selector; it is always discoverable but only used when `authentication` is omitted. See docs/building/implementation/security.mdx#webhook-callbacks for the full precedence and downgrade-resistance rules (including the `webhook_mode_mismatch` rejection a buyer MUST apply when a received webhook's signing mode does not match the registered mode).
+     */
+    authentication?: {
+        /**
+         * Array of authentication schemes. Supported: ['Bearer'] for simple token auth, ['HMAC-SHA256'] for legacy shared-secret signing. Both are deprecated; new integrations SHOULD omit `authentication` and use the RFC 9421 webhook profile.
+         */
+        schemes: AuthenticationScheme[];
+        /**
+         * Credentials for the legacy scheme. For Bearer: token sent in Authorization header. For HMAC-SHA256: shared secret used to generate signature. Minimum 32 characters. Exchanged out-of-band during onboarding.
+         * @minLength 32
+         */
+        credentials: string;
+    };
+}
+
+/**
+ * Current task execution state. Indicates whether the task is completed, in progress (working), submitted for async processing, failed, or requires user input. REQUIRED on every task response envelope. Synchronous tasks (including read-only metadata calls like `get_adcp_capabilities`) MUST emit `status: "completed"`; async tasks emit `submitted`, `working`, `input-required`, etc. per their lifecycle. Agents MUST NOT emit the legacy task_status or response_status fields alongside this field — the status field is the single authoritative task state.
+ */
+export type TaskStatus = 'submitted' | 'working' | 'input-required' | 'completed' | 'canceled' | 'failed' | 'rejected' | 'auth-required' | 'unknown';

package/dist/lib/types/report-plan-outcome.d.ts

@@ -0,0 +1,433 @@
+// AUTO-GENERATED — DO NOT EDIT.
+// Per-tool .d.ts slice for `report_plan_outcome`. Built from the published
+// `tools.generated.d.ts` + `core.generated.d.ts` + `enums.generated.d.ts`
+// by `scripts/generate-per-tool-types.ts`.
+//
+// Self-contained: imports nothing from the broader SDK. Adopters who
+// import only this slice pay a fraction of the tsc cost of pulling in
+// `@adcp/sdk` root — useful when strict + skipLibCheck:false adopters
+// hit memory pressure on the full surface.
+
+/**
+ * Report the outcome of an action to the governance agent. Called by the orchestrator (buyer-side agent) after a seller responds. This is the 'after' half of the governance loop. Sellers do not call this task -- they report delivery data via check_governance with phase 'delivery'.
+ */
+export interface ReportPlanOutcomeRequest {
+    /**
+     * Release-precision AdCP version (VERSION.RELEASE, e.g. "3.0", "3.1", "3.1-beta"). On a request: the buyer's release pin — the seller validates against its supported_versions and returns VERSION_UNSUPPORTED on cross-major mismatch, or downshifts to the highest supported release within the same major. On a response: the release the seller actually served — clients SHOULD validate the response against that release's schema, not against their pin. Patches are not negotiated; surface them as build_version on capabilities for operational visibility. When omitted, falls back to adcp_major_version (deprecated) or server default. Buyers SHOULD emit both adcp_version and adcp_major_version through 3.x to remain compatible with sellers that only read the legacy field. NORMALIZATION: SDKs that read full-semver values from bundle metadata (e.g. ComplianceIndex.published_version = "3.1.0-beta.1") MUST normalize to release-precision ("3.1-beta.1") before emitting on the wire — meta-field values are NOT valid wire values.
+     */
+    adcp_version?: string;
+    /**
+     * DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.
+     */
+    adcp_major_version?: number;
+    /**
+     * The plan this outcome is for. The plan uniquely scopes the account and operator; do not include a separate `account` field — the governance agent resolves account from the plan. Including `account` is rejected by `additionalProperties: false`.
+     */
+    plan_id: string;
+    /**
+     * The check_id from check_governance. Links the outcome to the governance check that authorized it. Required for 'completed' and 'failed' outcomes.
+     */
+    check_id?: string;
+    /**
+     * Client-generated unique key for this request. Prevents duplicate outcome reports on retries. MUST be unique per (seller, request) pair to prevent cross-seller correlation. Use a fresh UUID v4 for each request.
+     * @minLength 16
+     * @maxLength 255
+     * @pattern ^[A-Za-z0-9_.:-]{16,255}$
+     */
+    idempotency_key: string;
+    purchase_type?: PurchaseType;
+    outcome: OutcomeType;
+    /**
+     * The seller's full response. Required when outcome is 'completed'.
+     */
+    seller_response?: {
+        /**
+         * The seller's identifier for the created resource (e.g., media_buy_id, rights_grant_id, deployment_id). Not interpreted by the governance agent — included in audit logs for human-readable traceability alongside the opaque governance_context.
+         * @maxLength 255
+         */
+        seller_reference?: string;
+        /**
+         * Total budget committed across all confirmed packages. When present, the governance agent uses this directly instead of summing package budgets.
+         * @minimum 0
+         */
+        committed_budget?: number;
+        /**
+         * Confirmed packages with actual budget and targeting.
+         */
+        packages?: {
+            /**
+             * @minimum 0
+             */
+            budget?: number;
+        }[];
+        planned_delivery?: PlannedDelivery;
+        /**
+         * ISO 8601 deadline for creative submission.
+         * @format date-time
+         */
+        creative_deadline?: string;
+    };
+    /**
+     * Delivery metrics. Required when outcome is 'delivery'.
+     */
+    delivery?: {
+        /**
+         * Start and end timestamps for the reporting window.
+         */
+        reporting_period?: {
+            /**
+             * @format date-time
+             */
+            start: string;
+            /**
+             * @format date-time
+             */
+            end: string;
+        };
+        /**
+         * Impressions delivered in the period.
+         * @minimum 0
+         */
+        impressions?: number;
+        /**
+         * Spend in the period.
+         */
+        spend?: number;
+        /**
+         * Effective CPM for the period.
+         */
+        cpm?: number;
+        /**
+         * Viewability rate (0-1).
+         */
+        viewability_rate?: number;
+        /**
+         * Video completion rate (0-1).
+         */
+        completion_rate?: number;
+    };
+    /**
+     * Error details. Required when outcome is 'failed'.
+     */
+    error?: {
+        /**
+         * Error code from the seller.
+         */
+        code?: string;
+        /**
+         * Human-readable error description.
+         */
+        message?: string;
+    };
+    /**
+     * Opaque governance context from the check_governance response that authorized this action. Enables the governance agent to correlate the outcome to the original check.
+     * @minLength 1
+     * @maxLength 4096
+     * @pattern ^[\x20-\x7E]+$
+     */
+    governance_context: string;
+    context?: ContextObject;
+    ext?: ExtensionObject;
+}
+
+/**
+ * Response from reporting an action outcome. Only returned to the orchestrator (buyer-side agent) that manages the plan. Sellers report delivery data via check_governance with phase 'delivery', not via this task.
+ */
+export interface ReportPlanOutcomeResponse {
+    /**
+     * Release-precision AdCP version (VERSION.RELEASE, e.g. "3.0", "3.1", "3.1-beta"). On a request: the buyer's release pin — the seller validates against its supported_versions and returns VERSION_UNSUPPORTED on cross-major mismatch, or downshifts to the highest supported release within the same major. On a response: the release the seller actually served — clients SHOULD validate the response against that release's schema, not against their pin. Patches are not negotiated; surface them as build_version on capabilities for operational visibility. When omitted, falls back to adcp_major_version (deprecated) or server default. Buyers SHOULD emit both adcp_version and adcp_major_version through 3.x to remain compatible with sellers that only read the legacy field. NORMALIZATION: SDKs that read full-semver values from bundle metadata (e.g. ComplianceIndex.published_version = "3.1.0-beta.1") MUST normalize to release-precision ("3.1-beta.1") before emitting on the wire — meta-field values are NOT valid wire values.
+     */
+    adcp_version?: string;
+    /**
+     * DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.
+     */
+    adcp_major_version?: number;
+    /**
+     * Unique identifier for this outcome record.
+     */
+    outcome_id: string;
+    /**
+     * Outcome state. 'accepted' means state updated with no issues. 'findings' means issues were detected. Renamed from `status` in 3.1 to free the top-level `status` key for the envelope task-status (TaskStatus) under MCP flat-on-the-wire serialization.
+     */
+    outcome_state: 'accepted' | 'findings';
+    /**
+     * Budget committed from this outcome. Present for 'completed' and 'failed' outcomes.
+     */
+    committed_budget?: number;
+    /**
+     * Issues detected. Present only when outcome_state is 'findings'.
+     */
+    findings?: {
+        /**
+         * Which validation category flagged the issue.
+         */
+        category_id: string;
+        severity: EscalationSeverity;
+        /**
+         * Human-readable description of the issue.
+         */
+        explanation: string;
+        /**
+         * Structured details for programmatic consumption.
+         */
+        details?: {};
+    }[];
+    /**
+     * Updated plan budget state. Present for 'completed' and 'failed' outcomes.
+     */
+    plan_summary?: {
+        /**
+         * Total budget committed across all campaigns in the plan.
+         */
+        total_committed?: number;
+        /**
+         * Authorized budget minus total committed.
+         */
+        budget_remaining?: number;
+    };
+    /**
+     * Set to true when this response was returned from the idempotency cache rather than from a fresh execution. Set to false (or omitted) when the request was executed fresh. Buyers use this to distinguish cached replays from new executions — matters for billing reconciliation, audit logs, state-machine routing (cached state-tracking fields are historical snapshots, not current state — re-read via the resource's read endpoint), and any downstream system that assumes exactly-once event semantics. From 3.1 onward, `replayed` MAY appear on responses to any request that resolved via the idempotency cache, including read tools — universal `idempotency_key` (see security.mdx §Idempotency) means the cache holds read responses too.
+     */
+    replayed?: boolean;
+    context?: ContextObject;
+    ext?: ExtensionObject;
+}
+
+/**
+ * Selects an audience by signal reference or natural language description. Uses 'type' as the primary discriminator (signal vs description). Signal selectors additionally use 'value_type' to determine the targeting expression format (matching signal-targeting.json variants).
+ */
+export type AudienceSelector = {
+    /**
+     * Discriminator for signal-based selectors
+     */
+    type: 'signal';
+    signal_id: SignalID;
+    /**
+     * Discriminator for binary signals
+     */
+    value_type: 'binary';
+    /**
+     * Whether to include (true) or exclude (false) users matching this signal
+     */
+    value: boolean;
+} | {
+    /**
+     * Discriminator for signal-based selectors
+     */
+    type: 'signal';
+    signal_id: SignalID;
+    /**
+     * Discriminator for categorical signals
+     */
+    value_type: 'categorical';
+    /**
+     * Values to target. Users with any of these values will be included.
+     */
+    values: string[];
+} | {
+    /**
+     * Discriminator for signal-based selectors
+     */
+    type: 'signal';
+    signal_id: SignalID;
+    /**
+     * Discriminator for numeric signals
+     */
+    value_type: 'numeric';
+    /**
+     * Minimum value (inclusive). Omit for no minimum. Must be <= max_value when both are provided.
+     */
+    min_value?: number;
+    /**
+     * Maximum value (inclusive). Omit for no maximum. Must be >= min_value when both are provided.
+     */
+    max_value?: number;
+} | {
+    /**
+     * Discriminator for description-based selectors
+     */
+    type: 'description';
+    /**
+     * Natural language description of the audience (e.g., 'likely EV buyers', 'high net worth individuals', 'vulnerable communities')
+     * @minLength 1
+     * @maxLength 2000
+     */
+    description: string;
+    /**
+     * Optional grouping hint for the governance agent (e.g., 'demographic', 'behavioral', 'contextual', 'financial')
+     */
+    category?: string;
+};
+
+/**
+ * Opaque correlation data that is echoed unchanged in responses. Used for internal tracking, UI session IDs, trace IDs, and other caller-specific identifiers that don't affect protocol behavior. Context data is never parsed by AdCP agents - it's simply preserved and returned.
+ */
+export interface ContextObject {
+}
+
+/**
+ * A time duration expressed as an interval and unit. Used for frequency cap windows, attribution windows, reach optimization windows, time budgets, and other time-based settings. When unit is 'campaign', interval must be 1 — the window spans the full campaign flight.
+ */
+export interface Duration {
+    /**
+     * Number of time units. Must be 1 when unit is 'campaign'.
+     * @minimum 1
+     */
+    interval: number;
+    /**
+     * Time unit. 'seconds' for sub-minute precision. 'campaign' spans the full campaign flight.
+     */
+    unit: 'seconds' | 'minutes' | 'hours' | 'days' | 'campaign';
+}
+
+/**
+ * Finding severity.
+ */
+export type EscalationSeverity = 'info' | 'warning' | 'critical';
+
+/**
+ * Extension object for platform-specific, vendor-namespaced parameters. Extensions are always optional and must be namespaced under a vendor/platform key (e.g., ext.gam, ext.roku). Used for custom capabilities, partner-specific configuration, and features being proposed for standardization.
+ */
+export interface ExtensionObject {
+}
+
+/**
+ * Frequency capping settings for package-level application. Two types of frequency control can be used independently or together: suppress enforces a cooldown between consecutive exposures; max_impressions + per + window caps total exposures per entity in a time window. When both suppress and max_impressions are set, an impression is delivered only if both constraints permit it (AND semantics). At least one of suppress, suppress_minutes, or max_impressions must be set.
+ */
+export type FrequencyCap = {
+    [k: string]: unknown | undefined;
+} & {
+    /**
+     * Cooldown period between consecutive exposures to the same entity. Prevents back-to-back ad delivery (e.g. {"interval": 60, "unit": "minutes"} for a 1-hour cooldown). Preferred over suppress_minutes.
+     */
+    suppress?: Duration;
+    /**
+     * Deprecated — use suppress instead. Cooldown period in minutes between consecutive exposures to the same entity (e.g. 60 for a 1-hour cooldown).
+     * @minimum 0
+     */
+    suppress_minutes?: number;
+    /**
+     * Maximum number of impressions per entity per window. For duration windows, implementations typically use a rolling window; 'campaign' applies a fixed cap across the full flight.
+     * @minimum 1
+     */
+    max_impressions?: number;
+    /**
+     * Entity granularity for impression counting. Required when max_impressions is set.
+     */
+    per?: ReachUnit;
+    /**
+     * Time window for the max_impressions cap (e.g. {"interval": 7, "unit": "days"} or {"interval": 1, "unit": "campaign"} for the full flight). Required when max_impressions is set.
+     */
+    window?: Duration;
+};
+
+/**
+ * Standardized advertising media channels describing how buyers allocate budget. Channels are planning abstractions, not technical substrates. See the Media Channel Taxonomy specification for detailed definitions.
+ */
+export type MediaChannel = 'display' | 'olv' | 'social' | 'search' | 'ctv' | 'linear_tv' | 'radio' | 'streaming_audio' | 'podcast' | 'dooh' | 'ooh' | 'print' | 'cinema' | 'email' | 'gaming' | 'retail_media' | 'influencer' | 'affiliate' | 'product_placement' | 'sponsored_intelligence';
+
+/**
+ * Outcome type.
+ */
+export type OutcomeType = 'completed' | 'failed' | 'delivery';
+
+/**
+ * The seller's interpreted delivery parameters. Describes what the seller will actually run -- geo, channels, flight dates, frequency caps, and budget. Present when the account has governance_agents or when the seller chooses to provide delivery transparency.
+ */
+export interface PlannedDelivery {
+    /**
+     * Geographic targeting the seller will apply.
+     */
+    geo?: {
+        /**
+         * ISO 3166-1 alpha-2 country codes where ads will deliver.
+         */
+        countries?: string[];
+        /**
+         * ISO 3166-2 subdivision codes where ads will deliver.
+         */
+        regions?: string[];
+    };
+    /**
+     * Channels the seller will deliver on.
+     */
+    channels?: MediaChannel[];
+    /**
+     * Actual flight start the seller will use.
+     * @format date-time
+     */
+    start_time?: string;
+    /**
+     * Actual flight end the seller will use.
+     * @format date-time
+     */
+    end_time?: string;
+    frequency_cap?: FrequencyCap;
+    /**
+     * Human-readable summary of the audience the seller will target.
+     */
+    audience_summary?: string;
+    /**
+     * Structured audience targeting the seller will activate. Each entry is either a signal reference or a descriptive criterion. When present, governance agents MUST use this for bias/fairness validation and SHOULD ignore audience_summary for validation purposes. The audience_summary field is a human-readable rendering of this array, not an independent declaration.
+     */
+    audience_targeting?: AudienceSelector[];
+    /**
+     * Total budget the seller will deliver against.
+     * @minimum 0
+     */
+    total_budget?: number;
+    /**
+     * ISO 4217 currency code for the budget.
+     * @pattern ^[A-Z]{3}$
+     */
+    currency?: string;
+    /**
+     * Registry policy IDs the seller will enforce for this delivery.
+     */
+    enforced_policies?: string[];
+    ext?: ExtensionObject;
+}
+
+/**
+ * The type of financial commitment this outcome is for. Determines which budget allocation (if any) to charge against. Defaults to 'media_buy' when omitted.
+ */
+export type PurchaseType = 'media_buy' | 'rights_license' | 'signal_activation' | 'creative_services';
+
+/**
+ * Unit of measurement for reach and audience_size metrics in this forecast. Required for cross-channel forecast comparison.
+ */
+export type ReachUnit = 'individuals' | 'households' | 'devices' | 'accounts' | 'cookies' | 'custom';
+
+/**
+ * The signal to target
+ */
+export type SignalID = {
+    /**
+     * Discriminator indicating this signal is from a data provider's published catalog
+     */
+    source: 'catalog';
+    /**
+     * Domain of the data provider that owns this signal (e.g., 'polk.com', 'experian.com'). The signal definition is published at this domain's /.well-known/adagents.json
+     * @pattern ^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)*$
+     */
+    data_provider_domain: string;
+    /**
+     * Signal identifier within the data provider's catalog (e.g., 'likely_tesla_buyers', 'income_100k_plus')
+     * @pattern ^[a-zA-Z0-9_-]+$
+     */
+    id: string;
+} | {
+    /**
+     * Discriminator indicating this signal is native to the agent (not from a data provider catalog)
+     */
+    source: 'agent';
+    /**
+     * URL of the signals agent that provides this signal (e.g., 'https://liveramp.com/.well-known/adcp/signals')
+     */
+    agent_url: string;
+    /**
+     * Signal identifier within the agent's signal set (e.g., 'custom_auto_intenders')
+     * @pattern ^[a-zA-Z0-9_-]+$
+     */
+    id: string;
+};