One consequential action. One exact owner decision.
Qeravio publishes five bounded escalation classes for every declared AI unit. A valid request can describe one exact decision for the venture owner, but this public surface does not send a message, collect an approval or execute the action.
An approval plan is not evidence that the owner received or approved it.
This page does not prove owner authentication, notification delivery, approval storage, durable replay protection, spend, publication, account change, irreversible execution, tenant isolation or whole-product coverage.
01 / Per-unit policy
Five escalation classes. Nine AI units. No hidden bundle.
Every valid dry-run request is bound to one task, one serving Worker, one rollback Worker, one AI unit, one independent AI checker and one fifteen-minute evidence window.
No exact-version escalation policy is available for this response.
02 / Escalation meaning
Each class asks one question and grants no authority.
Financial scope
Money
Would the owner approve this exact financial commitment? No amount is charged here.
Commitment scope
Commitment
Would the owner accept this exact external obligation? No term is accepted here.
Publication scope
Sensitive publication
Would the owner approve this exact sensitive release? Nothing is published here.
Account scope
Account change
Would the owner approve this exact account change? No account or credential is changed here.
Irreversible scope
Irreversible action
Would the owner approve an action without a verified recovery path? It remains blocked here.
03 / Open gates
What must pass before a packet can become an approval.
Gate 1Build an authenticated owner flow before presenting any decision as approved or rejected.
Gate 2Create one durable, idempotent notification route before claiming that an escalation reaches the owner.
Gate 3Persist redacted approval records with exact scope, expiry and immutable decision evidence.
Gate 4Connect approved decisions to a central fail-closed execution gateway without widening their scope.
Gate 5Prove durable replay protection, organization isolation and cancellation across concurrent requests.
Gate 6Measure repeated escalation use, response time, wrong-decision recovery and whole-product coverage before widening the claim.
Version binding
One serving Worker. One rollback Worker. One exact decision shape.