Read The Rules

This skill creates an incident report by mapping the event to a ledger item, reading the relevant rule set, identifying violated or missing rules, and proposing the smallest durable prevention patch to prevent recurrence.

The best way to identify missing or ambiguous rules during an incident review is to run a structured workflow that reads the smallest relevant rule set, surfaces prior resolutions, and flags the specific governance rules that were violated or lack clarity.

You can track incident reports for audit and governance compliance by mapping every new incident review to a ledger item and storing the durable report artifacts in a repo-local location, ensuring full traceability from failure to prevention patch.

No, this incident review workflow has no external dependencies. It stores durable review artifacts directly in a repo-local location, allowing you to audit incident summaries and rule patches without needing additional external tracking tools.

You need to generate a fresh incident report document for every failure occurrence to ensure structured governance. This converts the event into durable knowledge by mapping it to a ledger item, analyzing rule violations, and defining recurrence control.