For the Head of Claims
A declined claim is a decision. Six months later, can you show who made it — and what was argued against it?
The file will hold an outcome, a reference number and a letter. What it will not hold is the argument: which considerations were weighed, who disagreed, what evidence each of them was actually looking at, and which named person carried the ruling. That is the part the ombudsman, the regulator and the litigator all ask for, and it is the part that was never written down.
One case, four seats, and a chair who has to sign
Coverage seatAccept
slice: the wording, the endorsements, the schedule
Argues the claim falls inside the insuring clause; flags one endorsement as decisive.
Liability seatRefer
slice: the loss narrative, the adjuster report, the third-party file
Argues quantum is unsupported by the report on file and asks for re-inspection.
Policyholder-advocate seatAccept
slice: the customer history, the correspondence, the sold representations
Argues the exclusion was never disclosed at the point of sale.
Red-Queen seatPuncture
slice: the other seats’ own arguments — nothing else
Attacks the emerging consensus: two seats are reading the same document and calling it two sources.
DISSENT IS KEPT, NOT RESOLVED BY VOTE
The room does not average four opinions into one number. The structure of the disagreement — who diverged, on which slice, and on what evidence — is what the chair reads before ruling, and it stays in the thread afterwards.
AWAITING THE CHAIR
- chair
- a named human, not a role mailbox
- ruling
- accept · decline · refer, with reasons captured
- waitpoint
- durable — the job survives a restart and waits
- override
- permitted, recorded, and attributed
- on timeout
- the room fails closed and escalates; nothing releases
- on sealing
- the ruling closes the thread and the record becomes replayable
[O] Illustrative composition, built from the components the product ships. No customer data appears anywhere on this site. Rooms, typed messages, persona invocation and the live relay are observed at PC/src/routes/rooms.routes.ts, PC/src/blueprint/CharacterBibleManager.ts and NX/services/nexus-gateway/src/websocket/room-event-relay.ts.
The mechanism, in three lines
Versioned expert personas argue the case from different angles — including one seat whose only job is to attack the conclusion — and a named human chair rules, at a durable waitpoint.
First
Each seat gets its own evidence
A persona is a versioned, drilled definition with an assigned evidence slice. Two seats reading the same document are one source wearing two hats, and the room refuses to count it twice.
Then
One seat exists to attack
The adversarial seat is designed and drilled to puncture the emerging consensus before the chair ever sees it. Agreement that survives it is worth something; agreement that never met it is not.
Finally
A named human rules
The chair reads the dissent, rules with reasons, and can override. The ruling is a durable waitpoint — the work waits for the person, rather than the person catching up with the work.
shipped(shipped)The chamber is the contested lane, not every decision. Most cases never convene a room — they still pass the gate.
PC/src/routes/rooms.routes.ts and NX/services/nexus-gateway/src/websocket/room-event-relay.ts; the persona-bible pattern to PC/src/blueprint/CharacterBibleManager.ts; the durable human-approval waitpoint to NX/services/nexus-orchestrator/src/routes/dispatch-routes.ts. “Fails closed” means the room produces an escalation rather than an output — there is no default ruling to fall back on.The honest limit
EVERYTHING ON THIS PAGE IS SHIPPED
Every capability described above resolves to a repository path we publish. Where a pillar has an unbuilt part, that part is named on its own page — see thetrust centre for the full register.