[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"article-body-the-agent-question-is-an-exception-question":3},"\nEvery platform now sells agent governance. Guardrails to bound\nbehaviour, identity so agents can be permissioned like employees,\ncontrol planes to watch them work. Kinaxis frames its supply chain\nagents as\n[\"governed, not autonomous\"](https://www.kinaxis.com/en/blog/long-running-ai-agents-supply-chain-orchestration),\nand the phrase could stand for the industry's whole posture. All of\nit answers one question. What may the agent do?\n\nNone of it answers the question you will actually manage by. Of the\nmillion actions agents take on your behalf this week, nearly all of\nthem correct and inside policy, which handful genuinely needs a\nperson, and who decides?\n\n## A century of prior art\n\nThat question is not new. Management by exception is roughly a\nhundred years old; it is the discipline that lets a plant manager\nrun a factory without watching every machine, because thresholds,\nmateriality rules and escalation paths decide what surfaces. The\nmanager's attention is treated as the scarcest resource in the\nbuilding and spent accordingly.\n\nAgents multiply the actions taken on your behalf by orders of\nmagnitude, which multiplies the value of exactly that discipline.\nAttention does not scale with the fleet. The routing rules must.\n\n*Autonomy is safe where exceptions are routed well, and unsafe\neverywhere else.*\n\n## Governance without routing is a promise\n\nRead the governance messaging closely. It describes what agents are\nprevented from doing, and it never says which deviations are\nmaterial, who gets interrupted at what severity, or what happens\nwhen an exception is ignored.\n\nPicture the first month of a deployed fleet. A planner arrives on\nTuesday to find four hundred purchase orders re-sequenced overnight,\nevery one inside policy, and one of them quietly cancelling a\ndelivery a key account had been promised. Which of the four hundred\nshould have interrupted someone's evening? The guardrails have no\nopinion; nothing was breached. The person explaining the missed\npromise on Thursday's call will have one.\n\n## The routing spec\n\nTreat agents as an exception problem and you get a specification\ninstead of a posture. Every class of machine action gets a\nmateriality threshold. Crossing it creates one exception with a\nseverity, an owner and a deadline. Exceptions are deduplicated and\nranked, because ten duplicate alerts bury the one that matters.\nEscalation fires when the clock runs out, and every routed exception\nrecords what the human did, so the thresholds get reviewed against\nevidence rather than folklore.\n\nNone of that is speculative. It is what\n[management by exception at machine scale](/insights/millions-of-events-in-a-handful-of-decisions-out)\nalready looks like in production, applied to a new source of events.\nAgents do not change the discipline, but they make skipping it much\nmore expensive.\n\nProphesee's answer to the agent question is Pulse, which routes\nmillions of events into the handful of decisions that need a person,\nwith thresholds, owners and clocks attached. It is one exception\nengine shared across every module, so an escalation rule proven in\none corner of the business is inherited by the next. A bolted-on\ncontrol plane cannot compound like that. To see your own exception\nstream, [start here](/contact).\n",1786984937301]