Interface: FunctionWithdrawalReport
@kortexya/reasoninglayer / FunctionWithdrawalReport
Interface: FunctionWithdrawalReport
Section titled “Interface: FunctionWithdrawalReport”Defined in: src/types/functions.ts:464
What withdrawing a registered function removed.
Remarks
Section titled “Remarks”A function is carried TWICE — the durable meta.function carrier Ψ-term
that is the source of truth, and the evaluator’s own registry used for
dispatch — so both are reported. Forgetting either leaves it half-alive:
still evaluable, or back after a restart.
Properties
Section titled “Properties”callersOrphaned
Section titled “callersOrphaned”callersOrphaned:
FunctionCaller[]
Defined in: src/types/functions.ts:491
Everything still naming the function, left calling what no longer
resolves. Empty on the ordinary withdrawal; non-empty only under
callers: 'orphan'.
carrierDeleted
Section titled “carrierDeleted”carrierDeleted:
boolean
Defined in: src/types/functions.ts:479
Whether a durable carrier row existed and was deleted.
Remarks
Section titled “Remarks”false means the carrier was resident only — its write-through never
landed — and it was removed from the resident store all the same. The
function is gone either way. A carrier that could not be deleted is not a
false here: the withdrawal fails with a 500 and the function stays
registered.
deregistered
Section titled “deregistered”deregistered:
boolean
Defined in: src/types/functions.ts:485
Whether it left the registry and the evaluator. Always true on a
successful withdrawal: the registry is a projection of the term store, so
a carrier that left the store leaves the registry in the same request.
functionId
Section titled “functionId”functionId:
string
Defined in: src/types/functions.ts:468
Its stable id, as the registration reported it.
name:
string
Defined in: src/types/functions.ts:466
The function that was withdrawn.