{"@":{"v":"gdom/1.2","profile":"https://dng.ai/gibberdom/gdom-1.2.json","proj":"text","index":"https://dng.ai/_gdom/manifest.json","site":"https://dng.ai/_gdom/site.gdom","self":"https://dng.ai/_gdom/platform/audit-trail/index.text.gdom"},"text":"# Every run, logged for governance.\n\nEach workflow run is recorded end to end — completed and failed steps, per-step state, timestamps, inputs, and outputs. Human approvals are captured in the trail, so you can prove what happened and why.\n\n## Who did what, when, and why.\n\n### Enterprise-ready\n\nBuilt for scale, governance, and reliability.\n\n### Composable\n\nWorks with the rest of the agentic platform out of the box.\n\n### Observable\n\nEvery run is logged, retrievable, and auditable via the Workflow Runs API.\n\n### Traceable\n\nPer-step state and timestamps show exactly what ran, when, and how it ended.\n\n### Accountable\n\nHuman-in-the-Loop approvals are recorded as part of the run.\n\n### Exportable\n\nRetrieve any run by ID; step outputs are downloadable where available.\n\n## Every run is a complete, retrievable record.\n\nWhen a workflow runs, the platform logs the run with its inputs, overall state, and start and end timestamps. Retrieve any run by ID through the Workflow Runs API to monitor progress or reconstruct exactly what happened.\n\n## Steps, states, timestamps, and approvals.\n\nEach run separates completed_steps from failed_steps. Every step carries its own state and timing, so nothing about an execution is left implicit.\n\n## Failures and aborts are first-class, not silent.\n\nCompleted steps record their output; failed or aborted steps record state and an error message. A user-intentional stop is marked USER_ABORTED so you can filter it apart from a genuine FAILED — clean signal for monitoring dashboards.\n\n## Governance you can hand to an auditor.\n\n### Prove what ran\n\nReconstruct any execution from its logged inputs, steps, and outputs.\n\n### Accountable approvals\n\nHuman-in-the-Loop checkpoints record who approved what before it proceeded.\n\n### Monitor at scale\n\nPoll runs by ID to track progress and catch failures as they happen.\n\n### Distinguish intent\n\nUSER_ABORTED vs FAILED tells deliberate stops apart from real errors.\n\n## A governed publishing pipeline, fully logged.\n\nThe run logs each step's state and timestamps; the Human-in-the-Loop approval is recorded before publish, so the trail proves a person signed off.\n\n## How every run becomes evidence.\n\n### Configure\n\nBuild it visually in Studio and add a Human-in-the-Loop checkpoint where sign-off matters.\n\n### Run\n\nTrigger the workflow; it executes asynchronously while each step is logged with state and timestamps.\n\n### Approve\n\nThe run pauses at the checkpoint until a reviewer approves — and that approval is recorded.\n\n### Audit\n\nRetrieve the run by ID to review completed and failed steps, inputs, and outputs.\n\n## What teams ask before they commit.\n\nAn audit trail is the complete, retrievable record of what an automated workflow did: which steps ran, in what state, when, with which inputs and outputs, and who approved what. In Draft & Goal, every workflow run is logged end to end so teams can prove what happened and why.\n\nEach run records its inputs, overall state, and start and end timestamps, and separates completed steps from failed ones. Every step carries its own state and timing, completed steps record their output, and failed or aborted steps record a state and an error message, so nothing about an execution stays implicit.\n\nYes. Any run can be retrieved by ID through the Draft & Goal Workflow Runs API, returning the run record with its inputs, state, timestamps, and completed and failed steps. Step outputs are downloadable where available, so you can reconstruct exactly what an execution did and hand the evidence to an auditor.\n\nYes. When a Draft & Goal workflow reaches a Human-in-the-Loop checkpoint, the run pauses until a reviewer approves, and that approval is recorded as part of the run. For a governed publishing pipeline, the trail proves a person signed off on the copy before anything was published.\n\nA user-intentional stop is marked USER_ABORTED, while a genuine error is marked FAILED with its error message preserved in the run record. That distinction gives monitoring dashboards a clean signal, so teams can track true failures at scale without deliberate aborts polluting the data.\n\nShow us the workflow.We'll show you the 10x.\n\nBring the marketing workflow that eats your week. We'll build it live, with your data and your models, in 30 minutes.\n\n## Outbound links\n\n- [Book a demo →](https://dng.ai/book-demo/)\n\n- [Tour the platform](https://dng.ai/platform/)\n\n- [Draft & Goal](https://dng.ai/)\n\n- [Read the docs](https://docs.dng.ai/)\n\nSite navigation: https://dng.ai/_gdom/site.gdom\n\nFull page index: https://dng.ai/_gdom/manifest.json","links":[{"rel":"internal","href":"https://dng.ai/book-demo/","path":"/book-demo","label":"Book a demo →","gdom":"/_gdom/book-demo/index.text.gdom"},{"rel":"internal","href":"https://dng.ai/platform/","path":"/platform","label":"Tour the platform","gdom":"/_gdom/platform/index.text.gdom"},{"rel":"internal","href":"https://dng.ai/","path":"/","label":"Draft & Goal","gdom":"/_gdom/index.text.gdom"},{"rel":"external","href":"https://docs.dng.ai/","label":"Read the docs"}]}