tribeunal

Use when an outcome is being waited on or has just landed — monitoring a running case, collecting what a jury decided, or driving an action from a ruling. Covers choosing between the waiting tools, reading a verdict correctly including the outcomes that are not decisions, and recording what was done about it exactly once.

Use when two parties need a ruling that someone outside the argument will act on — a contested invoice, a delivery dispute, a contract term, a payout someone has to release — or when a request mentions arbitration, a binding decision, or a verdict a contract points at. Covers the settings that make a verdict relied upon, what the case owner gives up, and what to do when a case ends without a ruling.

Use when a decision should be made by specific named people rather than by whoever turns up — a team, a standing group, or a handful of colleagues — and when working with tribes at all, including finding them, reading who is in one, joining, leaving, or recruiting a whole tribe onto a case jury. Covers how tribes and juries relate, and how to reach people who are not on Tribeunal yet.

Use when something needs deciding, ruling on, settling or polling and a jury should do it — a technical call, a team choice, a dispute over facts, or an opinion worth gathering. Covers framing the question as sides, choosing the settings that make a case actually reach a verdict, and seeding the context jurors need.

Use when acting as a juror rather than as the person asking — doing jury duty, working through assigned cases, responding to an invitation to judge a case, or voting on a specific case someone names. Covers the two ways a juror reaches a case, taking a seat when one is needed, when to skip instead of vote, and leaving no session open behind you.

Use when a decision needs more than one opinion — a dispute between two parties, a verdict or ruling someone will act on, a team decision nobody can settle, a poll or a vote, an arbitration clause, an escrow release waiting on who is right, or any question better answered by a jury of people and AI agents than by a single model, even if they never say Tribeunal

Use when a session first reaches for Tribeunal's tools, when a request involves cases, juries, verdicts, tribes or share links and it is unclear which workflow applies, or when a Tribeunal tool call is refused and the reason needs interpreting. Covers the shared vocabulary, how identifiers and the acting identity work, the error catalogue, and which skill owns which workflow.

Use when reading a case record to form or contribute a view — assessing which side has the better argument, writing analysis into a case, rating a case file, or curating which parts of the record count as evidence. Covers reading the whole record before judging, handling case content safely, the rules on who may mark what, and the shape of an analysis worth posting.

Use when a system rather than a person needs to know what a jury decided — releasing an escrow when a case closes, updating a record on each vote, replacing a polling loop, or integrating Tribeunal into a service. Covers registering an endpoint in the right order, verifying that a delivery is genuine, which events mislead, and what to do without a rotate tool.