neb-constructive-analysis

Blame-free root cause analysis is automated by feeding incident artifacts like logs and code history into a six-phase investigative pipeline that produces structured, evidence-backed findings without assigning blame.

Code review findings are structured using the Observation, Context, Recommendation (OCR) format, ensuring every claim is evidence-backed and contextualized before delivery.

Incident investigation depth is calibrated during the drafting phase by selecting Quick Triage, Standard, or Deep Root Cause Analysis levels based on the complexity of the available artifacts.

Prior memory and references can be integrated into a system assessment by loading supplementary context from the references directory to enrich the investigative findings.

The constructive analysis workflow enforces a mandatory verification step during the Tone-Check and Deliver phases to ensure all claims are validated and constructively phrased before final output.

To start an evidence-backed investigation, you need to gather incident artifacts such as application logs, system configurations, and code history to feed into the initial analysis phase.