Capture

The orchestrator routed you here. This atom owns the full recording lifecycle: launch a target, execute an interaction script, collect raw outputs.

You should already have a driver atom loaded (terminal-use, true-input, browser-use, or desktop-use) and optionally a target atom (droid-cli). This atom layers the recording discipline on top.

Inputs

The command that invoked you should have provided:

• Target: what to launch and on which branch(es)
• Interaction script: the sequence of actions to perform
• What to capture: recordings (.cast/.mp4), screenshots, text snapshots, byte sequences
• Keystroke logging: whether to emit a keystroke TSV for later overlay

Recording lifecycle

For desktop-use, follow its recording contract; do not translate the terminal commands below into desktop commands. Routine desktop snapshots stay in the driver's observe/act/verify loop.