Skip to content

Platform

Run history and audit

What is recorded per run, retention, and exporting for audit.

Every run produces an append-only record. It is the artefact that makes automation defensible, so it is deliberately detailed.

What is recorded

  • The trigger, its payload, and the identity that caused it.
  • The workflow version that executed.
  • The resolved tenant, environment and asset scope.
  • Each step's inputs, outputs, duration and status.
  • Every branch decision and the condition values behind it.
  • Interpretation output, including the intent and confidence score where applicable.
  • Every approval: who was asked, who decided, when, and what they were shown.
  • The verification assertion and its result.

What is not recorded

Resolved credential values are never written to run history. Where a step's output would contain a secret, it is redacted at capture time rather than at display time.

Retention and export

Retention is configurable by plan, and records are exportable for external audit and reporting. Reports your team needs regularly — backup reconciliation, patch campaign results, per-tenant operations summaries — are generated from this same data rather than assembled separately.

Scope of this documentation

This page describes how the StackHeal platform is designed to behave. This website does not execute workflows or connect to infrastructure — see the repository README for the backend integration points.