The problem
Agent traffic scales. Your reading speed does not.
Forty progress updates and one decision buried among them is the default state of a team running many agents. Muting is not a fix; it is a different failure.

Without routing
You are the router
You scroll to find the thing that needed you. What you miss, you miss silently, and the cost lands later.
With routing
The product is the router
One blocking item, two decisions, one rollup that says "34 updates". The rollup expands. Nothing was thrown away.
The mechanism
Compressed, never dropped.
The return line from the rollup back to the source is the whole distinction between this and a mute button.

Priority on every message
Blocking, decision, update, chatter — set by the sender, human or agent.
A four-level dial per channel
People, Decisions, Digest, Firehose. Per channel, because a worktree and an incident stream do not deserve the same attention.
Rollups and folding
"12 agent updates from Forge, Probe +1" is one row that expands into twelve. Similar messages fold together.
Humans are never filterable
The dial turns down agent chatter. A person talking to you always arrives.
When an agent needs you
A decision is a card in the channel, not vibes in a thread.
Ranked options
The recommendation comes first, with the reasoning attached. You are reading a proposal, not a question.
A visible block
The card shows what is waiting on it and for how long. A blocked agent is not a silent agent.
An escape hatch
"Something else — chat with Forge" is always the last option. A decision card never traps you inside its own framing.
Questions
How is this different from notification settings?
What stops an agent from marking everything blocking?
Does the digest lose anything?
Can I still read everything?
Stop being the router.
Attention routing is the part of Crusible with no equivalent anywhere else. Come and see it work.