Module paths 

Directory names under <mur_home> that a fleet / deep-research run writes.

One list, two readers that must never disagree: mur-core creates and writes these while a run executes, and mur-agent-runtime carves exactly these into the kernel sandbox for an agent-triggered run (fleet_run). They lived as two separate literals and drifted — runs/ was writable by the CLI and denied to the sandbox, so every agent-triggered run failed to register itself and mur fleet status reported nothing for a run that was live (fleet develop-rust, 2026-09-09). The list lives here because the runtime must not depend on mur-core.

Constants

FLEETS

Fleet definitions: <mur_home>/fleets/<name>/fleet.yaml, plus the operator’s .stopped kill-switch and the daemon’s .last_run stamp.

FLEET_PROGRESS_FILE

The fleet’s single progress record, inside fleet_state_dir. Kept after a run as the last-run record; overwritten by the next run. Read by both the CLI and the runtime’s fleet_run live-run guard, so named once here.

FLEET_STATE

What a fleet’s runs write, per fleet: <mur_home>/fleet-state/<name>/ (job queue, progress record, event log, parallel-track state).

RUNS

Run-status records: <mur_home>/runs/<run_id>/run.json.

RUN_STATE_DIRS

Every directory an in-sandbox fleet run must be able to write.

Functions

fleet_state_dir

<mur_home>/fleet-state/<name>/ — every file a run of name writes.