Today’s rule replaces yesterday’s reason
The policy has changed since the action. Looking only at the current definition cannot explain which condition governed the original decision.
Benefit / Trust & Control
Every governed decision
carries its own evidence.
When someone asks why an AI-assisted action happened, the answer should already be connected to the work. Frozion records the authority, rules, facts, decisions and reported effects as the process runs.
Capture it with the work. Keep the versions. Check coverage and integrity.
FROZIONExecution FabricGoverned from request to outcome
- The decision at the time
Policy v4, fact definition v3 and the reviewed proposal stay connected.
- The action and its result
The attempted payment is distinct from the ERP’s confirmation.
- The evidence you can inspect
Required items, retained references and integrity checks are visible.
An explanation grounded in the recorded case, not the current configuration.
01 / The challenge
The audit request arrives.
The reconstruction begins.
A business decision can depend on a policy, a calculated fact, a human approval and an external system’s response. Separate logs rarely explain how those pieces belonged together at that moment.
Approval lacks its proposal
A person clicked approve, but the exact revision and the facts they saw are scattered across other systems. The click alone does not establish what was authorized.
A trace looks more complete than it is
A tool call was attempted, a source reference exists or a check passed. None of those, on its own, proves the action completed or the original evidence is still available.
02 / How it works
Eight questions.
One connected decision record.
Define the evidence the process requires, then capture and connect it as governed work proceeds. The record makes both supported conclusions and unresolved gaps inspectable.
Who acted
The agent and the initiating person or application identity, connected to the case.
Under what authority
The role, tenant, delegated scope and business purpose relevant to the decision.
Which rule applied
The policy and workflow versions used, with the condition and resulting obligation.
Which facts were used
The values, source references, definition versions and freshness information required by the decision.
What was proposed
The exact proposal revision and the agent’s contribution to it.
Who approved, when required
The authorized reviewer, the proposal revision and any assurance required by the policy.
What happened
The attempt, the destination’s response and the reported outcome. An uncertain external effect remains unresolved.
What supports the record
Integrity evidence and required-item coverage, with retained payloads distinguished from references.
03 / In practice
A March payment.
An October question.
An investigator reviews why a $41,200 payment was released months earlier. The current policy is v6; the record shows that the decision used v4.
Payment PAY-3318 · sample data
Follow the historical rule, facts, approval and outcome, then check what evidence is actually available.
Historical definition
Inspect the rule used then.
The investigation starts from the policy version attached to the March decision. The current v6 definition can be inspected separately; it does not replace the historical explanation.
Decision context
- Payment
- $41,200
- Decision date
- March 14
- Review date
- October 28
- Policy used
- Supplier payment controls · v4
- Current policy
- v6 · separate definition
Values used in the decision
Follow the facts back to their sources.
The payment used a verified supplier status and a zero-variance fact. The case retains the fact definition and the source references required by its evidence contract. A reference identifies the source; access to that source remains a separate question.
Business inputs
- Supplier status
- Verified at the recorded check
- Invoice variance
- 0%
- Fact definition
- Invoice variance · v3
- Freshness
- Accepted by the decision’s contract
- Invoice source
- Original PDF referenced in ERP
Proposal revision 2
See exactly what finance approved.
The finance manager’s decision is attached to proposal revision 2. The record includes the assurance required by policy and the pre-action checks that allowed this proposal to proceed.
Approval evidence
- Reviewer
- Authorized finance manager
- Proposal
- Revision 2 · $41,200
- Required assurance
- FIDO2 step-up recorded
- Before action
- Authority and required conditions revalidated
Attempt and reported effect
An attempt becomes a confirmed result.
Attempt A1 is linked to the ERP’s payment confirmation. This record supports the reported completed state. If the destination had timed out without confirmation, the outcome would remain unresolved instead.
Action evidence
- Attempt
- A1 · protected payment action
- Destination
- ERP payment endpoint
- Response
- Payment confirmation received
- Case state
- Confirmed
Evidence contract
Know what the record establishes.
All nine required evidence items are satisfied under this sample contract, which allows a source reference for the invoice. The original PDF remains in the ERP. Its continuing availability must be checked separately; a complete reference set is not a guarantee of retrievable source payloads.
Evidence assessment
- Contract coverage
- 9 of 9 required items satisfied
- Invoice retention
- Source reference · payload in ERP
- Source availability
- Checked separately under ERP access
- Integrity
- Tamper-evident record checks
- Meaning
- Coverage and integrity do not certify source truth
04 / Control evidence
Control evidence
without the scavenger hunt.
Use the connected record to answer specific control questions. Whether that evidence satisfies an audit depends on the control design, coverage and auditor’s requirements.
- Human oversight
- Why review was required, which proposal was reviewed and which decision was recorded.
- Access and separation of duties
- The initiating identity, delegated authority and eligible reviewer associated with the action.
- Change control
- The workflow, policy and fact-definition versions attached to the case.
- Lineage and integrity
- Source relationships, retained evidence and the integrity checks available for the record.
- Incident investigation
- The attempted operation, reported response, unresolved effects and missing evidence.
05 / By role
Answer the question.
Follow the evidence.
Give authorized teams a common record to inspect, with access boundaries appropriate to their responsibilities.
Risk & compliance
Inspect the decision against its authority, policy and evidence requirements. Identify gaps without assuming that a successful run proves a complete control.
A review grounded in the case.Internal audit
Follow historical definitions, approvals and outcomes without reconstructing their relationships from separate systems. Check references and retained payloads distinctly.
A clearer evidence trail.Operations & security
Investigate the same case after an incident or exception. Distinguish an unauthorized proposal, a held action and an uncertain destination response.
A precise starting point for investigation.06 / Scope and questions
Evidence by design.
Conclusions you can support.
Audit readiness begins with the required record and the work that produces it. Retention, permission and evidence coverage remain explicit responsibilities.
Coverage must be defined
Specify what the governed process must retain, reference and verify. Required-item checks reveal whether those configured obligations are satisfied.
The record has access boundaries
Authorized viewers can inspect the evidence available to them. Sensitive payloads and source systems keep their own access and retention constraints.
No. Frozion supplies connected execution evidence. Compliance depends on your applicable obligations, control design, deployment and operating practices.
The decision remains associated with the versions used at the time. An investigator can distinguish that historical definition from the current one.
No. A reference identifies the source. Payload retention, availability and permission to retrieve it must be established separately according to the evidence contract and source system.
Yes. Coverage and integrity checks do not establish that an external source was accurate. Source quality, validation and the decision’s input requirements remain essential.
Start with one business process
Bring the question
your auditor will ask.
We’ll trace one governed decision from its authority and source facts to the approval, action and evidence required to explain it.