Methodology
From field experience to a reviewable task.
Kosho’s method sets out how to qualify contributors, capture maintenance decisions, and review the evidence behind a grade.
Source and vet technicians
A machine-specific assessment asks a technician to reconstruct a repair and explain the evidence behind it. Reviewers distinguish self-reported experience, supporting documents, and knowledge demonstrated in the interview.
Build the environment
Authors specify the information available at each step. A request for an inspection reveals only what that inspection could show. State transitions capture prerequisites, operational constraints, and the consequences of acting too early.
Capture expert reasoning
A technician works through the scenario with the information available at that moment. The record pairs each decision with its rationale, plausible alternatives, and evidence that could change the technician’s mind.
Validate and refine
A domain review checks the fault against the symptoms and tests the rubric against more than one defensible path. An ambiguous finding or disputed grade goes back to the scenario author for revision and replay.
Quality assurance
Review the disagreement.
Two technicians may choose different first tests for good reasons. A reviewer examines the assumptions behind each choice, including the cost of stopping the line and the availability of a reliable baseline.
If both paths fit the stated conditions, the rubric should credit both. If an assumption is missing, the scenario needs a clearer observation or operating constraint before it can support a reliable comparison.
Research inquiries
Build better physical-world intelligence.
Explore expert-informed maintenance environments and evaluation data for your model-training needs.