Damage and Repair Triage Guide¶
Specification¶
The full specification below is extracted from Chapter 19: Budgeting, Sourcing, and Classroom Logistics.
Type: mermaid-diagram
**sim-id:** damage-repair-triage-guide<br/>
**Library:** Mermaid<br/>
**Status:** Specified
Learning objective: Students will *apply* (Bloom L3: Apply) a damage-and-repair triage process to decide whether a damaged component should be repaired, replaced from spares, or removed from the kit rotation.
Canvas: responsive Mermaid flowchart rendered at container width, using Mermaid's default responsive SVG scaling.
Layout: a top-down Mermaid flowchart starting at "Component reported damaged," branching to "Is it safe to power on?" — No leads to "Remove from service immediately, tag for review"; Yes leads to "Is a spare in the shared bin?" which splits into "Yes: swap immediately, log old unit for repair" and "No: is it repairable with basic tools?" which splits again into "Yes: repair and return to inventory" and "No: retire and add to next order's BOM."
Interaction: every node has a `click` directive opening a short definition/tip in an infobox beneath the diagram — for example, clicking "Is it safe to power on?" shows a one-sentence electrical-safety reminder tied to the Electrical Safety concept defined later in this chapter, and clicking "Remove from service immediately" shows a reminder to log the incident on the kit checklist. A "Reset" link below the diagram clears any open infobox.
Implementation: Mermaid `flowchart TD` syntax with a `click NodeId "javascript:showInfobox('NodeId')"` directive on every node, paired with a small JavaScript object mapping node IDs to infobox text, satisfying the requirement that every node in a Mermaid diagram be interactive rather than a static image.