@kortexya/reasoninglayer 0.15.2 → 0.17.0

package/dist/index.cjs

@@ -1,7 +1,7 @@
 'use strict';
 
 // src/config.ts
-var SDK_VERSION = "0.15.2";
+var SDK_VERSION = "0.17.0";
 function resolveConfig(config) {
   if (!config.baseUrl) {
     throw new Error("ClientConfig.baseUrl is required");
@@ -4022,6 +4022,24 @@ var Causal = class {
     format: "json",
     ...params
   });
+  /**
+   * @description This endpoint validates whether a DiD design is theoretically sound given the known causal structure and unobserved confounding. It uses the Transformed SWIG (Delta-SWIG) framework from Knaus & Pfleiderer (2026).
+   *
+   * @tags causal
+   * @name ValidateDid
+   * @summary Validate a Difference-in-Differences (DiD) design
+   * @request POST:/api/v1/causal/validate-did
+   * @secure
+   */
+  validateDid = (data, params = {}) => this.http.request({
+    path: `/api/v1/causal/validate-did`,
+    method: "POST",
+    body: data,
+    secure: true,
+    type: "application/json" /* Json */,
+    format: "json",
+    ...params
+  });
 };
 
 // src/api-spec/generated/Reviews.ts
@@ -5093,6 +5111,42 @@ var Query = class {
     format: "json",
     ...params
   });
+  /**
+   * @description Skips the NL → structured-problem LLM hop entirely. Caller must have seeded the tenant KB with ≥ 3 successful + ≥ 2 limited Ψ-terms per domain (`/api/v1/terms/bulk` or `/api/v1/inference/facts/bulk`). Returns the same `NlQueryResponse` shape as the NL route so the UI can render either output uniformly.
+   *
+   * @tags query
+   * @name TrizInvent
+   * @summary Handle `POST /api/v1/triz/invent` — deterministic TRIZ invention.
+   * @request POST:/api/v1/triz/invent
+   * @secure
+   */
+  trizInvent = (data, params = {}) => this.http.request({
+    path: `/api/v1/triz/invent`,
+    method: "POST",
+    body: data,
+    secure: true,
+    type: "application/json" /* Json */,
+    format: "json",
+    ...params
+  });
+  /**
+   * No description
+   *
+   * @tags query
+   * @name TrizRecordOutcome
+   * @summary Handle `POST /api/v1/triz/record-outcome` — persist a measured outcome for a previously-emitted TRIZ proposal and learn from it.
+   * @request POST:/api/v1/triz/record-outcome
+   * @secure
+   */
+  trizRecordOutcome = (data, params = {}) => this.http.request({
+    path: `/api/v1/triz/record-outcome`,
+    method: "POST",
+    body: data,
+    secure: true,
+    type: "application/json" /* Json */,
+    format: "json",
+    ...params
+  });
   /**
    * @description This performs unification AND validates the result against the GLB sort's witnesses. ## How It Differs from Regular Unification **Regular `/api/v1/term-store/sessions/:id/unify` (POST)**: - Computes GLB and unifies terms - Validates sort constraints (required features, type hints) - Does NOT check witnesses **This endpoint `/api/v1/query/validated-unify` (POST)**: - Computes GLB and unifies terms - Validates sort constraints - ALSO checks witnesses on the result - Returns proof of validity ## Example Unifying `person(name => "Alice")` with `grandparent(grandchild => "Charlie")`: 1. Computes GLB of person and grandparent 2. Creates unified term with both features 3. Checks grandparent witnesses: ∃Y. parent(Alice,Y) ∧ parent(Y,Charlie) 4. Returns unified term + witness proof
    *
@@ -17038,7 +17092,7 @@ function FormalJudgeRequestFromFrontToApi(model) {
     final_output: model.finalOutput,
     execution_log: model.executionLog,
     config: model.config ? JudgeConfigDtoFromFrontToApi(model.config) : void 0,
-    use_osfkb_engine: model.useOsfkbEngine
+    risk_categories: model.riskCategories
   };
 }
 function LayerResultDtoFromApiToFront(dto) {