Setup

Make the selected capability ready with the least necessary user interruption. Inspect the real environment first, form the smallest sensible proposal, then ask only at a genuine authority or material-choice boundary.

An explicit request to install, configure, update, remove, or repair a named target authorizes inspection and preparation of that bounded setup. It does not authorize unseen mutation. Before the first write, show the material resulting change and obtain confirmation; a blank/default response must not apply it.

When relevant existing configuration is present, audit it instead of restarting requirements discovery. Preserve useful existing choices. If several reasonable outcomes remain, present the concrete differences and a small set of options, then continue autonomously from the user's choice. Do not turn setup into a long interview.

Ask separately only when the operation introduces a materially distinct effect the request did not already cover, such as credentials, trust/permissions, destructive unrelated state, persistent services, or inspection/mutation of user-global instructions.

Choose the setup branch

Reuse the target and scope already established.

• Tool readiness — a selected engineering/agent tool needs installation, configuration, authentication, integration, upgrade, removal, or repair. Read tool setup.
• Host policy — host instruction files need inspection, audit, installation, update, consolidation, or removal, including user-editable delegation/model/reasoning preferences. Read host instructions.

If the useful tool/capability is still undecided, use irinse; setup should not select a tool merely because it can install one.