Your agent said
it was done.
Who checked?

IRIN is structured multi-model deliberation you run at home on macOS or Ubuntu. War Room is the face: assigned seats, streamed rounds, evidence checks, a chair ruling. Direct provider transport is the default; Gateway is explicit per-seat opt-in. A separate Sentinel/Watch lane — disarmed by default — can end in a signed Outbox directive, so observation, judgment, and authorization stay separated by design.

Below this line, thousands of events are drifting past. One of them matters.

Sentinels are deterministic watchers: files, queues, feeds, ledger deltas. No model calls, no reasoning, a fire decision in under 100 ms. They watch, and they never speak.

When observed state crosses a declared line, a sentinel fires: an evidence-based escalation (facts only, no inference), recorded to a hash-chained fire log. That amber trace is one fire, leaving the noise.

The Watch producer ships disarmed by default. Loading or enabling a Sentinel is not arming; a hardware ceremony arms the Gateway Watch producer.

Direct provider transport is the default. Gateway is explicit per-seat opt-in — never a silent detour for every call. On the Watch lane, an escalation that is promoted crosses Gateway: it meters spend against a hard budget, enforces policy, and can write a signed audit-ledger record for that path. The fire that just passed is now inside irin.comms.v0.1: a versioned envelope with a TTL, a budget hint, and a reply address.

Most events never make it this far. That's the point: the gate earns the next tier its scarcity.

The Council is where reasoning finally happens — and War Room is the room you live in. Multiple frontier models deliberating under a chair, with frame checks, flip-flop detection, budget pause, a convergence judge. make warroom opens that path on macOS or Ubuntu — pick a cabinet, ask a real question, watch the seats argue and converge. Real deliberation still needs a usable provider transport (API key or authenticated CLI).

The Council speaks, but it never acts. An ordinary War Room run does not create a signed Outbox directive — that is the separate Watch→Outbox lane. Budget and clock are hard stops: closed-loop triage bounds at 120 seconds; sessions you convene run on your clock. When the Watch lane does triage, the answer is a directive: a named job, a scope, a stop condition, and what must come back.

The directive is canonicalized, then signed. RFC 8785 JCS bytes, an Ed25519 signature, a signed row in directive_outbox. The companion fire lives on the watch_fires hash chain; each outbox row is individually signed; the governed audit ledger is a separate signed surface. Not a dashboard claiming success: a verifiable artifact that does not trust anyone's self-report, including ours.

The signed record is the product endpoint — no autonomous operator-ready Worker ships. Not every action is recorded or executed.