gsd-forensics

To diagnose a stalled workflow crash or missing artifacts, you trace root causes by correlating git history, planning files, and filesystem state. This forensic analysis identifies stuck loops, abandoned work, and interruption patterns to explain what changed and when.

The best way to investigate abandoned progress in get-shit-done workflows is through evidence-backed anomaly detection. This process examines session reports and planning artifacts to identify exactly where and why the workflow drifted off course.

You trace the root cause of missing planning artifacts by performing a forensic review of git history and filesystem state. This method correlates commit changes with session state to pinpoint when artifacts were lost or abandoned.

Yes, forensic analysis preserves read-only source files while producing a structured diagnosis. It examines existing filesystem state and session reports to generate actionable recovery recommendations without modifying the original evidence.

Yes, workflow forensics works for triaging interrupted GSD sessions by examining session reports for crash patterns. It correlates this evidence with git history to produce a redacted report detailing anomalies and next-step recommendations for escalation.

A structured forensic diagnosis for a failed GSD workflow run should include identified anomalies, evidence-backed findings, and next-step recommendations. It correlates git history and filesystem state to summarize the most likely root cause for recovery.