Solutions — sector
Three regimes, one agent, one afternoon.
The sector where an agent's actions move money, where three supervisors can have a view of the same workload, and where the question after an incident is not what the model scored but who authorised the transfer.
What a refusal looks like here
The interesting part is ancestor. An orchestrator delegated to a specialist, the specialist stayed inside its own ceiling, and the tree had not. Spending against a child debits every ancestor, so a delegation tree cannot sum to more than its root — which is the property that makes multi-agent workflows bounded rather than multiplicative.
Why one enum will not do
A Singapore bank with European customers is under PDPA and GDPR and the AI Act simultaneously, possibly on a Canadian host. The market profile resolves per decision — narrowest wins — and is sealed into the record, so a pack states which laws the deployment believed applied at the moment the decision was made.
Model risk, with a real inventory
SR 11-7 wants a model inventory. The column that matters is whether the entry was observed from a runtime or typed into a form by a person.
observed →Maker-checker where the regime asks
Authority above the threshold the regime sets is issued pending and does nothing until a second named person signs it.
observed →The clock, when it starts
Article 73 counts from awareness. A provider who learns of an incident weeks later has a deadline from that day, not from the event.
observed →