issue-record-formatter

To format SP-STM issue notes with frontmatter validation, input your existing problem note or a minimal crash description. The system enforces strict frontmatter enums and inserts standardized analytical sections to produce a validation-safe Issue Record.

Generating a complete issue record from a one-sentence tip crash description involves specifying the event, such as scanning Co/Cu(111). The system scaffolds crash-specific physical mechanisms, computes parameters, and inserts a Pre-flight Checklist before the processing section.

Creating quantifiable loss and historical statistics tables for fault notes is automated during the formatting process. The system generates these mandatory analytical modules alongside standard section layouts to reduce ambiguity during troubleshooting retrospectives.

The issue record formatter does not auto-fill the solves field for SP-STM problem notes. It actively prevents prohibited auto-filling of specific fields while enforcing required frontmatter integrity and inserting mandatory analytical sections.

A risk checklist for SP-STM tip crash failures is needed when the issue category is set to tip_crash. The system conditionally generates a Pre-flight Checklist and places it correctly before the processing section to ensure proper troubleshooting protocols.