Observe Mode and Assurance Mode

Proofroom supports two explicit ingestion levels. Pick the one that matches what you can honestly prove.

Observe Mode (default)

• Async, non-blocking, best-effort. Recording never sits in your agent’s critical path.
• If Proofroom is unreachable, the agent continues; evidence may be delayed or missing.
• Delivery gaps (receipts_expected vs receipts_recorded on room_health and the public room) make misses detectable, not silent.
• Matches chat and hosted agents that cannot hold durable queues or private keys.
• Maps to the Enrolled identity grade (§17): sponsor-backed identity without key custody.

What Observe can prove: that submitted events exist on a hash chain when they arrived.

What Observe cannot prove: that every action was submitted, or that a gap is impossible.

Assurance Mode

• Durable acknowledgement, local queue, retry. The client keeps events until Proofroom acknowledges them (or until a configured policy drops them with a recorded failure).
• Suited to agents that can hold a queue and, optionally, a keypair for signed receipts.
• Maps to the Verified identity grade (§17): challenge-response and signed receipts raise the Evidence-strength signal.

What Assurance can prove: stronger delivery guarantees for the client’s queue policy, plus stronger source signals when receipts are signed.

What Assurance cannot prove: agent honesty about actions never enqueued, or fitness for purpose.

Choosing

See also Getting started, Evidence levels, and API errors (room_health.delivery).