The platform floor is the set of actions a governed agentic operating system refuses on purpose for every agent, at every depth, for every customer. The actions exist and work, but no agent may take them. The verdict for an action at the floor is withheld. Reversing a settled payment on Pryme's own rail is an example.
Why does a platform floor matter?
Customers decide much of what their agents may do, and they should. But some actions carry consequences that reach beyond one customer: harm to third parties, damage to payment systems, or outcomes no business would defend if asked. For those, a customer setting is the wrong control, because settings can be misconfigured, pressured or changed by someone without the full picture.
The platform floor puts those actions beyond any setting. It is the fifth bound every action meets, the platform guardrails, and it is the only one a customer cannot move. The design is described in agent governance is a bound, not a model.
How does the platform floor work in practice?
- It is set by the platform, not the customer. Withheld is a platform decision, not a customer setting.
- It applies to every agent at every depth. Certification cannot earn past it; a customer ceiling cannot raise it.
- It is narrow. It covers a small number of actions where the case for never delegating is clear.
- It is recorded. Each withheld verdict is filed, naming the platform guardrails as the deciding bound.
Customers narrow what their agents do through their own limits, and those actions are refused or held. Only the floor produces withheld. Keeping that distinction clean means a withheld verdict always means the same thing.
What does that look like in an example?
A payments business runs an agent that handles merchant queries, with payments settling on the platform's own rail. A merchant writes that a payment to a supplier settled yesterday was a mistake and asks for it to be reversed. The agent is certified at depth 4 for merchant refunds, and the merchant's limits would cover the amount. But reversing a settled payment on that rail is at the platform floor. The verdict is withheld. The agent tells the merchant that it cannot reverse a settled payment, explains the recall process, and drafts a case for the operations team, which follows the scheme's own procedure with the receiving bank.
How is the platform floor different from a certification floor?
The words are similar, but they mean different things. A certification floor is the minimum score an agent must reach on one certification gate. It is set by the person who owns the work, for that customer, and it decides whether the agent earns a depth. Setting one is covered in the pass floor setting template for certification gates.
The platform floor is not a score. It is a list of actions that are never delegated, regardless of how well any agent performs. A perfect certification run does not move it.
How is it different from a human gate?
A human gate holds an action until a named person approves it, and then the action goes ahead. The platform floor does not hold; it withholds. There is no approver who can release a withheld action through the agent. If the action needs to happen, a person carries it out through the business's own controlled process, outside the agent's authority.
Questions people ask
Can a customer ask for an action to be removed from the platform floor?
No. The floor applies to every customer equally, which is what gives it meaning. Customers can add their own restrictions on top, through their limits, but cannot remove what the platform withholds.
Why not just refuse those actions instead of having a separate verdict?
Because the reason is different and the owner is different. A refusal means the action is outside this agent's bounds and might be within another's. Withheld means no agent may take it at all. Keeping them separate tells reviewers immediately whether a change in settings could ever have produced a different outcome.