gsd-forensics

Workflow debugging identifies root causes of failed orchestration runs by analyzing git history, planning artifacts, and filesystem state to reconstruct events and detect anomalies. It reviews diffs and status to determine why execution stalled or crashed.

Post-mortem forensics investigates stalled or crashed automation workflows by examining planning artifacts and git history for missing files or interrupted execution. It classifies anomalies and generates evidence-backed reports to guide corrective actions.

Anomaly detection scans git history and filesystem state to identify stuck loops, missing artifacts, abandoned work, and crash patterns. It checks planning artifacts to classify workflow inconsistencies and interruption points for forensic reporting.

Yes, you can generate a forensic report from planning artifacts after a crashed orchestration run. The analysis produces structured findings, recommendations, and optional escalation paths written as redacted output to the .planning/forensics/ directory.

No dependencies are required to analyze filesystem state and git history for workflow debugging. The investigation relies on existing planning artifacts, git diffs, and filesystem metadata to reconstruct failed orchestration runs and classify anomalies.

The best way to investigate inconsistent state after an interrupted workflow is evidence-backed forensics that examines git history, planning artifacts, and filesystem conditions. This approach distinguishes missing files from interrupted execution to identify the root cause.