Devops Start Services

Bringing the service fleet up — NATS and the ores services.

1. Check the database is up and current before starting anything. The services fail their first query against a missing or stale schema, and the failure surfaces as a service crash rather than a database error.
2. Start the fleet with the recipe below, then verify. Starting is asynchronous: the command returns before the services are ready.
3. Read the status, do not assume it. running is the only state that means ready; starting means the health check has not passed yet, and missing means the unit is not installed in this worktree at all.

• How do I start the ORE Studio services? — starting the fleet and verifying it.

• ores.compass — the tool every one of these commands runs through.