Record 975b1623d94b46d0b00d5c024ae45ab5

You are an operations planner. Below is the current state of a small deployment environment, a goal, and a catalog of tools you may call. Each tool has typed parameters and PRECONDITIONS that must hold at the moment you call it; calling a tool whose preconditions are not met is an error and your plan fails.
CURRENT STATE:
- At the end of last week, webhooks-1 was fully torn down and has not been touched since.
- The release-image artifact does not exist yet.
- The db-migration artifact does not exist yet.
- ledger-0 is currently down (not yet provisioned).
- The secrets_synced flag is off.
- The maintenance_window_open flag is off.

GOAL (all conditions must hold at the end):
- service 'ledger-0' must reach at least the 'provisioned' state

ENTITY IDS (use these exact ids in your tool args):
Services: svc_0 (ledger-0), svc_1 (webhooks-1)
Artifacts: art_0 (release-image), art_1 (db-migration)
Flags: flag_0 (maintenance_window_open), flag_1 (secrets_synced)

TOOL CATALOG:
- id: advance_0 | name: provision | params: service: service
    Provision a service, moving it from 'down' to 'provisioned'. Precondition: the service must currently be 'down'.

Output ONLY a JSON array of tool calls that, executed in order from the current state, satisfies the goal. Each element must be an object {"tool": "<tool id>", "args": {"<param>": "<entity id>", ...}}. Do not include any prose, explanation, or markdown fences -- just the JSON array.

You may use at most 5 tool calls.

[{"tool": "advance_0", "args": {"service": "svc_0"}}]

(no reasoning captured)