singularity ecosystem run

Invocation

singularity ecosystem run --policy /absolute/policy.json [--start-paused] [--ready-json] with every runtime input of [singularity run](/docs/cli/run): identity, --starting-balance, --instance-price, --cycle-interval-secs, --state-dir, --workspace, Brama and the signed Las inputs. The policy's SHA-256 must equal --policy-digest; its fields are listed under [fixed delegated policy](/docs/ecosystem).

State and output

The process takes the owner lock in the state directory, opens the portfolio in the fleet database singularity, recovers retained model answers and execution results, and opens ecosystem.sock. --start-paused records a pause before the socket opens; without it the recorded pause is unchanged.

--ready-json prints one flushed line, {"schema_version":2,"event":"ecosystem_control_ready","socket":…,"paused":…,"source_revision":…}, once control is listening. It does not attest Las admission, model access or delivery. The process keeps running until it is cancelled or a background operation stops.

An invalid policy, a changed owner or policy, a policy sequence that rolls back, another owner of the directory, a leftover ecosystem.sqlite3 or an unbindable socket refuses startup. Dependency failures after startup are recorded as issues, read with [status](/docs/cli/ecosystem/status).