Domain Specialist playbook
Interpret layer-specific evidence and improve the guide without taking over unrelated ownership.
Primary responsibility
A domain specialist contributes depth at the point where the evidence reaches their layer. The goal is not to restart the investigation in specialist language. The goal is to interpret the committed evidence, identify the next discriminating signal, and make the supported boundary understandable to the rest of the team.
Enter with context
Review the pain statement, affected scope, healthy comparison, evidence ledger, eliminated boundaries, and current gate before requesting new data. Ask for the smallest additional evidence set that can change the decision path.
Explain confidence
State why the evidence supports or weakens a boundary, what alternative remains, and what would falsify the current interpretation. Avoid absolute claims when the data only supports a probable layer or component class.
Improve the system
After the incident, identify missing guide questions, ambiguous options, weak expected signals, unsafe command language, or ownership gaps. Submit a guide improvement that is reusable and vendor-neutral.
Expected outputs
Technical interpretation, supported fault boundary, confidence statement, next evidence request, owner route, and guide feedback.