Interface: FunctionDefinitionSignature
@kortexya/reasoninglayer / FunctionDefinitionSignature
Interface: FunctionDefinitionSignature
Section titled “Interface: FunctionDefinitionSignature”Defined in: src/types/functions.ts:516
The signature half of a read definition — everything that answers whether or not the clauses could be expressed.
Properties
Section titled “Properties”arity:
number
Defined in: src/types/functions.ts:522
The number of named arguments it accepts.
callers
Section titled “callers”callers:
FunctionCaller[]
Defined in: src/types/functions.ts:543
Everything that calls this function, by the same scan DELETE refuses on
and PUT reports.
Read before offering an edit: a replacement that changes the arity keeps every one of these resolvable and makes every one of them wrong. Empty when nothing calls it.
functionId
Section titled “functionId”functionId:
string
Defined in: src/types/functions.ts:520
Its stable id, as the registration reported it.
kind:
FunctionKindDto
Defined in: src/types/functions.ts:524
Whether it is classical or neural/fuzzy.
name:
string
Defined in: src/types/functions.ts:518
The function’s name — the key POST /functions/evaluate takes.
notReplaceable?
Section titled “notReplaceable?”
optionalnotReplaceable?:FunctionNotReplaceableDto
Defined in: src/types/functions.ts:534
The refusal a PUT would produce. Absent while replaceable is true.
replaceable
Section titled “replaceable”replaceable:
boolean
Defined in: src/types/functions.ts:532
Whether PUT/DELETE on this function will act rather than refuse.
Read through the same admission the mutation routes run, so the read and the refusal cannot disagree. The engine stays the authority: a state change between this read and the write can still refuse.