Routed by policy
Use explicit rules to determine when review is required and which role has authority to decide.
AI Control Plane / HITL Inbox
Human review,
ready to use.
Connected to the work.
When policy requires a person to decide, give an authorized member of your team the exact proposal, evidence and a real-time case thread. Their decision returns to the waiting workflow, bound to the revision they reviewed.
FROZIONExecution FabricGoverned from request to outcome
Exact proposal · revision r3
Review requiredSupplier bank change
- Proposal
- ACME-204 · account ending 4821 → 9056
- Why it’s here
- Finance approval + FIDO2 required by policy
- Facts with sources
- bank_changes_30d = 2 · source + freshness checked
Real-time case thread
Finance reviewer Is the supporting supplier document attached?
Case owner Yes. The evidence package is linked to proposal r3.
Approve · FIDO2Request informationReject
Decision options shown for this sample case. No live approval is performed on this page.
The HITL Inbox across your adoption path
Govern existing agents
Sensitive agent actions wait for an authorized internal reviewer, with the proposal and evidence.
Grow tools into workflows
Human review becomes a connected workflow step, routed by policy.
Build native agents
Native agents hand required decisions to the right internal people.
Build systems of engagement
Application workflows connect to the same internal review case and its decisions.
01 / The gap
“Approval required”
is the beginning of the review.
A policy decision still needs a process: the authorized reviewer, the exact case, a way to discuss missing evidence, a durable wait and a checked return to execution. The HITL Inbox brings those responsibilities together inside Frozion.
decision: approval_requiredA person, the evidence, a decision and a path back to the work.02 / What’s included
What the reviewer needs.
What the process needs back.
A ready-to-use review experience for internally assigned members.
The exact case
See the proposal revision, relevant facts with sources, evidence and the reason for review together.
A real-time case thread
Discuss the exception, ask colleagues a question or request supporting information in the same case.
Clear decision status
Approve, request information or reject. An information request stays separate from an approval.
FIDO2 assurance
Require passkey step-up for a high-risk decision and bind the approval to the exact revision reviewed.
Back to the workflow
Return the decision to the waiting case. Recheck authority, policy and the approval before a protected action.
03 / How it connects
Policy, review and execution.
One connected process.
- 01
Policy
The supplier change needs finance review with FIDO2.
- 02
Durable wait
The workflow holds the case while the decision is pending.
- 03
HITL Inbox
An authorized internal reviewer sees the proposal, facts and thread.
- 04
Revalidation
Current authority, policy, facts and approval binding are checked.
- 05
Governed action
Attempt the eligible operation and record the destination’s response.
Identity and FIDO2A named reviewer, with the assurance required by the rule.
Connected case recordThe request, review, decision, wait, action attempt and reported result stay connected.
The Inbox is part of the Control Plane. You configure the review rule and authorized role within the workflow, using the platform’s shared identity and evidence services.
04 / Build vs ready
The review process
is already part of the workflow.
If a policy decision is your starting point, these are the responsibilities the review process still needs to connect.
| Responsibility to connect | Included in Frozion |
|---|---|
| An authenticated review experience | The HITL Inbox for internal members |
| The right authority to decide | Policy-defined review roles |
| Proposal, facts and supporting evidence | A case view with eligible context and sources |
| Discussion and requests for information | A real-time case thread |
| Stronger assurance for a sensitive decision | FIDO2 passkey step-up |
| Approval for the action that will run | Binding to the exact reviewed revision |
| State while the decision waits | A durable workflow case |
| A checked return to execution | Revalidation before the protected operation |
| Evidence across the review and action | One connected execution record |
05 / Scope and questions
Who reviews the case.
What their decision means.
For assigned internal members. Customers, vendors and partners participate through App Builder portals.
Permitted context. Reviewers see the evidence their role and case scope allow; a review task does not grant unrestricted data access.
People decide; models propose. An AI recommendation is not an approval.
One proposal revision. A material change needs the appropriate new review. Expired or revoked authority must be resolved before action.
No. Configure when review is required and the authorized reviewer role. The HITL Inbox, case thread and return to the waiting workflow are included. Define the application’s evidence and permitted integrations as part of the business process.
The Inbox serves internally assigned members. Use App Builder portals for external participants and connect their permitted tasks to the same business process.
Yes. Existing agents can invoke a Frozion tool or workflow over MCP or HTTPS. When policy requires review, the workflow holds the protected action and connects the case to the HITL Inbox.
Approval belongs to the reviewed revision. Re-evaluate the changed proposal and obtain the appropriate new decision before execution. A previous approval is not standing permission for a different operation.
The protected operation stays held. A request for information or a pending review does not become approval. The workflow continues only when the configured conditions are satisfied, with revalidation before action.
See the connected review
See an approval,
end to end.
Trigger a review requirement, inspect the case, discuss the evidence, approve with FIDO2 and follow the checked path to the reported result.