Resolve an executor human decision
The audited MANUAL resolution path of a single-tenant deployment: the only route that resolves an executor human decision. A multi-tenant deployment answers 422 SBJ-0053 before any read and must use the audited manual procedure instead. ledgerEvidence is REQUIRED when the revision is UNCERTAIN, and never changes the answer on a proven revision. Journals a human platform administrator’s resolution of the revision’s open human decision under every write key of the revision (one row with no key when it wrote nothing), so the open-order probe stops counting it under HumanDecision. Nothing is sent to any channel: the answer to the court stays with the institution. decisionId binds the resolution to the request it answers (the revision’s latest). A human platform-administrator action (executor_human_decision:resolve, never held by M2M): an application token (SBJ-0044) or a tenant-carrying token (SBJ-0045) is refused with 403. The rows and the audit row commit in one transaction. 200 outcome NOOP: the same resolution was already journaled. 409 SBJ-0051: no open human decision. 409 SBJ-0054: the journal contradicts the resolution (no effect declared on a PROVEN EFFECT revision, or an acknowledgment while the write is undetermined). 409 SBJ-0055: an acknowledgment on a PROVEN NO EFFECT revision. 409 SBJ-0064: an acknowledgment whose transaction ledgerEvidence is the executor’s own effect (a transaction its recovery probe recorded for the revision); movedAmount is the total that left the block account. Each revision is classified, under the same locks as the write, by its journal evidence: PROVEN EFFECT (a posted row or a moving effect) admits only the acknowledgment; PROVEN NO EFFECT (neither, and no moved-needs-human request) admits only the no-effect declaration; UNCERTAIN (a moved-needs-human request without a posted row or a moving effect) admits both, only with ledgerEvidence. 422 SBJ-0052: resolution, reason or ledgerEvidence invalid (reason missing, longer than 200 characters or with personal data), or an UNCERTAIN revision without ledgerEvidence, or movedAmount missing, invalid or not admitted. A release (UNBLOCK or TRANSFER) whose parent block landed without its origin legs is UNCERTAIN whatever its request: its acknowledgement requires movedAmount and a transaction ledgerEvidence. 422 SBJ-0053: multi-tenant deployment (single-tenant only; use the audited manual procedure). 404: unknown revision, or one of an institution this executor does not own (the same answer).
Parámetros de ruta
Cuerpo
Required when the revision is UNCERTAIN: the executor raised moved-needs-human and the journal holds no posted row nor a moving effect, so only the ledger tells whether money moved (missing: 422 SBJ-0052). Optional otherwise, validated whenever present, and it never changes which resolution the journal admits. Stored only in the sealed audit row; never echoed, logged nor traced. On an acknowledgement, a transaction reference is also journaled as the ledger transaction the human read.
The TOTAL, a decimal string above zero (e.g. 150.00), that left the block account for this leg, including any effect the executor already read: an effect of the executor on the same release counts once, never added to it. Required, with a transaction ledgerEvidence, to acknowledge the effect of a release (UNBLOCK or TRANSFER) whose parent block landed without its origin legs: the executor could not plan that return, and the block counts as released only when the acknowledged amounts equal what it holds. Refused anywhere else (422 SBJ-0052); a transaction ledgerEvidence that is the executor's own effect is refused (409 SBJ-0064). Journaled; never echoed, logged nor audited.
"150.00"
Required. proven-no-effect: the ledger evidence shows the revision's writes never landed (refused with 409 SBJ-0054 when the journal shows money moved). effect-acknowledged: the effect is acknowledged as it is (refused with 409 SBJ-0055 when the journal shows no landed effect).
"effect-acknowledged"
Respuesta
OK

