Deadline Room

When a company is breached, the clock starts on several regulators at once: NIS2 in 24 hours, DORA in 72, the SEC in four business days, the UK ICO in 72. Miss one and the fines, and personal liability, land on named officers. The obvious move is to let LLM agents draft the filings. The catch: ask a language model to compute a statutory deadline and it is wrong 25 to 74 percent of the time, and it obeys prompt injections. You cannot let a model decide what gets filed. Deadline Room splits the job. LLM drafter agents, one per regulator, research and write filings and collaborate live in a Band room. A deterministic Warden, pure Python with no model in the loop, decides and proves. It enforces every handoff through Band and guarantees three things on camera: - Exactly-once under a live kill. Kill an agent mid-filing and it reconnects and re-posts; the Warden's idempotency ledger drops the duplicate. Zero double-files across 5,000 kill schedules. - A contradiction veto. When two filings disagree on a load-bearing fact, when the incident started, the Warden blocks all signoff until they reconcile, then requires two distinct human keys. - Byte-identical replay. Every run seals to a hash-chained, Ed25519-signed log. Replay it offline and you get the same bytes, the same hash. Flip one byte and the signature breaks. A regulator verifies it on their own laptop. Thirteen regulatory regimes ship as config, with business-day clocks that know federal holidays and real EDGAR 8-K filings with inline XBRL. It runs live on Band, three multi-agent incidents proven, each replaying byte-identical, and is production-shaped: Kubernetes, Terraform, a two-key approval gate, multi-model failover, and a sovereign air-gapped mode. The hard part, exactly-once on Band, is extracted as an open library any builder can install. Over 1,435 tests, all green. The agents draft. Python proves.