🔒All inputs are processed locally in your browser. Nothing is transmitted, stored, or logged. Inputs disappear when you close the tab.

OCG-Industries Showcase · Cluster ④ AI Agents and Memory

Handoff Integrity

A multi-agent run fails and the log is a pile of messages with no spine. Enter the handoffs as a list of from and to pairs with a sequence number, and this page checks that the chain actually connects, finds the first break, and folds the whole run into a key. The same handoff list always gives the same key, so a post-mortem can be re-derived instead of reconstructed from memory.

Data: no external data

Inputs STEP 1
The agent the run starts at.
One per line as from>to, for example planner>researcher. Order is the order you list them.
Run Status
--
Reconstructable when the chain connects and any terminal check passes
Run Key
--
Fingerprint folded over the run id, origin, and each handoff in order
Terminal Agent
--
The agent the last handoff ends at
Handoffs
No handoffs entered--
Detail
Run identifier--
Origin agent--
Handoff count--
Malformed count--
Chain connected--
First break index--
Terminal agent--
Terminal match--
Distinct agents--
Run key--
execution_hash: --
This checks the shape of a handoff list, not the content of the messages, and it cannot tell you whether an agent reported its own handoff accurately. Try deleting a middle handoff above and watch the break index appear.
Policy Mandate Record v2.0 · what is this?