Persist one positive terminal observation and resolve matching fences.
Ordinary evidence resolves through an opaque durable adoption receipt. A nil-adoption orphan tombstone is resolved server-side from exact host/session/shim/process and group-reap proof. Time, liveness loss, and fence expiry are not evidence.
workerJwtAuthorizationBearer <JWT>Short-lived worker runtime JWT minted by the platform. Claims bind the worker, project, organization, registration, and scopes.
application/json- body
orgId*string1 <= length <= 256sessionId*string1 <= length <= 256hostId*string1 <= length <= 256shimId*string1 <= length <= 256processEpoch*string^(0|[1-9][0-9]*)$evidenceId*string1 <= length <= 256kind*stringdurableAdoptionCorrelation*string1 <= length <= 4096adoptedControllerGeneration*string^(0|[1-9][0-9]*)$observedAt*string^(0|-?[1-9][0-9]*)$Terminal evidence is durable.
application/json- response
evidence*||revision*string^[1-9][0-9]*$requestDigest*string^[0-9a-f]{64}$resolvedCorrelationCount*integer0 <= value <= 9007199254740991idempotentReplay*booleancurl -X POST 'https://app.rensei.ai/api/daemon/session-shim/terminal-evidence' \ -H 'Content-Type: application/json' \ -d '{ "orgId": "string", "sessionId": "string", "hostId": "string", "shimId": "string", "processEpoch": "string", "evidenceId": "string", "kind": "ordinary_terminal_receipt", "durableAdoptionCorrelation": "string", "adoptedControllerGeneration": "string", "observedAt": "string"}'{ "evidence": { "orgId": "string", "sessionId": "string", "hostId": "string", "shimId": "string", "processEpoch": "string", "evidenceId": "string", "kind": "ordinary_terminal_receipt", "durableAdoptionCorrelation": "string", "adoptedControllerGeneration": "string", "observedAt": "string" }, "revision": "string", "requestDigest": "string", "resolvedCorrelationCount": 0, "idempotentReplay": true}Resolve all five current proof-v2 readiness facts.
Runtime-JWT-only source bound to the authenticated tenant, stable host, current controller, exact stored cutover, and live Relay acknowledgement readiness. It cannot create the global cutover or admit a carrier candidate.
Durably ingest normalized runtime events for one owned session.
Accepts a bounded, versioned batch from the worker runtime that owns the session. The server verifies deterministic event identity and strict monotonic structured sequence, injects authenticated org/project/subject scope, validates each active topic payload, commits idempotent outbox rows atomically, and only then attempts the execution-ledger drain. Redis remains a post-append wake hint.