postmortem

To generate a postmortem, run the analysis command against completed campaigns, telemetry files, and git history to automatically extract failures, safety catches, and recommendations into a structured markdown document.

Automated incident analysis reads campaign artifacts and telemetry logs to identify what broke, what safety systems caught, and scope drift, producing a cohesive postmortem with actionable recommendations without manual reconstruction.

Yes, you can apply the retrospective analysis to ad-hoc debugging sessions or a specified time range, summarizing failures, safety catches, and scope drift even outside of formal campaign structures.

Yes, the postmortem generator includes fallbacks for missing telemetry or campaigns, ensuring it can still produce a structured markdown document with failure analyses and recommendations from available git history.

Limitations depend on the availability of campaign files and telemetry logs; while fallbacks exist for missing data, incomplete git history or sparse telemetry will reduce the accuracy of failure analysis and scope drift detection.