Status

The live operational state of the block is not kept in these docs — it lives in the files the scripts read and write, so it never goes stale.

Source of truth

• config.yaml → status — the current phase, progress, next_steps, and blockers.
• artifacts/index.yaml — archived run records (one entry per run).
• dashboard — a live visual view of jobs, analysis reports, and trajectories.

Read config.yaml → status for what is happening now, and artifacts/index.yaml for run history.

During a run

While a job is active, monitor artifacts/jobs/<job> and update the status block in config.yaml after inspection. Use status.next_steps as the live operator checklist. The job moves through idle → running → done; keep config.yaml → status current as it does.

Remote execution

eval runs on the node declared in config.yaml → meta_info.resources.ip (currently 192.168.35.240).

• If your shell is on a different host: SSH into the configured IP and operate inside a tmux session there — never invoke this block's scripts from a different node.
• If your shell is already on the configured IP: skip the SSH step and run scripts directly in a named tmux session (e.g. tmux new-session -d -s eval …).

Either way, all execution must happen on the configured IP in a named tmux session so the run survives shell disconnects. Environments and the Harbor checkout are host-local — never build them on a host the run won't use.