Automation Acceptance Replay Harness
Replay automation traces against explicit rules for required steps, order, retries, approvals, idempotency, external side effects, duration, and terminal success.
What problem does Automation Acceptance Replay Harness solve?
An automation can end on a green node while a required step failed, an email or write happened twice, an external action lacked idempotency, a gated action skipped human approval, or the execution log cannot support client acceptance.
Use it to
- Replay production-like executions before approving an automation release
- Catch duplicate emails, writes, charges, or other side effects across retries
- Verify configured human approval occurs before a gated action
- Create a portable client acceptance record after workflow changes
What it returns
- Severity-ranked findings CSV for each execution
- Execution summary CSV with ACCEPT, REVIEW, or REJECT disposition
- JSON acceptance recommendation and severity totals
- Markdown handoff tied to the exact contract and supplied trace
A representative input and result
Access and approval boundaries
- Read access to a user-supplied JSON contract and CSV execution trace.
- Write access only to the selected local audit output directory.
- No workflow platform, connector, browser, email, CRM, payment, or network access is required.
Known limitations
- The result is limited to events represented in the supplied trace; missing logging can resemble missing execution.
- A clean fixture does not prove that every input, connector failure, race condition, or replay scenario is covered.
- External provider state must be checked separately when acceptance depends on whether an email, write, charge, or deletion actually occurred.
Questions
Does it execute or replay my live workflow?
No. It replays the logic of acceptance checks over an exported trace. It does not call connectors or change external systems.
Which automation platforms work?
Any platform can work after its execution records are mapped to the documented CSV fields, including n8n, Zapier, Make, agent frameworks, and custom systems.
How does it detect a duplicate side effect?
It flags more than one successful allowed side effect sharing a side-effect key or idempotency key inside an execution trace.
How is human approval represented?
A gated action must be preceded by an event with event_type human_review and status approved in the same execution.
Does ACCEPT prove the workflow is correct?
No. ACCEPT means the supplied executions cleared the declared contract. Coverage, log completeness, semantic output quality, and external state remain separate questions.
Does it need my n8n or Zapier credentials?
No. The helper runs locally on exported files and requires no platform, connector, browser, or network access.
Automation Acceptance Replay Harness keeps proof and approval boundaries visible.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get Automation Acceptance Replay Harness on Agensi