The Engine Room: one chat for noise
All routine machine output delivers to one designated chat; the main chat receives only escalations that cross a bar set when each job was created.
The problem
Dozens of useful jobs, each arriving in a conversation and asking to be read, become a second inbox. The automation census here reached 93 scheduled jobs, plus 7 enabled hooks; without routing rules, even useful jobs are noise.
The arrangement
Create one designated chat for routine machine output: heartbeats, health checks, deploy watches, bookkeeping. The main chat stays available for decisions, exceptions, and work the operator asked to see. Escalation is a property of the job, set when the job is created, not a judgment call made at 3 a.m. by a tired process. Every standing job is registered with a purpose, a class, a delivery home, an escalation bar, and a sunset or review date. An unregistered live job is treated as drift.
What it costs to run
A registry someone owns, and a weekly digest that reports drift, expiries, and escalations. The Engine Room is not a junk drawer; it is an instrument panel with an owner, an inventory, and a review rhythm.
Starter template
Registry entry Job: <name> Purpose: <one plain line> Class: bookkeeping / push-born watch / long-horizon guard / delivery / one-off / exempt Delivers to: the Engine Room (never the main chat) Escalates when: <bar written in advance> Sunset or review: <date>