Signals
Where your team currently disagrees with itself — surfaced from what people actually said in Slack and Gmail, not from a status meeting.
What's a “referent”?
The thing two people are disagreeing about — a launch date, a sign-off owner, a scope decision. The small mono text under each headline (like indep_event.launch_date) is that topic's internal key — system-generated from a fixed vocabulary the team's topics are catalogued against, not something anyone typed in. Not every topic Quorum notices is catalogued; auto-detected ones are tagged “auto-detected” and use whatever phrase the message itself used.
Not every topic changes between snapshots — some stay open with the same live positions across dates, so two dates can look alike.
Known gap: the launch-date item above is supposed to flip from Contradiction to Resolved between 15 and 18 Jul once the studio head's message lands — it doesn't reproduce on this interactive tab, because the free model's read of that one message comes back truncated and is correctly rejected rather than guessed at. The transition is real and verified on the eval path (Evals); see README §8, item 10 for the full explanation.
Nothing needs your attention
No open disagreements at this point in time.
How this page works (for reviewers)
Each row runs through a deterministic pre-rule ladder (R0–R9) before any model is called — same-asserter updates, self-corrections, and authority-based supersession are all decided by code, not by the model. Only a bucket with two or more live claims from different people, with no pre-rule able to settle it, gets a single binary model call: “do these live positions genuinely conflict?” “Rewind the ledger” re-runs the same deterministic pipeline as of an earlier point in time; it does not re-ask the model a new question, it replays the same logic against a smaller set of visible messages.
Full detail in the README: /architecture#pre-rules