---
name: commission
description: Commission this machine for impstack setup, troubleshooting, or provisioning by probing it against the fixed contract and recording proven local state.
---

# Commission this machine

Probe the current machine. Write one global machine skill from observed results. Keep all secret values out of commands, output, and files.

## Run the probe

1. Locate the impstack repository. Use `~/impstack` unless `IMPSTACK_DIR` names another path.
2. Run `bin/commission check --repo "$IMPSTACK_DIR" --home "$HOME" --format text`.
3. Set the wizard path to `$HOME/.config/impstack/commission-wizard.sh`.
4. Run `bin/commission probe --repo "$IMPSTACK_DIR" --home "$HOME" --wizard <wizard-path>`.
5. Read the generated record path from the command output. Expand `$HOME` locally.
6. If the output says `custom`, resolve the shared root locally. Do not report that root.

The probe runs the fixed assertion registry in `commission.contract.json`. It records every status and exact command. The `proof.install-bin` assertion is the required real proof lane.

## Handle the result

- If every applicable assertion passes, report the record path and the proof command.
- If an assertion fails, report its ID and its recorded remediation.
- If the wizard has stages, tell the operator to run its path. The wizard alone handles login, browser, URL, token, and credential input.
- If a proof cannot run, keep the failed or not-applicable result in the record. Do not describe it as verified.

Never ask the operator to paste a secret into the conversation. Never include an environment value in a report. Run an install step only when the recorded remediation names that step.