Freight Room: a response room for ship delays

Ocean carriers billed $15.4 billion in demurrage and detention between 2020 and 2025, at $150 to $250 per container per day. When a ship is stuck at anchor, sorting it out means logistics, finance, the carrier, and customer teams chasing each other across separate companies, tools, and inboxes. That coordination gap is where the money and the time leak out. Freight Room pulls that into one room. A Sentinel agent watches a live AIS feed; when a real vessel dwells at anchor, it opens a room in Band and recruits only the agents the incident needs, at runtime. It then names the actual importers whose cargo is on that ship, pulled from public U.S. Customs bills of lading. Seven agents across three frameworks (LangGraph, PydanticAI, CrewAI) work through Band by @mentioning each other: logistics proposes recovery options, finance prices each one against the published Maersk demurrage tariff, the carrier counters on tariff terms, and a dissent agent challenges the leading option before anyone commits. A quorum vote produces a single recommendation, with the dissent recorded right next to it. A human ops manager approves or rejects in the dashboard. The decision flows back into the Band room, and a one-page audit dossier is generated from the full record: every option, cost, vote, the dissent, and the human call, each line tagged with where the number came from. Nothing is mocked. Vessel positions are live AIS, importers come from real customs records (pre-arrival matches are labeled inferred), and costs come from a published tariff. Band is the part that makes it work: the room, the runtime recruitment, the @mention handoffs, and the audit trail all run on Band.