@pam-ai/pam-ordo-contracts 3.41.0 → 3.43.0

package/dist/generated.d.ts

@@ -1522,8 +1522,9 @@ export interface components {
             resolvedAt?: string | null;
             version: number;
             /**
-             * @description Inbound Customer Interactions on THIS WorkCycle with no outbound Interaction after them. Optional until every producer publishes it; absent means the count is unknown, not zero.
-             *     It answers a different question from `InteractionSummary`, which sits beside this object rather than inside it: that one is Conversation-wide and totals every Interaction ever exchanged, so it keeps climbing across cycles and never falls when someone replies. A row that says how much is waiting on the reader needs this one. `oldestUnrespondedAt` already names the same set's earliest member.
+             * @description Inbound Customer Interactions in this WorkCycle's pending round: those after the last human advisor reply on the cycle, meaning an outbound Interaction a User sent that is not an automatic message (DASH-379, 3.43.0). Pam's automatic replies and RO status texts do not end the round. Before 3.43.0 any outbound Interaction did. Optional until every producer publishes it; absent means the count is unknown, not zero.
+             *     It answers a different question from `InteractionSummary`, which sits beside this object rather than inside it: that one is Conversation-wide and totals every Interaction ever exchanged, so it keeps climbing across cycles and never falls when someone replies. A row that says how much is waiting on the reader needs this one.
+             *     NOT the set `oldestUnrespondedAt` measures. That clock drives Overdue and still treats Pam's automatic replies as a response, so after one the clock can be null while this count is still above zero. Never derive either from the other.
              */
             unrespondedInboundCount?: number;
             /** @description The Interactions counted by `unrespondedInboundCount`, split by kind, for the three kinds a Customer arrives by. Other inbound kinds are counted in the total but not here, so the three may sum to less than it; a consumer that needs the split to be complete must check the sum. Optional: absent means the producer does not publish it. Null when there is no WorkCycle to scope it to. */
@@ -1537,6 +1538,38 @@ export interface components {
              *     Optional and independently nullable: absent means the producer does not publish it, null means there is nothing waiting or the body is not available. Never reconstruct it from the count, and never treat its absence as an empty message.
              */
             latestUnrespondedInboundPreview?: string | null;
+            /** @description The pending round the counts above describe, as one window shared by row counts, labels, attachments and the AI summary (DASH-379). Optional: absent means the producer does not publish it. Null when the cycle is resolved or nothing is pending; a resolved cycle keeps its history, and its final preview is a separate concern. */
+            pendingRound?: components["schemas"]["PendingRoundV1"] | null;
+        };
+        /** @description Inbound arrivals on one WorkCycle since the last human advisor reply, computed from server state rather than from whatever part of the thread a reader has loaded. Out-of-order delivery is placed by occurrence time, so it lands in the round it belongs to and cannot restore an earlier round's state. */
+        PendingRoundV1: {
+            /**
+             * Format: date-time
+             * @description Occurrence time of the last human advisor reply on the cycle; the round holds arrivals strictly after it. Null when nobody has replied, so the round runs from the start of the cycle.
+             */
+            startsAfter: string | null;
+            /** @description Caller intents of the round's calls, each key once at its first occurrence. Ordered with every `intent` before every `transfer`, oldest first within each group. A consumer that shows fewer must keep this order. Deliberately uncapped and never truncated: a round holds any number of calls, so the list is bounded only by the distinct caller-intent keys, and a cut would silently drop the transfers that sort last. */
+            labels: components["schemas"]["PendingRoundLabelV1"][];
+            /** @description Calls in the round whose post-call analysis has not landed yet, so the labels may still grow. Zero when every call is analyzed. */
+            pendingAnalysis: number;
+        };
+        PendingRoundLabelV1: {
+            key: string;
+            /** @enum {string} */
+            kind: "intent" | "transfer";
+            /**
+             * Format: date-time
+             * @description Occurrence time of the earliest call in the round carrying this key.
+             */
+            firstSeenAt: string;
+            /**
+             * Format: uuid
+             * @description That earliest call, so a consumer can open the call this label came from.
+             */
+            sourceInteractionId: string;
+            requestedPersonName?: string | null;
+            requestedDepartment?: string | null;
+            serviceRequestInvoked?: boolean | null;
         };
         /** @description The three queue counts the Reporting page shows, with the same meaning as the matching InboxCounts fields for TEAM_INBOX in the same scope. */
         ReportingQueueCounts: {
@@ -1658,6 +1691,35 @@ export interface components {
          * @enum {string}
          */
         CallTerminalOutcomeV1: "answered" | "voicemail" | "missed" | "busy" | "no_answer";
+        /** @description One thing the caller wanted, as classified by post-call analysis (pam-postcall `caller_intent`, the source call logs and reporting already use). `key` is the CALLER_INTENT tag, such as SCHEDULE_SERVICE or SPEAK_TO_HUMAN_IN_PARTS; it is an open string because tags are configured outside this contract, so a consumer must render an unknown key gracefully rather than reject it. */
+        CallerIntentV1: {
+            key: string;
+            /**
+             * @description `transfer` when the caller asked for a person or department (the SPEAK_TO_* keys), otherwise `intent`. A call can carry both; consumers show intents before transfers.
+             * @enum {string}
+             */
+            kind: "intent" | "transfer";
+            /** @description The analysis' main reason for the call. At most one entry is primary. */
+            primary: boolean;
+            /** @description Who the caller asked for, on SPEAK_TO_SPECIFIC_HUMAN. Null or absent when the analysis did not name anyone. */
+            requestedPersonName?: string | null;
+            /** @description The department the caller asked for, on a SPEAK_TO_HUMAN_IN_* transfer. */
+            requestedDepartment?: string | null;
+            /** @description Only on SCHEDULE_SERVICE. True when Pam actually called the service-request tool on this call, false when the analysis observed the call's tools and it did not, null when tool calls were not observed. Never derived from `fulfillment`, which is rewritten to service_appointment_request for rooftops without a service integration. */
+            serviceRequestInvoked?: boolean | null;
+        };
+        /** @description The caller intents recorded for one call. `pending` means post-call analysis has not reported yet, which is different from an analyzed call whose only intent is UNCLEAR_INTENT. A pending entry may carry the call summary's primary intent as a provisional item so a reader is not left blank in the seconds before analysis lands. */
+        CallerIntentsV1: {
+            /** @enum {string} */
+            analysis: "pending" | "analyzed";
+            /**
+             * Format: date-time
+             * @description When the analysis that produced `items` ran. Null while pending.
+             */
+            analyzedAt?: string | null;
+            /** @description Producer order with the primary entry first. */
+            items: components["schemas"]["CallerIntentV1"][];
+        };
         InteractionRef: {
             /** Format: uuid */
             id: string;
@@ -1688,6 +1750,8 @@ export interface components {
              *     Null for Interactions Ordo itself authored — an internal comment has no external record to point at — and for any source that has not recorded one. Distinct from `sourceLocator`, which is a native partition/sort key and is published only when the source addresses records that way; a source can have one, both, or neither.
              */
             sourceRecordId?: string | null;
+            /** @description What the caller wanted on this call, one entry per intent or transfer request (DASH-378). Present only on an inbound `call` or `voicemail`; absent or null on every other Interaction. Optional so this addition is a minor version. */
+            callerIntents?: components["schemas"]["CallerIntentsV1"] | null;
             /**
              * @description Present only on an Interaction of kind `ro_event`. Before this field a repair-order Interaction arrived with kind `ro_event`, a null body and nothing else, so a reader could tell that SOMETHING had happened to a repair order but neither which one nor whether it had opened or closed.
              *     NULL IS POSSIBLE ON AN ro_event, and 3.14.0 wrongly said it was not. There are two reasons for it, and only one of them is historical.
@@ -2209,6 +2273,14 @@ export interface components {
             /** @description Optional same-call current-source assessment. It is omitted when the model abstains; consumers must not derive fresh Attention from cumulative snapshot categories. */
             assessment?: components["schemas"]["ConversationAiAssessmentV1"];
         };
+        /** @description The complete set of caller intents one post-call analysis produced for one call. The consumer replaces the call's previous set when `analyzedAt` is later than the stored one and ignores an equal or earlier analysis, so redelivery and out-of-order delivery cannot restore a stale set. */
+        ProducerCallerIntentsObservedPayloadV1: {
+            /** @description The call, as Ordo already knows it: `pam_call_metadata` and the connection id. The call may not have reached Ordo yet; the consumer keeps the intents until it does. */
+            sourceInteraction: components["schemas"]["ProducerSourceInteractionIdentityV1"];
+            /** Format: date-time */
+            analyzedAt: string;
+            intents: components["schemas"]["CallerIntentV1"][];
+        };
         ProducerReminderFirePayloadV1: {
             /** Format: uuid */
             reminderId: string;
@@ -2296,6 +2368,27 @@ export interface components {
             target: components["schemas"]["ProducerSourceActivityTargetV1"];
             payload: components["schemas"]["ProducerAttentionCategoryObservedPayloadV1"];
         };
+        /** @description Reports the caller intents post-call analysis recorded for one call (DASH-378). Unlike other producer commands it has no target: the producer knows the call, not its Conversation or Customer, and the call's own identity is enough for the consumer to find it. occurredAt is the call's business time. It uses its own FIFO message group per call, so it never delays the call's Conversation. */
+        ProducerCallerIntentsObservedCommandV1: {
+            /** @constant */
+            schemaVersion: 1;
+            operationId: string;
+            /**
+             * @description discriminator enum property added by openapi-typescript
+             * @enum {string}
+             */
+            commandType: "interaction.caller_intents_observed";
+            clientOrgId: string;
+            traceId: string;
+            /** Format: date-time */
+            occurredAt: string;
+            actor: {
+                /** @constant */
+                type: "source";
+            };
+            source: components["schemas"]["ProducerSourceV1"];
+            payload: components["schemas"]["ProducerCallerIntentsObservedPayloadV1"];
+        };
         ProducerReminderFireCommandV1: {
             /** @constant */
             schemaVersion: 1;
@@ -2360,7 +2453,7 @@ export interface components {
             payload: components["schemas"]["ProducerOverdueFirePayloadV1"];
         };
         /** @description Versioned internal FIFO producer command. Serialized SQS bodies are limited to 64 KiB by producers and consumers even though JSON Schema cannot express a byte-size limit. */
-        ProducerCommandV1: components["schemas"]["ProducerSourceActivityCommandV1"] | components["schemas"]["ProducerAttentionCommandV1"] | components["schemas"]["ProducerAttentionCategoryObservedCommandV1"] | components["schemas"]["ProducerReminderFireCommandV1"] | components["schemas"]["ProducerSnoozeReturnCommandV1"] | components["schemas"]["ProducerOverdueFireCommandV1"];
+        ProducerCommandV1: components["schemas"]["ProducerSourceActivityCommandV1"] | components["schemas"]["ProducerAttentionCommandV1"] | components["schemas"]["ProducerAttentionCategoryObservedCommandV1"] | components["schemas"]["ProducerCallerIntentsObservedCommandV1"] | components["schemas"]["ProducerReminderFireCommandV1"] | components["schemas"]["ProducerSnoozeReturnCommandV1"] | components["schemas"]["ProducerOverdueFireCommandV1"];
         CommandEnvelope: {
             operationId: string;
             clientOrgId: string;