Label: ungraded stage case. Original fiction. Not a captured crash, scan, or challenge result.
Keep a private evidence note with source, reasoning and limits.

Piece 1. Bounds.
Buffer bin has 3 positions, indexed from 0.
Requested write: 4 bytes, and no extra terminator is requested.
The write needs more positions than bin has. Mark it as a bounds violation.

Piece 2. Mitigation.
Row on this card: the stack's model address differs across two ordinary runs.
Match that row to the role whose job is a layout that varies between runs.
The bounds violation in piece 1 remains. The match does not repair it.

Piece 3. Practice.
Assignment sentence: You may study the single file crate on the assigned Linux x86-64 host.
The status dashboard is not in that sentence.
In-scope file: crate.
Stop condition: stop when the next step is the status dashboard, another file, or a change to a host setting.

Rubric, for your own note. The site does not grade the note.
- Piece 1 says the 4-byte write does not fit in 3 positions.
- Piece 2 names the layout that varies between runs, and still calls the write wrong.
- Piece 3 keeps crate and leaves the status dashboard out.
- The note does not claim a program was run, a mitigation was changed, or a flag was found.