Writing investigation notes that travel
Screenshots without a spine force the next reader to rebuild your thinking. In mixed-language teams, that rebuild happens twice.
Use a fixed spine
- Signal that fired and why it matters.
- Evidence reviewed (IDs, not only file names).
- Alternate explanations considered.
- Conclusion and residual risk.
- Follow-up owner and date.
Add a short local summary
Keep the evidence spine in English if that is your audit language of record. Add a brief Korean summary block for plant controllers. Do not maintain two contradictory narratives.
Avoid vanity length
Long notes are not safer notes. Clarity is. Module 4 of Ledger Signal Studio drills this under a time box.