Lecture Note

3. Create a lightly cleaned transcript.

• Remove or normalize obvious STT noise such as inaudible-type fragments, repeated filler bursts, and accidental repeated characters.
• Keep edits loose and minimal; preserve wording/order whenever possible.

4. Create the structured lecture note from the cleaned transcript.

• Fill all template sections.
• Keep core terminology and emphasized points explicit.

5. Build merged output and save.

• Compose one Markdown file as:
  • Structured note
  • ---
  • Cleaned transcript
• Save in the same directory as the transcript.
• Filename must use local KST date: YYMMDD.md.
• If filename exists, use YYMMDD (2).md, then (3), etc.

Output Contract

• Summary: what was cleaned and how the note was structured
• Artifact: exact saved file path
• Validation: whether collision numbering was used
• Follow-up: only if a specific ambiguous section needs user confirmation

Resource Routing

• Work instructions: references/work-instructions.md
• Note template: references/lecture-note-template.md

Guardrails

• Process one transcript file per invocation only.
• Do not over-edit transcript content; prefer minimal correction.
• Do not omit explicit uncertainty; keep unclear parts visible in note sections.
• Always output a single merged Markdown file.