Interface: DeleteSortResponse
@kortexya/reasoninglayer / DeleteSortResponse
Interface: DeleteSortResponse
Section titled “Interface: DeleteSortResponse”Defined in: src/types/sorts.ts:1440
What a sort deletion removed.
Properties
Section titled “Properties”rulesOrphaned?
Section titled “rulesOrphaned?”
optionalrulesOrphaned?:SortReferencingRuleDto[]
Defined in: src/types/sorts.ts:1474
Rules left naming a sort that no longer exists, under rules: 'orphan'.
Remarks
Section titled “Remarks”Read back after the cascade, so every rule named here still exists. They are not withdrawn — they simply stop firing. Withdraw them yourself with InferenceClient.deleteRule, which applies its own refusals.
sortId
Section titled “sortId”sortId:
string
Defined in: src/types/sorts.ts:1442
The sort that was deleted (UUID).
sortsDeleted
Section titled “sortsDeleted”sortsDeleted:
string[]
Defined in: src/types/sorts.ts:1449
Every sort removed (UUIDs), leaves first, the requested sort last.
Remarks
Section titled “Remarks”One entry, unless descendants: 'delete' removed a subtree.
termsDeleted
Section titled “termsDeleted”termsDeleted:
number
Defined in: src/types/sorts.ts:1457
How many DATA terms were deleted with it.
Remarks
Section titled “Remarks”Rule scaffolding is not counted: the terms of a rule’s conclusion and antecedent patterns stay with the rule.
termsFailed
Section titled “termsFailed”termsFailed:
number
Defined in: src/types/sorts.ts:1465
How many could NOT be deleted, and are therefore orphaned now.
Zero on every ordinary cascade. Reported rather than raised: the request did most of what it was asked, and a bare 500 would say nothing about how much.