Relecture

Là où se revoient les sessions enregistrées : chaque ligne est une session, à qui elle appartient, quand elle a été enregistrée et ce qu'elle contient. La sélection ouvre le lecteur ; un enregistrement masqué se dit masqué, une absence ne se lit donc jamais comme une panne.

The sessions

Every recorded session the project holds: who it belongs to, when it was recorded, how long it runs and how many chunks it spans. The search narrows by the person the session belongs to, and a session recorded with masking on wears a masked chip, in the list and again beside the player, because what the recording deliberately does not show should never read as breakage.

The player

Selecting a session opens the player beside its metadata: play and pause, previous and next, speed, a timeline to scrub and the session identifier naming whose recording it is. The recording streams in chunks fetched on demand through short-lived links; a link that has expired says so and offers a reload rather than failing quietly.

Three arrangements

Session grid, Theater and Review queue are three arrangements of the same list and player: the grid is the flat table, Theater puts the list beside a large stage, and the Review queue walks sessions one after another and says where in the review you are. The choice is a stored preference per person, set here or on the Preferences screen under Layouts.

Where this meets the API

The concept behind the screen is the Replay pillar. On the wire: the list is the replaySessions query and playback is replayChunks, whose chunk links are short-lived by design (GraphQL reference). Recordings arrive from the SDK through the recorder edge alongside event ingestion.