Workflows that can prove what they did

The accountability problem in automation

Workflow engines are everywhere. Every business has automations: processes that move data between systems, trigger actions based on conditions, schedule recurring tasks. The tools are mature. n8n, Temporal, Airflow, Step Functions, Zapier, Make. They work.

What they do not do is produce evidence. When a workflow runs, it generates execution logs. Those logs record which nodes fired, what data moved through them, whether they succeeded or failed. This is useful for debugging. It is not useful for accountability.

Logs are mutable. They are unstructured. They are produced by the same system they describe, which means they can be altered without detection. When a regulator, an auditor, or a court asks "can you prove what this automation did?", execution logs are not the answer.

QuoxFlow: built for evidence

QuoxFlow is a workflow engine written in TypeScript with 429 tests. It runs workflows. It also produces cryptographically linked evidence of every execution.

• AEE envelopes on every node: Each node execution produces a structured envelope recording its inputs, outputs, timing, and the identity of the workflow that triggered it. These are not log lines. They are structured records with a defined schema, queryable and exportable.
• VOLT hash chains on every run: Envelopes are linked in a cryptographic hash chain. Each envelope references the hash of the previous one. If any record is modified, the chain breaks. Tamper detection is mathematical, not procedural.
• Human-in-the-loop approval gates: Any node can require human approval before execution continues. The approval decision is itself recorded in the evidence chain. Not a manual workaround. A first-class workflow primitive.
• Policy enforcement per node: Nodes can be scoped by policy. A data-processing node can be restricted to specific data categories. An API-calling node can be limited to specific endpoints. Policy violations are caught before execution, not after.
• n8n workflow import: Existing n8n workflows can be imported and run on QuoxFlow. The visual structure, node connections, and logic transfer. The governance layer wraps around them automatically.

Who needs this

Not everyone. If your workflows send Slack notifications and update spreadsheets, a standard automation tool is fine. Governance infrastructure is not free. It adds structure, and structure has a cost.

But if your workflows process personal data, execute financial transactions, modify production infrastructure, interact with healthcare systems, or make decisions that affect customers, the question is not whether you need accountability. It is whether you have it.

QuoxFlow is for the workflows where "it ran" is not enough. Where you need "it ran, here is exactly what it did, here is the evidence chain, and here is proof that nothing was altered." That is proof an auditor can check independently, not a log you are asking them to trust.