When an operation goes wrong, the surgeon, the anaesthetist, the scrub nurse and the bedside team each saw something different. Recount takes every account privately, seals it, and reveals them together, under letters, so the most senior voice can't shape the rest. Any operation, any theatre team.
01 · The room
The demo case is a remote robotic operation, so the robot's own log joins as a fifth witness. Five agents sit in a Switch room with the team. Each person talks to their own witness agent in private; the room only ever sees seals. Press play.
02 · Seals
A fingerprint and a time, never a name or a word of the account. At the reveal every account is checked against its fingerprint, so nobody can rewrite their story after hearing the others.
| Slot | Fingerprint | Sealed | Status |
|---|
03 · Report
Built by plain code from the five sealed accounts, for the morbidity and mortality meeting. Questions for the team, not blame.
04 · How it works
Each person gives their account to their own witness agent, by voice or text, on their own machine, with their own records beside it.
The agent compares the draft with the person's own chart or count sheet, privately. On their word, the account is sealed and its fingerprint posted.
The referee refuses to reveal while any account is out, however senior the person asking. The accounts live in code, not in any AI's memory.
At the reveal every seal is verified and accounts appear as Witness A to D. A name is added only when its owner agrees.
Every witness agent belongs to one person and runs on their machine, next to their own records. Switch puts five of them and the team in one room, decides who each agent takes instructions from, and records every approval.
The case, the people and the robot log are fictional; no patient data is used. The sealing, the checks and the report are the real code in this repository, and the agents run in a real Switch room.