Action review

Review what agents did when the reports disagree.

Action Review gathers every report about one agent-driven operation, flags the exceptions that need a person, and keeps a record of what the reviewer decided and why.

Conflicting reportsUnknown outcomesUnsupported approvalsExportable case
How a case forms

Separate reports in. One reviewable case out.

Agents, companies, gateways and payment providers each report on the same operation from their own side. Action Review lines those reports up, checks them against six rules, and puts the exceptions in front of a person.

01 · Sources report
Separate systems, separate claims
  • agentproposed, confirmed
  • companysucceeded, failed
  • gatewayallowed, denied
  • paymentauthorized, captured
02 · Correlate
One operation, every report
operation_refacme:workflow-88

Each report keeps its issuer, basis and timestamp. Nothing is merged or overwritten.

03 · Check
Six exception rules
  1. 01reported failure
  2. 02conflicting outcomes
  3. 03gateway vs result
  4. 04unsupported approval
  5. 05unknown outcome
  6. 06amount disagreement
04 · Decide
A case a person resolves
openin reviewresolved

Every status change carries the reviewer's reason in the activity trail.

05 · Hand off
Export what was found
case report (JSON)unsigned, source-attributed
evidence casesigned records, when required
One exception, step by step

The gateway said no. The company said done.

Neither report is wrong on its own. Together they are a question someone has to answer, and the case keeps both reports side by side until they do.

Try it

Work a queue of synthetic cases.

Filter the queue, open a case, add a simulated report and watch the rules re-run, then record a decision and export the case. Everything stays in your browser; the export is unsigned.

Operations
7
Synthetic operation references
Open exceptions
5
Need attention
In review
0
Being investigated
Critical
2
Conflicting high-impact reports
Operation cases
Ordered by severity, then newest activity
7 of 7
All figures are source-reported
Case inspection
acme:workflow-97
criticalopen
Findings · 1
Contradictory final-state reportscritical

The records contain incompatible final states: cancelled, succeeded. Investigate issuers and chronology.

events: wf97-cancel, wf97-success
Source observations · 2

None of these assertions is cryptographically verified here. Local hashes are not issuer signatures.

  1. agent · upstream report10-09 15:31 UTC
    operation · cancelled
    Agent reported the order cancelled
    issuer agent.demo.invalid · sha256 computing
  2. company · upstream report10-09 15:34 UTC
    operation · succeeded
    Fulfilment service reported the order shipped
    issuer company.demo.invalid · sha256 computing
Simulate an incoming report
Case disposition
Activity trail

No operator activity recorded.

Exception rules

Six deterministic checks, each stated as a report.

Every finding names the events it came from. The rules describe what sources said; they do not decide what happened.

critical
Conflicting outcomes

Sources reported incompatible final states for one operation, such as cancelled and succeeded.

critical
Gateway and result discrepancy

A gateway reported denial while another source reported successful execution.

high
Reported failure

A source reported the operation failed. Treated as a report, not a verified business outcome.

high
Unknown outcome

The last report was in progress more than 30 minutes ago. A timeout is not read as failure.

medium
Unsupported approval

An agent or company asserted user approval without an independent approval artifact.

medium
Amount disagreement

Sources reported different amounts in the same currency for one operation.

Verification boundary

Reported is not the same as verified.

Action Review works from what each system says it saw. When a case has to travel to another party, signed records and an evidence case carry the parts that can be checked.

What verification establishes

Verification checks the record's structure, signature, issuer information, and bound digests against the supplied verification material.

What verification does not establish

Verification does not independently prove that every relevant real-world event was captured, that the issuer's statements were truthful, or that an underlying system correctly enforced its policy.

Bring one workflow where the reports do not line up.

We will map its sources, run the rules on real reports, and show you the cases that need a decision.