@kortexya/reasoninglayer 0.15.1 → 0.16.0

package/dist/index.d.cts

@@ -109,7 +109,7 @@ type JsonValue$1 = string | number | boolean | null | JsonValue$1[] | object;
  * This is the single source of truth for the version constant.
  * The `scripts/release.sh` script updates this value alongside `package.json`.
  */
-declare const SDK_VERSION = "0.15.1";
+declare const SDK_VERSION = "0.16.0";
 /**
  * Configuration for the Reasoning Layer client.
  *
@@ -3898,6 +3898,28 @@ interface DetectMissingAttributesRequest$1 {
     call_attributes: string[];
     definition_attributes: string[];
 }
+/** Request to validate a Difference-in-Differences design */
+interface DiDValidationRequest {
+    /** Conditioning set (covariates) */
+    covariates?: string[];
+    /** Post-treatment outcome variable */
+    outcome_post: string;
+    /** Pre-treatment outcome variable */
+    outcome_pre: string;
+    /** The treatment variable */
+    treatment: string;
+}
+/** Response for DiD validation */
+interface DiDValidationResponse {
+    /** Identified "bad controls" (nodes that induce bias if conditioned on) */
+    bad_controls: string[];
+    /** Explanation of the result */
+    explanation: string;
+    /** The framework used for validation */
+    framework: string;
+    /** Whether the design is valid */
+    is_valid: boolean;
+}
 /** A pipeline diagnostic message. */
 interface DiagnosticDto$1 {
     /** Severity level: "info", "warning", or "error". */
@@ -6086,6 +6108,8 @@ type FeatureConstraintDto = {
 };
 /** API representation of a feature descriptor */
 interface FeatureDescriptorDto$1 {
+    /** Custom OWL annotations for this feature (e.g., isIdentifier, unit, enumValues) */
+    annotations?: Record<string, string>;
     /** Optional constraint on the feature value */
     constraint?: null | ConstraintDto$1;
     /**
@@ -6385,12 +6409,6 @@ interface FormalJudgeRequest$1 {
      * Paper Table 5: `trajectory.tool_calls`
      */
     trajectory: TrajectoryStepDto$1[];
-    /**
-     * Use the OSFKB-native safety engine instead of the LLM-based adapter.
-     * When true, uses sort hierarchy + neural sort grounding + homoiconic rules.
-     * When false (default), uses the LLM-based OversightExtractionAdapter.
-     */
-    use_osfkb_engine?: boolean;
     /** User instruction (what the agent was asked to do) */
     user_intent: string;
 }
@@ -14199,6 +14217,8 @@ interface SortDiscoveryResponseDto {
 }
 /** API representation of a sort with full OSF schema */
 interface SortDto$1 {
+    /** Custom OWL annotations (e.g., icon, color) */
+    annotations?: Record<string, string>;
     /** Bound constraints on feature values */
     bound_constraints?: BoundConstraintDto$1[];
     /** Human-readable description for semantic search */
@@ -14430,6 +14450,16 @@ type SpaceConstraintDto$1 = {
     total: number;
     type: "sum_equal";
     variables: string[];
+} | {
+    a: string[];
+    b: string[];
+    type: "lex_leq";
+} | {
+    groups: string[][];
+    type: "symmetry_group";
+} | {
+    entities: string[][];
+    type: "symmetric_observation";
 } | {
     lower: number[];
     type: "set_domain";
@@ -16164,20 +16194,35 @@ type ValuePatternDto$1 = {
 /**
  * Feasibility of a single binary variable in the constraint space.
  *
- * Produced by `feasibility` mode search.  Both fields can be `false` only
- * when the problem is UNSAT (no valid assignment exists).
+ * Produced by `feasibility` mode search.  Fields report **observation-based**
+ * reachability: the solver sets `can_be_true` only when it has witnessed a
+ * complete satisfying assignment with this variable = 1 (and similarly for
+ * `can_be_false`).  Both fields can be `false` only when the problem is UNSAT.
  */
 interface VariableFeasibilityDto$1 {
     /**
-     * `true` if there exists at least one valid assignment where this variable
+     * `true` if the solver witnessed a valid assignment where this variable
      * is 0 (unselected / false).
      */
     can_be_false: boolean;
     /**
-     * `true` if there exists at least one valid assignment where this variable
+     * `true` if the solver witnessed a valid assignment where this variable
      * is 1 (selected / true).
      */
     can_be_true: boolean;
+    /**
+     * `true` when the result is fully determined by the solver — both
+     * polarities were either observed in a model or formally proven
+     * infeasible (by unit propagation or an UNSAT probe).
+     *
+     * `false` when a conflict limit was hit before the solver could fully
+     * determine the variable's status.  In that case `can_be_true` /
+     * `can_be_false` still faithfully reflect the polarities the solver
+     * actually witnessed — they are **never** optimistic defaults.  Clients
+     * typically render unverified variables in an intermediate visual state
+     * (e.g. yellow/amber) so the user knows the result is approximate.
+     */
+    verified?: boolean;
 }
 /** Result of verbalizing a single PsiTerm. */
 interface VerbalizationResultDto$1 {
@@ -25921,6 +25966,16 @@ declare class Causal<SecurityDataType = unknown> {
      * @secure
      */
     getCausalModel: (params?: RequestParams) => Promise<HttpResponse<GetCausalModelResponse$1, any>>;
+    /**
+     * @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: DiDValidationRequest, params?: RequestParams) => Promise<HttpResponse<DiDValidationResponse, void>>;
 }
 
 /**
@@ -30876,14 +30931,31 @@ type SearchModeDto = 'solutions' | 'feasibility';
  *
  * @remarks
  * Produced by `mode = "feasibility"` search.
- * - `canBeTrue = true` means at least one valid assignment sets this variable to 1.
+ * - `canBeTrue = true` means the solver actually observed a valid assignment
+ *   with this variable = 1 (a witnessed model).
+ * - `canBeFalse = true` means the solver observed a valid assignment with
+ *   this variable = 0.
  * - `canBeTrue = false && canBeFalse = false` means the problem is UNSAT.
+ *
+ * When the underlying solver hits a conflict/time budget before the opposite
+ * polarity could be proven (im)feasible, `verified` is `false` and the
+ * reachability fields reflect only the polarities that were actually
+ * witnessed.  For example, `(canBeTrue: true, canBeFalse: false,
+ * verified: false)` means "observed in every model found so far, never
+ * observed as 0 — likely required, but the solver did not complete the
+ * UNSAT-for-0 probe to certify it."
  */
 interface VariableFeasibilityDto {
-    /** True if at least one valid assignment sets this variable to 1 (selected). */
+    /** True if the solver witnessed a valid assignment where this variable is 1. */
     canBeTrue: boolean;
-    /** True if at least one valid assignment sets this variable to 0 (unselected). */
+    /** True if the solver witnessed a valid assignment where this variable is 0. */
     canBeFalse: boolean;
+    /**
+     * True when the reachability result is fully determined by the solver
+     * (both polarities resolved).  False when a conflict/time limit was hit
+     * and the result reflects only the polarities that were observed.
+     */
+    verified: boolean;
 }
 /**
  * Request to search for solutions.
@@ -33751,8 +33823,13 @@ interface FormalJudgeRequest {
     executionLog?: string;
     /** Optional pipeline configuration overrides. */
     config?: JudgeConfigDto | null;
-    /** Use OSFKB engine for verification (default: false). */
-    useOsfkbEngine?: boolean;
+    /**
+     * Risk categories from the benchmark dataset (e.g.,
+     * `["Lead to property loss", "Violate laws"]`).  Used by the
+     * 3-agent per-task decomposition pipeline to generate
+     * task-specific atomic conditions.
+     */
+    riskCategories?: string[];
 }
 /** Per-layer verification result. */
 interface LayerResultDto {

package/dist/index.d.ts

@@ -109,7 +109,7 @@ type JsonValue$1 = string | number | boolean | null | JsonValue$1[] | object;
  * This is the single source of truth for the version constant.
  * The `scripts/release.sh` script updates this value alongside `package.json`.
  */
-declare const SDK_VERSION = "0.15.1";
+declare const SDK_VERSION = "0.16.0";
 /**
  * Configuration for the Reasoning Layer client.
  *
@@ -3898,6 +3898,28 @@ interface DetectMissingAttributesRequest$1 {
     call_attributes: string[];
     definition_attributes: string[];
 }
+/** Request to validate a Difference-in-Differences design */
+interface DiDValidationRequest {
+    /** Conditioning set (covariates) */
+    covariates?: string[];
+    /** Post-treatment outcome variable */
+    outcome_post: string;
+    /** Pre-treatment outcome variable */
+    outcome_pre: string;
+    /** The treatment variable */
+    treatment: string;
+}
+/** Response for DiD validation */
+interface DiDValidationResponse {
+    /** Identified "bad controls" (nodes that induce bias if conditioned on) */
+    bad_controls: string[];
+    /** Explanation of the result */
+    explanation: string;
+    /** The framework used for validation */
+    framework: string;
+    /** Whether the design is valid */
+    is_valid: boolean;
+}
 /** A pipeline diagnostic message. */
 interface DiagnosticDto$1 {
     /** Severity level: "info", "warning", or "error". */
@@ -6086,6 +6108,8 @@ type FeatureConstraintDto = {
 };
 /** API representation of a feature descriptor */
 interface FeatureDescriptorDto$1 {
+    /** Custom OWL annotations for this feature (e.g., isIdentifier, unit, enumValues) */
+    annotations?: Record<string, string>;
     /** Optional constraint on the feature value */
     constraint?: null | ConstraintDto$1;
     /**
@@ -6385,12 +6409,6 @@ interface FormalJudgeRequest$1 {
      * Paper Table 5: `trajectory.tool_calls`
      */
     trajectory: TrajectoryStepDto$1[];
-    /**
-     * Use the OSFKB-native safety engine instead of the LLM-based adapter.
-     * When true, uses sort hierarchy + neural sort grounding + homoiconic rules.
-     * When false (default), uses the LLM-based OversightExtractionAdapter.
-     */
-    use_osfkb_engine?: boolean;
     /** User instruction (what the agent was asked to do) */
     user_intent: string;
 }
@@ -14199,6 +14217,8 @@ interface SortDiscoveryResponseDto {
 }
 /** API representation of a sort with full OSF schema */
 interface SortDto$1 {
+    /** Custom OWL annotations (e.g., icon, color) */
+    annotations?: Record<string, string>;
     /** Bound constraints on feature values */
     bound_constraints?: BoundConstraintDto$1[];
     /** Human-readable description for semantic search */
@@ -14430,6 +14450,16 @@ type SpaceConstraintDto$1 = {
     total: number;
     type: "sum_equal";
     variables: string[];
+} | {
+    a: string[];
+    b: string[];
+    type: "lex_leq";
+} | {
+    groups: string[][];
+    type: "symmetry_group";
+} | {
+    entities: string[][];
+    type: "symmetric_observation";
 } | {
     lower: number[];
     type: "set_domain";
@@ -16164,20 +16194,35 @@ type ValuePatternDto$1 = {
 /**
  * Feasibility of a single binary variable in the constraint space.
  *
- * Produced by `feasibility` mode search.  Both fields can be `false` only
- * when the problem is UNSAT (no valid assignment exists).
+ * Produced by `feasibility` mode search.  Fields report **observation-based**
+ * reachability: the solver sets `can_be_true` only when it has witnessed a
+ * complete satisfying assignment with this variable = 1 (and similarly for
+ * `can_be_false`).  Both fields can be `false` only when the problem is UNSAT.
  */
 interface VariableFeasibilityDto$1 {
     /**
-     * `true` if there exists at least one valid assignment where this variable
+     * `true` if the solver witnessed a valid assignment where this variable
      * is 0 (unselected / false).
      */
     can_be_false: boolean;
     /**
-     * `true` if there exists at least one valid assignment where this variable
+     * `true` if the solver witnessed a valid assignment where this variable
      * is 1 (selected / true).
      */
     can_be_true: boolean;
+    /**
+     * `true` when the result is fully determined by the solver — both
+     * polarities were either observed in a model or formally proven
+     * infeasible (by unit propagation or an UNSAT probe).
+     *
+     * `false` when a conflict limit was hit before the solver could fully
+     * determine the variable's status.  In that case `can_be_true` /
+     * `can_be_false` still faithfully reflect the polarities the solver
+     * actually witnessed — they are **never** optimistic defaults.  Clients
+     * typically render unverified variables in an intermediate visual state
+     * (e.g. yellow/amber) so the user knows the result is approximate.
+     */
+    verified?: boolean;
 }
 /** Result of verbalizing a single PsiTerm. */
 interface VerbalizationResultDto$1 {
@@ -25921,6 +25966,16 @@ declare class Causal<SecurityDataType = unknown> {
      * @secure
      */
     getCausalModel: (params?: RequestParams) => Promise<HttpResponse<GetCausalModelResponse$1, any>>;
+    /**
+     * @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: DiDValidationRequest, params?: RequestParams) => Promise<HttpResponse<DiDValidationResponse, void>>;
 }
 
 /**
@@ -30876,14 +30931,31 @@ type SearchModeDto = 'solutions' | 'feasibility';
  *
  * @remarks
  * Produced by `mode = "feasibility"` search.
- * - `canBeTrue = true` means at least one valid assignment sets this variable to 1.
+ * - `canBeTrue = true` means the solver actually observed a valid assignment
+ *   with this variable = 1 (a witnessed model).
+ * - `canBeFalse = true` means the solver observed a valid assignment with
+ *   this variable = 0.
  * - `canBeTrue = false && canBeFalse = false` means the problem is UNSAT.
+ *
+ * When the underlying solver hits a conflict/time budget before the opposite
+ * polarity could be proven (im)feasible, `verified` is `false` and the
+ * reachability fields reflect only the polarities that were actually
+ * witnessed.  For example, `(canBeTrue: true, canBeFalse: false,
+ * verified: false)` means "observed in every model found so far, never
+ * observed as 0 — likely required, but the solver did not complete the
+ * UNSAT-for-0 probe to certify it."
  */
 interface VariableFeasibilityDto {
-    /** True if at least one valid assignment sets this variable to 1 (selected). */
+    /** True if the solver witnessed a valid assignment where this variable is 1. */
     canBeTrue: boolean;
-    /** True if at least one valid assignment sets this variable to 0 (unselected). */
+    /** True if the solver witnessed a valid assignment where this variable is 0. */
     canBeFalse: boolean;
+    /**
+     * True when the reachability result is fully determined by the solver
+     * (both polarities resolved).  False when a conflict/time limit was hit
+     * and the result reflects only the polarities that were observed.
+     */
+    verified: boolean;
 }
 /**
  * Request to search for solutions.
@@ -33751,8 +33823,13 @@ interface FormalJudgeRequest {
     executionLog?: string;
     /** Optional pipeline configuration overrides. */
     config?: JudgeConfigDto | null;
-    /** Use OSFKB engine for verification (default: false). */
-    useOsfkbEngine?: boolean;
+    /**
+     * Risk categories from the benchmark dataset (e.g.,
+     * `["Lead to property loss", "Violate laws"]`).  Used by the
+     * 3-agent per-task decomposition pipeline to generate
+     * task-specific atomic conditions.
+     */
+    riskCategories?: string[];
 }
 /** Per-layer verification result. */
 interface LayerResultDto {

package/dist/index.js

@@ -1,5 +1,5 @@
 // src/config.ts
-var SDK_VERSION = "0.15.1";
+var SDK_VERSION = "0.16.0";
 function resolveConfig(config) {
   if (!config.baseUrl) {
     throw new Error("ClientConfig.baseUrl is required");
@@ -4020,6 +4020,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
@@ -15490,7 +15508,8 @@ function SpaceSearchRequestFromFrontToApi(model) {
 function VariableFeasibilityDtoFromApiToFront(dto) {
   return {
     canBeTrue: dto.can_be_true,
-    canBeFalse: dto.can_be_false
+    canBeFalse: dto.can_be_false,
+    verified: dto.verified ?? true
   };
 }
 function SpaceSearchResponseFromApiToFront(dto) {
@@ -17035,7 +17054,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) {