
ENGINEERING
The audit trail that writes itself
JUN 6, 2026 · BY THE TURBINE TEAM
Ask any ops team where their process documentation lives and you will get a laugh, a wiki link last touched in March, or both. Documentation as a separate act always loses to the queue.
Turbine inverts it: the log is the execution. Every run records its inputs, its plan, every tool call with request and response, every check, every approval — as it happens, because that record is how the run happens.
If documenting the work is separate work, it will eventually not be done.
Replay makes the log useful to humans. A reviewer steps through a completed run read-only: what did it know, what did it do, what did it verify. Auditors stop asking for screenshots when they can watch the work.
Retention follows your policy, in your region, exportable to your SIEM. Access to the log is itself logged — turtles all the way down, on purpose.
We did not set out to build a compliance feature. We set out to make done provable, and the audit trail fell out of that decision.