# AGENTS.md

Scope: this file applies to the `2025-692ft_Fault_Tolerance` folder.

## Folder Purpose

This is a flat 2025 fault-tolerance course or seminar recording archive. It is not currently a reveal.js deck or source tree. At the time this file was written, it contains MP4 recordings only, with no immediate subfolders and no `index.html` or `presentation.html`.

The filenames encode the session order, topic, recording part, and notes about carryover or recording issues. Treat those filenames as the archive's main metadata.

## Content Inventory

The folder contains 10 MP4 files organized as five numbered sessions, each split into `-s1` and `-s2` parts:

- `1-game_of_surface_codes-s1.mp4` and `1-game_of_surface_codes-s2.mp4`.
- `2-latice_surgery_with_a_twist_(after a bad recording in the first half)-s1.mp4` and matching `-s2`.
- `3-pauli_based_measurement_(after finishing the presentation from last time)-s1.mp4` and matching `-s2`.
- `4-punching_holes_in_surface_code_(after finishing the presentation from last time)-s1.mp4` and matching `-s2`.
- `5-color_codes_surgery_(after finishing the presentation from last time)-s1.mp4` and matching `-s2`.

The spelling `latice` appears in existing filenames. Preserve it unless performing a deliberate migration of all dependent references.

## Content Themes

The sequence focuses on quantum fault tolerance and topological/error-correcting-code workflows. Topics inferred from filenames include:

- Surface-code intuition via a game or interactive framing.
- Lattice surgery with twists.
- Pauli-based measurement.
- Hole-punching or defect-based surface-code operations.
- Color codes and surgery.

Several filenames note that recordings continue or finish material from a previous presentation. Keep that context visible in any generated summaries or playlists.

## Editing And Organization Guidance

- Keep `-s1` and `-s2` files paired. If one part is moved, captioned, summarized, or checksummed, do the same bookkeeping for the other part.
- Preserve the leading session number and part suffix. Do not renumber existing sessions.
- Preserve parenthetical recording notes such as `(after a bad recording in the first half)` and `(after finishing the presentation from last time)`.
- If adding transcripts, captions, thumbnails, notes, or checksums, use the exact MP4 stem, for example `3-pauli_based_measurement_(after finishing the presentation from last time)-s1.vtt`.
- Do not rename files just to normalize spelling, underscores, spaces, or punctuation. These names encode the current archival state.
- If future source decks or `presentation.html` files are added, document how each recording part maps to the source material and inspect HTML decks with `tools/reveal_text.py` from the repository root.