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 and SFT stats.

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

Time convention

started_at and last_updated are recorded in UTC. Existing job directory names may include the local launch timestamp (UTC+8) so they continue to match the actual artifact path.

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.