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

package/dist/lib/types/check-governance.d.ts

@@ -0,0 +1,619 @@
+// AUTO-GENERATED — DO NOT EDIT.
+// Per-tool .d.ts slice for `check_governance`. 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.
+
+/**
+ * Universal governance check for campaign actions. The governance agent infers the check type from the fields present: tool+payload = intent check (proposed, orchestrator-side). planned_delivery = execution check (committed, seller-side). governance_context maintains lifecycle continuity across either check type — its presence alone does not determine binding. To check budget availability without a specific action, omit tool and payload.
+ */
+export interface CheckGovernanceRequest {
+    /**
+     * 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;
+    /**
+     * Campaign governance plan identifier. The plan uniquely scopes the account and operator; do not include a separate `account` field — the governance agent resolves account from the plan. Governance agents MUST treat any sibling `account` field as a contract violation and reject the request.
+     */
+    plan_id: string;
+    /**
+     * URL of the agent making the request.
+     */
+    caller: string;
+    purchase_type?: PurchaseType;
+    /**
+     * The AdCP tool being checked (e.g., 'create_media_buy', 'acquire_rights', 'activate_signal'). Present on intent checks (orchestrator). The governance agent uses the presence of tool+payload to identify an intent check.
+     */
+    tool?: string;
+    /**
+     * The full tool arguments as they would be sent to the seller. Present on intent checks. The governance agent can inspect any field to validate against the plan.
+     */
+    payload?: {};
+    /**
+     * Governance context token from a prior check_governance response. Pass this on subsequent checks for the same governed action so the governance agent can maintain continuity across the lifecycle. In 3.0 governance agents MUST emit a compact JWS per the AdCP JWS profile (see Security — Signed Governance Context); callers persist and forward the value verbatim.
+     * @minLength 1
+     * @maxLength 4096
+     * @pattern ^[\x20-\x7E]+$
+     */
+    governance_context?: string;
+    phase?: GovernancePhase;
+    planned_delivery?: PlannedDelivery;
+    /**
+     * Actual delivery performance data. MUST be present for 'delivery' phase. The governance agent compares these metrics against the planned delivery to detect drift.
+     */
+    delivery_metrics?: {
+        /**
+         * Start and end timestamps for the reporting window.
+         */
+        reporting_period: {
+            /**
+             * @format date-time
+             */
+            start: string;
+            /**
+             * @format date-time
+             */
+            end: string;
+        };
+        /**
+         * Total spend during the reporting period.
+         * @minimum 0
+         */
+        spend?: number;
+        /**
+         * Total spend since the governed action started.
+         * @minimum 0
+         */
+        cumulative_spend?: number;
+        /**
+         * Impressions delivered during the reporting period.
+         * @minimum 0
+         */
+        impressions?: number;
+        /**
+         * Total impressions since the governed action started.
+         * @minimum 0
+         */
+        cumulative_impressions?: number;
+        /**
+         * Actual geographic distribution. Keys are ISO 3166-1 alpha-2 codes, values are percentages.
+         */
+        geo_distribution?: {
+            /**
+             * @minimum 0
+             * @maximum 100
+             */
+            [k: string]: number | undefined;
+        };
+        /**
+         * Actual channel distribution. Keys are channel enum values, values are percentages.
+         */
+        channel_distribution?: {
+            /**
+             * @minimum 0
+             * @maximum 100
+             */
+            [k: string]: number | undefined;
+        };
+        /**
+         * Whether delivery is ahead of, on track with, or behind the planned pace.
+         */
+        pacing?: 'ahead' | 'on_track' | 'behind';
+        /**
+         * Actual audience composition during the reporting period. Enables mid-flight drift detection when actual delivery skews from planned audience targeting.
+         */
+        audience_distribution?: {
+            /**
+             * Population baseline used for index calculation. 'census': national census or equivalent population data. 'platform': the seller's active user base. 'custom': a custom baseline defined by the seller (describe in baseline_description).
+             */
+            baseline: 'census' | 'platform' | 'custom';
+            /**
+             * Description of the baseline when baseline is 'custom' (e.g., 'US adults 18+ with broadband access').
+             */
+            baseline_description?: string;
+            /**
+             * Audience index values for the current reporting period. Keys are seller-defined dimension:value strings (e.g., 'age:25-34', 'gender:female', 'income:high'). The protocol does not mandate a taxonomy — dimensions and value labels vary by seller. Values are index relative to the declared baseline (1.0 = at parity, >1.0 = over-indexed, <1.0 = under-indexed).
+             */
+            indices: {
+                /**
+                 * @minimum 0
+                 */
+                [k: string]: number | undefined;
+            };
+            /**
+             * Cumulative audience index values since the governed action started. Same key format as indices (dimension:value). Use for detecting sustained bias drift that may not appear in a single reporting period.
+             */
+            cumulative_indices?: {
+                /**
+                 * @minimum 0
+                 */
+                [k: string]: number | undefined;
+            };
+        };
+    };
+    /**
+     * Human-readable summary of what changed. SHOULD be present for 'modification' phase.
+     * @maxLength 1000
+     */
+    modification_summary?: string;
+    invoice_recipient?: BusinessEntity;
+    context?: ContextObject;
+    ext?: ExtensionObject;
+}
+
+/**
+ * Governance agent's response to a check request. Returns whether the action is approved under the governance plan.
+ */
+export interface CheckGovernanceResponse {
+    /**
+     * 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 governance check record. Use in report_plan_outcome to link outcomes to the check that authorized them.
+     */
+    check_id: string;
+    verdict: GovernanceDecision;
+    /**
+     * Echoed from request.
+     */
+    plan_id: string;
+    /**
+     * Human-readable explanation of the governance decision.
+     */
+    explanation: string;
+    /**
+     * Specific issues found during the governance check. Present when verdict is 'denied' or 'conditions'. MAY also be present on 'approved' for informational findings (e.g., budget approaching limit).
+     */
+    findings?: {
+        /**
+         * Validation category that flagged the issue (e.g., 'budget_compliance', 'regulatory_compliance', 'brand_safety'). This is an **agent-internal** taxonomy: the string is defined by the governance agent's own policy model and is not constrained to any protocol-level enum. Sellers and buyers MUST NOT pattern-match `category_id` values against a fixed list — treat them as opaque labels with human-readable significance for audit but no machine-level contract. See the Campaign Governance specification for how an agent composes internal specialist review behind one endpoint.
+         */
+        category_id: string;
+        /**
+         * ID of the policy that triggered this finding. May reference a registry policy (with source: registry) or a bespoke inline policy (with source: inline). Bespoke policy_ids are unique within their authoring container; use source_plan_id when findings aggregate across multiple plans (e.g., portfolio evaluations). When the violation traces to a producer-tagged surface (feature-requirement, creative-feature-result, or validation-result feature) carrying policy_id, governance agents SHOULD echo that policy_id here for end-to-end traceability, and MUST NOT invent a policy_id that wasn't present on the originating surface. See /docs/governance/policy-attribution.
+         */
+        policy_id?: string;
+        /**
+         * For portfolio or aggregated evaluations where findings draw on bespoke policies from multiple member plans: identifies the plan whose policy triggered this finding. Omit when the finding's policy_id is unambiguous within the response context (e.g., single-plan check_governance).
+         */
+        source_plan_id?: string;
+        severity: EscalationSeverity;
+        /**
+         * Human-readable description of the issue.
+         */
+        explanation: string;
+        /**
+         * Structured details for programmatic consumption.
+         */
+        details?: {};
+        /**
+         * Confidence score (0-1) in this finding. Distinguishes 'this definitely violates the policy' (0.95) from 'this might violate depending on how audience segments resolve' (0.6). When absent, the finding is presented without a confidence qualifier.
+         * @minimum 0
+         * @maximum 1
+         */
+        confidence?: number;
+        /**
+         * Explanation of why confidence is below 1.0 (e.g., 'Targeting includes regions that partially overlap jurisdiction boundaries'). Present when confidence is below a governance-agent-defined threshold.
+         */
+        uncertainty_reason?: string;
+    }[];
+    /**
+     * Present when verdict is 'conditions'. Specific adjustments the caller must make. After applying conditions, the caller MUST re-call check_governance with the adjusted parameters before proceeding.
+     */
+    conditions?: {
+        /**
+         * Dot-path to the field that needs adjustment (in payload for proposed, in planned_delivery for committed).
+         */
+        field: string;
+        /**
+         * The value the field must have for approval. When present, the condition is machine-actionable. When absent, the condition is advisory.
+         */
+        required_value?: unknown;
+        /**
+         * Why this condition is required.
+         */
+        reason: string;
+    }[];
+    /**
+     * When this approval expires. Present when verdict is 'approved' or 'conditions'. The caller must act before this time or re-call check_governance. A lapsed approval is no approval.
+     * @format date-time
+     */
+    expires_at?: string;
+    /**
+     * When the seller should next call check_governance with delivery metrics. Present when the governance agent expects ongoing delivery reporting.
+     * @format date-time
+     */
+    next_check?: string;
+    /**
+     * Governance categories evaluated during this check. Each value is an **agent-internal** label (e.g., `budget_authority`, `regulatory_compliance`, or any internal-reviewer key the agent's policy model defines) — not a protocol-level enum. Since one governance agent per account composes all specialist review behind its single endpoint, `categories_evaluated` is how that internal decomposition surfaces to auditors. Consumers MUST treat values as opaque labels for display and audit, not as a machine-level contract.
+     */
+    categories_evaluated?: string[];
+    /**
+     * Policy IDs evaluated during this check. Includes registry policy IDs (resolved via the policy registry) and any inline `policy_id`s declared in the plan's `custom_policies`.
+     */
+    policies_evaluated?: string[];
+    mode?: GovernanceMode;
+    /**
+     * Governance context token for this governed action. The buyer MUST attach this to the protocol envelope when sending the purchase request (media buy, rights acquisition, signal activation) to the seller. The seller MUST persist it and include it on all subsequent check_governance calls for this action's lifecycle.
+     *
+     * Value format: in 3.0 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 so auditors can verify downstream. In 3.1 all sellers MUST verify per the checklist. Non-JWS values from pre-3.0 governance agents are deprecated and will be rejected in 3.1.
+     *
+     * Sellers that implement verification MUST verify signature, `aud`, `exp`, `jti` replay, and revocation per the profile before treating the request as governance-approved. This is the primary correlation key for audit and reporting across the governance lifecycle — the governance agent decodes its own signed token to look up internal plan state (buyer correlation IDs, policy decision log, etc.).
+     * @minLength 1
+     * @maxLength 4096
+     * @pattern ^[\x20-\x7E]+$
+     */
+    governance_context?: string;
+    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;
+};
+
+/**
+ * Override the account's default billing entity for this specific buy. When provided, the seller invoices this entity instead. The seller MUST validate the invoice recipient is authorized for this account. When governance_agents are configured, the seller MUST include invoice_recipient in the check_governance request.
+ */
+export interface BusinessEntity {
+    /**
+     * Registered legal name of the business entity
+     * @maxLength 200
+     */
+    legal_name: string;
+    /**
+     * VAT identification number (e.g., DE123456789 for Germany, FR12345678901 for France). Required for B2B invoicing in the EU. Must be normalized: no spaces, dots, or dashes.
+     * @pattern ^[A-Z]{2}[A-Z0-9]{2,13}$
+     */
+    vat_id?: string;
+    /**
+     * Tax identification number for jurisdictions that do not use VAT (e.g., US EIN)
+     * @maxLength 30
+     */
+    tax_id?: string;
+    /**
+     * Company registration number (e.g., HRB 12345 for German Handelsregister)
+     * @maxLength 50
+     */
+    registration_number?: string;
+    /**
+     * Postal address for invoicing and legal correspondence
+     */
+    address?: {
+        /**
+         * Street address including building number
+         * @maxLength 200
+         */
+        street: string;
+        /**
+         * @maxLength 100
+         */
+        city: string;
+        /**
+         * @maxLength 20
+         */
+        postal_code: string;
+        /**
+         * State, province, or region
+         * @maxLength 100
+         */
+        region?: string;
+        /**
+         * ISO 3166-1 alpha-2 country code
+         * @pattern ^[A-Z]{2}$
+         */
+        country: string;
+    };
+    /**
+     * Contacts for billing, legal, and operational matters. Contains personal data subject to GDPR and equivalent regulations. Implementations MUST use this data only for invoicing and account management.
+     */
+    contacts?: {
+        /**
+         * Contact's functional role in the business relationship
+         */
+        role: 'billing' | 'legal' | 'creative' | 'general';
+        /**
+         * Full name of the contact
+         * @maxLength 200
+         */
+        name?: string;
+        /**
+         * @maxLength 254
+         * @format email
+         */
+        email?: string;
+        /**
+         * @maxLength 30
+         */
+        phone?: string;
+    }[];
+    /**
+     * Bank account details for payment processing. Write-only: included in requests to provide payment coordinates, but MUST NOT be echoed in responses. Sellers store these details and confirm receipt without returning them.
+     */
+    bank?: {
+        /**
+         * Name on the bank account
+         * @maxLength 200
+         */
+        account_holder: string;
+        /**
+         * International Bank Account Number (SEPA markets)
+         * @pattern ^[A-Z]{2}[0-9]{2}[A-Z0-9]{4,30}$
+         */
+        iban?: string;
+        /**
+         * Bank Identifier Code / SWIFT code (SEPA markets)
+         * @pattern ^[A-Z]{4}[A-Z]{2}[A-Z0-9]{2}([A-Z0-9]{3})?$
+         */
+        bic?: string;
+        /**
+         * Bank routing number for non-SEPA markets (e.g., US ABA routing number, Canadian transit/institution number)
+         * @maxLength 30
+         */
+        routing_number?: string;
+        /**
+         * Bank account number for non-SEPA markets
+         * @maxLength 30
+         */
+        account_number?: string;
+    };
+    ext?: ExtensionObject;
+}
+
+/**
+ * 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;
+};
+
+/**
+ * Governance verdict (present for check entries). Renamed from `status` in 3.1 alongside check-governance-response for vocabulary consistency.
+ */
+export type GovernanceDecision = 'approved' | 'denied' | 'conditions';
+
+/**
+ * Governance mode active at the moment this specific check was evaluated. Governance agents SHOULD populate this field on check entries, recording the mode from their runtime configuration at the moment check_governance was processed — not derived from a plan field. This is a per-check value: if the operator changes mode between checks for the same governed action, each entry records the mode active for that entry. A future `governed_actions[].mode` field would describe the action's current mode, which may differ from the most recent entry's `mode` if the plan has since been re-synced. Absent for outcome entries and for pre-3.1 governance agents that do not surface mode on audit responses.
+ */
+export type GovernanceMode = 'audit' | 'advisory' | 'enforce';
+
+/**
+ * The phase of the governed action's lifecycle. 'purchase': initial commitment (create_media_buy, acquire_rights, activate_signal). 'modification': update to existing commitment. 'delivery': periodic delivery or usage reporting. Defaults to 'purchase' if omitted.
+ */
+export type GovernancePhase = 'purchase' | 'modification' | 'delivery';
+
+/**
+ * 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';
+
+/**
+ * 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;
+};