Skip to content
KortexyaKortexyaReasoning Layer SDK

Interface: UpdateScenarioRequest

@kortexya/reasoninglayer

@kortexya/reasoninglayer / UpdateScenarioRequest

Interface: UpdateScenarioRequest

Section titled “Interface: UpdateScenarioRequest”

Defined in: src/types/scenarios.ts:500

Request to incrementally update a scenario.

Remarks

Section titled “Remarks”

Adds new sorts, beliefs, rules, constraints, guard constraints, temporal constraints, and/or webhook actions to an existing scenario.

The items are the same objects a GeneratedScenario holds in the matching collection. The field names of this request are mapped to the wire (addBeliefs to add_beliefs). addRules is mapped field by field: each ScenarioRule goes out as head, antecedents and certainty, each term as sort, features, negated and binding, and only features goes out as written. The items of every other add* collection go out unchanged: write their keys as the engine reads them (see GeneratedScenario).

Properties

Section titled “Properties”

addBeliefs?

Section titled “addBeliefs?”

optional addBeliefs?: unknown[]

Defined in: src/types/scenarios.ts:502

Additional beliefs to materialize.

addConstraints?

Section titled “addConstraints?”

optional addConstraints?: unknown[]

Defined in: src/types/scenarios.ts:504

Additional generic constraints to materialize.

addGuardConstraints?

Section titled “addGuardConstraints?”

optional addGuardConstraints?: unknown[]

Defined in: src/types/scenarios.ts:506

Additional guard constraints to materialize.

addRules?

Section titled “addRules?”

optional addRules?: ScenarioRule[]

Defined in: src/types/scenarios.ts:512

Additional rules to register, in the same REST rule encoding as GeneratedScenario.rules. A refused rule is named in UpdateScenarioResponse.warnings, not thrown.

addSorts?

Section titled “addSorts?”

optional addSorts?: unknown[]

Defined in: src/types/scenarios.ts:514

Additional sorts to add (appended to existing hierarchy).

addTemporalConstraints?

Section titled “addTemporalConstraints?”

optional addTemporalConstraints?: unknown[]

Defined in: src/types/scenarios.ts:516

Additional temporal constraints to materialize.

addWebhookActions?

Section titled “addWebhookActions?”

optional addWebhookActions?: unknown[]

Defined in: src/types/scenarios.ts:518

Additional webhook actions to materialize.

prefixes?

Section titled “prefixes?”

optional prefixes?: Record<string, string>

Defined in: src/types/scenarios.ts:525

Prefix bindings (prefix → namespace IRI, '' = the default prefix) the CURIE names of addSorts use. Same contract as BulkCreateSortsRequest.prefixes: bound on the tenant with the added sorts, and released again when they are refused. The keys go out verbatim.