Wait without losing the case
Retain progress, obligations and the proposal while a person or system is pending.
Durable Execution & Human
Decisions
Pause the work.
Keep its meaning.
Agent work waits for people, events and slow systems. Frozion preserves the case independently of the calling agent’s session, rechecks current conditions on continuation and keeps an uncertain external effect visible until it is reconciled.
Keep proposal revisions, policy, authority, approval and outcome evidence connected through the wait. Resume the governed process from its recorded state instead of asking the agent to reconstruct the case.
FROZIONExecution FabricGoverned from request to outcome
SUPPLIER ACCOUNT CHANGE
Waiting for review
Execution EX-041
-
Validate proposal & evaluate policyProposal P-8472 · revision 2 · policy v4Recorded
-
Obtain the human decisionAuthorized finance review + FIDO2 requiredPending
-
Wait for supplier confirmationCorrelate the event to this proposal and waitNext
-
Revalidate before the updateProposal · authority · policy · resource stateRequired
-
Confirm the business outcomeOperation identity, attempts and effect evidenceNot attempted
Durability connects the whole consequential path
Persisted execution stateBound human decisionsHITL + FIDO2Governed recoveryEnd-to-end evidence
Durable execution across your adoption path
Govern existing agents
A governed operation can retain its case after the calling agent’s session ends.
Grow tools into workflows
Keep the work through waits and revalidate before the next protected action.
Build native agents
Native agents participate in workflows with durable state and controlled continuation.
Build systems of engagement
Applications retain their cases while people, evidence or external responses are pending.
The problem this solves
The business process can outlast the session that started it.
A person may decide tomorrow. An external system may return late or time out after completing a write. The workflow needs a durable case and an explicit next step.
Resume with current authority
Preserved state explains the work; current checks decide whether it may continue.
Reconcile uncertain effects
A missing response is not proof that a consequential write failed.
For agents you already operate
A tool call can be
a complete durable process.
Keep your agent's language and framework. Put the consequential work on a governed execution path.
An existing agent can invoke a Frozion workflow through a supported integration. Inside that workflow, orchestrate data access, calculated facts, policy, per-step RBAC, human decisions and external actions—with durable state and an inspectable execution graph.
The process can outlast the original request. Define how the caller receives a result or tracks completion through the integration's response, status or event contract.
EXISTING INVESTMENTYour agent proposes or requests the work
FROZION EXECUTIONThe workflow governs every configured step
BUSINESS RESULTReturn an outcome with connected evidence
Coverage follows the integrated workflow and its configured enforcement points. Define the caller contract and the paths that can reach each protected action.
01 / Durable continuity
Work on business time.
Resume with context.
Wait for a reviewer, document, callback or other business event. The original browser or calling agent session does not need to stay open while the workflow holds the case.
The Execution Instance preserves the state needed to decide where to continue, whether continuation is allowed and what the next action may do.
THE WORK
Proposal & progress
Execution identity, current state, active proposal, expected event and pending obligations.
ITS AUTHORITY
Policy & human decisions
Actor and tenant context, policy references, approval bindings and assurance requirements.
ITS INTERPRETATION
Versions & evidence
Published Graph version, relevant definitions, operation identity and the history of transitions.
FOLLOW ONE GOVERNED SUPPLIER CHANGE
What may this execution do next?
State carried with the work
- Human decision
- Pending authorized finance review
- FIDO2 assurance
- Required · not recorded
- Current authority
- Resume event
- Supplier confirmation not yet expected
- External attempts
- 0 · no update attempted
- Effect evidence
- No effect receipt
An execution, a human decision and a business operation have
distinct identities. Their relationship is preserved across
waits and attempts.
The resume contract
An event must belong
to the work it advances.
A callback can be technically valid and still refer to another tenant, an older proposal, an expired wait or a changed resource. Define the business conditions an event must satisfy before it advances execution.
Check identity and correlation together with current authority, policy and state. Handle duplicate and late events explicitly within the configured process.
Connect event contracts to strict schemas
RESUME CONTRACT · CONFIGURED CHECKS
- Belongs here
- Event identity · tenant · Execution Instance · expected wait
- Matches the work
- Proposal · resource · current business state
- May advance
- Authority · policy · expiry · relevant version
- Is handled once as intended
- Explicit duplicate and late-event handling
INFRASTRUCTURE CAN CHANGE
The same execution can resume on another eligible node.
Persist the durable state, receive the relevant event later and continue the same business execution. Its identity and governed meaning remain connected even when the process performing the work changes.
02 / Integrated human decisions
See exactly what the
reviewer authorized.
The decision remains linked to its proposal, evidence, reviewer, authority and conditions as the workflow waits, resumes and proceeds to later actions.
Frozion connects the review experience, policy-required assurance and downstream execution so the approval can be checked where its consequence occurs.
The review package
Review the proposed change with
its evidence and consequences.
Use App Builder to present the current record, exact proposed change, supporting documents, eligible context, calculated Feature Store facts, model results, uncertainty, policy obligations and prior decisions.
The reviewer sees the evidence and actions permitted for their role, the external operation approval would allow, and any conditions still outstanding.
Explore review applications in App BuilderSupplier account change
- Supplier
- SUP-204 · Tenant A
- Proposed change
- Replace the account ending 1842 with the verified proposal ending 6729
- Why review?
- 2 recorded account changes in 30 days · fact definition v3
- Decision context
- Eligible supplier evidence, verification results and policy v4
- Permitted consequence
- One account update, subject to confirmation and current checks
01
Scope the human task
Identify who may decide for this tenant, resource, purpose and operation. A reviewer role alone does not grant authority over every case.
02
Require the right assurance
Use integrated FIDO2 step-up reauthentication where policy requires fresh assurance for the consequential decision.
03
Bind the decision
Associate the exact proposal, evidence, reviewer, authority, assurance, policy, time and permitted transition with the recorded outcome.
Approval continuity + material change
Carry valid decisions forward.
Revisit the ones that no
longer apply.
While the workflow waits, the account, amount, supplier, evidence, risk classification, policy or resource state can change. Reviewer authority can also expire.
A Material Change Gate compares the current proposition with the one approved. Depending on the change and applicable policy, preserve the approval, revalidate conditions, request more evidence or invalidate it and seek a new decision.
Explore policy obligations and enforcement
MATERIAL CHANGE · EXAMPLE
ApprovedP-8472 / revision 2Account ending 6729
Proposed nowP-8472 / revision 3Account ending 9051
Reapproval required in this example. The earlier decision does not authorize the changed account. The protected update remains unattempted.
03 / Governed recovery
A timeout leaves a question.
Resolve it before retrying.
An external system might reject a request, still be processing it, or complete the action while its response is lost. Keep an uncertain outcome explicit.
Connect recovery to the intended business operation, current authority, destination evidence and the next eligible action.
OP-204 · ONE INTENDED UPDATE
Attempt 1 times out.
The effect is ambiguous. No automatic assumption of failure.
Reconciliation required
DESTINATION CONFIRMS IT APPLIED
Retain the receipt. Stop further writes.
Connect the confirmed account revision to OP-204. The business outcome is established.
DESTINATION CONFIRMS IT DID NOT APPLY
Revalidate. A retry may become eligible.
Check the same intention, current authority and approval before another attempt.
THE OUTCOME IS STILL UNCERTAIN
Keep the ambiguity visible.
Continue the configured investigation or escalation path without blindly repeating the effect.
Business Operation Identity
One business intention.
Explicit technical attempts.
Business Operation Identity represents the intended action across its attempts. A timeout and a later retry do not by themselves authorize a second business operation.
Use destination idempotency support where available. Reconcile with receipts, resource revisions, correlated events, ledger entries or authoritative external status. The destination's capabilities determine which evidence can establish the effect.
Durability does not establish exactly-once effects across arbitrary external systems. Model their guarantees and uncertainty explicitly.
OPERATION RECORD
OP-204 · update one supplier account
- Authorized intention
- SUP-204 → account ending 6729 under proposal revision 2
- Write attempt A1
- Sent · response timed out · outcome ambiguous
- Reconciliation
- Destination account revision 18 confirms the intended change
- Further write attempts
- None · confirmed operation is not repeated
- Effect receipt
- Resource revision 18 linked to OP-204
EXPLICIT EFFECT STATE
See what is known about the action.
These states describe different facts; they are not an automatic sequence that every operation follows.
- Not attempted
- No external attempt yet
- Attempted
- A request was issued
- Ambiguous
- The effect is not yet established
- Confirmed
- Authoritative outcome evidence exists
- Failed
- Failure is established
- Reconciled
- Destination evidence resolved the uncertainty
- Compensated
- A governed corrective action has completed
At the effect boundary
Recheck before changing
the outside world.
Verify the approved proposal, Human Approval State, current actor or delegation, policy, resource state, effect status and Business Operation Identity before a consequential action proceeds.
Successful delivery alone does not establish that the business action completed. Inspect the authoritative destination evidence linked to the operation in its Effect Receipt.
When an effect must be corrected
Make compensation
an authorized business action.
A committed payment, order or entitlement may require an explicit reversal or correction. That action needs its own authority, policy, operation identity, evidence and outcome.
Model the recovery the business system supports. Retain the original effect and the corrective action in the execution history.
04 / Operate and evolve
Know why the work is waiting.
Explain how it finished.
Inspect the execution as a business process: its current state, expected event, active authority, policy obligations, human decisions, attempts and effect status.
Connect each transition to its evidence under the viewer's permission scope, in the context of the end-to-end execution graph.
INSPECTABLE EXECUTION · COMPLETED PATH
EX-041 / one connected history
01 / PROPOSITIONWhat was requested?
Proposal revision 2, eligible context, Feature Store facts and policy v4.
02 / HUMAN DECISIONWhat did the person authorize?
Exact proposal, reviewer authority, FIDO2 assurance, decision and conditions.
03 / CONTINUATIONWhy could the process resume?
Matching confirmation event, valid wait and revalidated approval and authority.
04 / OUTCOMEWhat happened outside Frozion?
OP-204, one timed-out write attempt, reconciliation and the confirmed effect receipt.
Versioned execution
Ship improvements.
Keep active work interpretable.
A new graph, mapping, policy, model configuration or capability version must not silently change the meaning of an execution already in flight.
See the version associations needed to interpret active work. Existing executions retain their applicable behavior unless explicitly migrated; current authority and approval validity are still checked at the relevant boundaries.
APPLICATION v7Execution EX-041 begins
Its active state remains associated with the definitions needed to interpret it.
APPLICATION v8 PUBLISHEDNew execution EX-042 begins under v8
Deployment does not silently migrate EX-041 or make an expired approval valid.
See the current condition
Active, waiting, blocked, ambiguous or complete—with the latest transition and expected next event.
Inspect the reason
Follow the proposal, policy, approval, attempt and evidence associated with that state.
Govern the next step
Use the configured recovery or escalation path with current authority and an auditable outcome.
One connected application model
Bring execution, decisions
and effects together.
Durable workflow systems can preserve process progress and implement rich recovery through application code. Frozion brings proposal binding, policy obligations, human assurance and effect evidence into the governed application model.
Keep existing queues and event brokers that start or resume the workflow through defined integrations. Identity providers, business systems and telemetry retain their roles.
Before the workflow goes live
Questions teams ask.
Yes. Invoke a workflow through MCP or HTTPS. The workflow retains its own state, contracts, authority checks, human decisions and evidence while the caller keeps its existing framework.
No. Durable Wait State is associated with the Execution
Instance. The original request, browser, process or node
can end while the work waits. A qualifying event or human
decision can allow continuation on an eligible runtime
node under the applicable resume checks.
Compare the active proposition with the approval binding.
A material change can invalidate the prior decision,
require new evidence or trigger reapproval. Approval
continuity preserves decisions that remain applicable
while preventing an earlier approval from silently
authorizing a different action.
Policy can require fresh assurance at a consequential
human decision. The recorded approval stays associated
with the reviewer, current authority, assurance, exact
proposal, policy, time and validity conditions. FIDO2
assurance complements authorization and proposal checks.
No, not blindly. A write may have happened despite the missing response. The configured recovery path reconciles the authoritative destination state, then checks whether a retry is eligible under the same business intention, current authority and approval.
Keep each execution associated with the application
semantics required to interpret its active state. New
executions can start under the new version; existing work
is not silently migrated. Explicit migration is a separate
operation, and current authority and approval validity
still matter when consequential work resumes.
Existing event infrastructure, appropriate human task
systems, IdP/IAM, ERP or CRM applications, telemetry and
audit systems can remain. Frozion connects their supported
interactions to execution identity, proposal, authority,
human decisions and effect evidence. The integration
contract defines each system's responsibilities.
Bring one workflow that waits, decides or changes the outside
world
Keep the work moving.
Keep its authority connected.
We'll map the human decisions, resume conditions
and recovery paths your consequential process needs.