cs

Trace customer-reported issues from the affected screen or URL through Controller, Service, Mapper, and SQL layers to narrow down root-causes. This outside-in method ranks potential causes for functional bugs, data inconsistencies, and permission failures with concrete verification steps.

Triage incidents using an urgency-aware workflow that separates immediate workarounds from structural root-fix recommendations. Rank potential causes by probability and impact to prioritize engineering communication and address high-severity functional bugs first.

Generate customer-facing support messages by enforcing guardrails that avoid disclosing internal paths, tables, or constants. Produce polite, non-technical explanations while maintaining strict separation between internal SQL verification and customer-facing text.

Yes, selectively read internal documentation like CLAUDE.md, biz-rules, module docs, and DDL to verify SQL queries and improve root-cause analysis accuracy. Leverage these documents to validate data inconsistencies, integration issues, and refine diagnostic hypotheses.

Yes, root-cause analysis applies to performance problems and integration issues alongside functional bugs and permission failures. Map symptoms across controller, service, mapper, and SQL layers to identify responsible code paths for these diverse failure cases.