@aiqa/sdk 3.1.0 → 3.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -363,6 +363,21 @@ a timeout, a rejected payload.
363
363
  answer_format: { type: "STRING" }
364
364
  /** Optional (default: `false`). Use `true` when the fact was collected before the conversation started. It is stored, not verified. */
365
365
  prefilled?: boolean
366
+ /**
367
+ * Optional. Use `true` for a value you already know is correct, such as data
368
+ * from your own records. Unlike `prefilled`, it is about trusting the value, not
369
+ * when it was collected. It is stored and visible to whoever reviews the call,
370
+ * never verified, and left out of the verification summary counts.
371
+ */
372
+ reference?: boolean
373
+ /**
374
+ * Optional. Use "watch" to check the fact over the whole call instead of
375
+ * at one moment, about every 15 seconds. addFact() then resolves right
376
+ * away with verification_status: "awaiting_question", and the result
377
+ * (matched or unmatched) arrives later on FACT_VERIFIED, at the latest
378
+ * when the call ends.
379
+ */
380
+ evaluation?: "watch"
366
381
  /**
367
382
  * Optional. Your own identifiers for this fact — a form field ID, a
368
383
  * section name, anything that lets your UI map the result back to the
@@ -579,6 +594,12 @@ Rules:
579
594
  - **Handle a `verification_status` you don't recognize as `processing`.**
580
595
  - **A fact sent with `prefilled: true` is never verified**, so it gets no
581
596
  `verification_status` and no `FACT_VERIFIED` event.
597
+ - **A fact sent with `reference: true` is never verified either.** Use it for
598
+ a value you already know is correct, such as the plan name from your own
599
+ records. It is stored, visible to whoever reviews the call, and left out of
600
+ the verification summary counts. `addFact()` still resolves, with
601
+ `is_valid_answer: false` and no `verification_status`, and no `FACT_VERIFIED`
602
+ event is emitted for it.
582
603
  - **`pending_confirmation_*` is never final.** The answer can still change,
583
604
  so don't show it as a decision.
584
605
  - **A fact can be revised after `addFact()` has resolved.** If you keep its
@@ -829,6 +850,21 @@ type ApplicationFactInput = {
829
850
  is_skipped?: boolean;
830
851
  /** Optional (default: `false`). Use `true` when the fact was collected before the conversation started. It is stored, not verified. */
831
852
  prefilled?: boolean;
853
+ /**
854
+ * Optional. Use `true` for a value you already know is correct, such as data
855
+ * from your own records. Unlike `prefilled`, it is about trusting the value, not
856
+ * when it was collected. It is stored and visible to whoever reviews the call,
857
+ * never verified, and left out of the verification summary counts.
858
+ */
859
+ reference?: boolean;
860
+ /**
861
+ * Optional. Use `"watch"` to check the fact over the whole call instead of
862
+ * at one moment, about every 15 seconds. `addFact()` then resolves right
863
+ * away with `verification_status: "awaiting_question"`, and the result
864
+ * (`matched` or `unmatched`) arrives later on `FACT_VERIFIED`, at the latest
865
+ * when the call ends.
866
+ */
867
+ evaluation?: "watch";
832
868
  /**
833
869
  * Optional. Your own identifiers for this fact — a form field ID, a section
834
870
  * name, anything that lets your UI map the result back to the right place.
@@ -208,6 +208,21 @@ type ApplicationFactInput = {
208
208
  is_skipped?: boolean;
209
209
  /** Optional (default: `false`). Use `true` when the fact was collected before the conversation started. It is stored, not verified. */
210
210
  prefilled?: boolean;
211
+ /**
212
+ * Optional. Use `true` for a value you already know is correct, such as data
213
+ * from your own records. Unlike `prefilled`, it is about trusting the value, not
214
+ * when it was collected. It is stored and visible to whoever reviews the call,
215
+ * never verified, and left out of the verification summary counts.
216
+ */
217
+ reference?: boolean;
218
+ /**
219
+ * Optional. Use `"watch"` to check the fact over the whole call instead of
220
+ * at one moment, about every 15 seconds. `addFact()` then resolves right
221
+ * away with `verification_status: "awaiting_question"`, and the result
222
+ * (`matched` or `unmatched`) arrives later on `FACT_VERIFIED`, at the latest
223
+ * when the call ends.
224
+ */
225
+ evaluation?: "watch";
211
226
  /**
212
227
  * Your own identifiers for this fact — a form field ID, a section name,
213
228
  * anything that lets your UI map the result back to the right place.
@@ -266,7 +281,7 @@ interface AddFactResult {
266
281
  answer_type?: string;
267
282
  agent_answer?: string;
268
283
  ai_answer?: string;
269
- /** `false` for a fact that was never verified, such as a prefilled one. */
284
+ /** `false` for a fact that was never verified, such as a prefilled or reference one. */
270
285
  is_valid_answer: boolean;
271
286
  question_asked?: boolean;
272
287
  /**
@@ -3407,7 +3407,7 @@ var compareVersions = (left, right) => {
3407
3407
  // package.json
3408
3408
  var package_default = {
3409
3409
  name: "@aiqa/sdk",
3410
- version: "3.0.0-develop.2",
3410
+ version: "3.1.0-develop.3",
3411
3411
  main: "dist/node/node.js",
3412
3412
  module: "dist/node/node.js",
3413
3413
  types: "dist/node/node.d.ts",