Skip to main content
server.OccurrenceCustody The accepted occurrence an operation invocation is processing. An occurrence’s verified body stays in the engine’s custody; the handler is given a reference to it — the occurrence identity, its event type and the body’s SHA-256 — as ordinary arguments, and reads the bytes through here. Two things follow. The retained invocation record holds the reference and never the provider’s payload, so the operation’s contract competes with nothing for that record’s size. And removing the retained payload removes the engine’s copy of those bytes, rather than leaving them in invocation history. The host answers only the transaction that is processing that exact occurrence, under the same service actor whose grants authorize the handler. It is not a way to read stored payloads: an ordinary call of the same operation, a preview, or a read after the occurrence settles is refused.

​
Methods

​
payload

▸ payload(): Promise<string> The exact verified JSON the provider sent, byte for byte. It is returned as a string and parsed by the handler, so provider integers and decimals never pass through a host float on the way in.

​
Returns

Promise<string>