Humanities & PolicyOperations & AdminReleased 7 Oct 2026
Generates a troubleshooting document as one labeled block per problem, each carrying five explicit fields - symptom, probable cause, diagnostic, fix, and verification. Renders entries as label-to-value blocks rather than as a wide table, so no field is ever separated from its heading. Tags every claim with its epistemic status (FACT with file and line, DOC, or HYPOTHESIS) and never invents failure behavior that was not read in the code, in a log, or in a ticket. Use when a repository, runbook, or support thread needs a troubleshooting section, when recurring failures must be written down for an operator working under time pressure, or when an existing troubleshooting tabl…