desk-autopilotlisted
Install: claude install-skill Mendurim/strikegrok-trading-desk
# Autopilot
`desk-signal-scan` and `desk-standing-approvals` describe a desk that scans hourly, fires on a frozen rule at 03:00 and sends inside signed bounds. They are written for agents. `scripts/autopilot.py` is the same two runbooks with the language model taken out of the path.
That is the whole point. A Bot deciding at 03:00 whether a rule fired is a Bot writing its own evidence. A script evaluating a frozen rule on closed bars produces the same answer twice, and the answer can be checked afterwards against the bars.
```bash
python3 scripts/autopilot.py scan # hourly
python3 scripts/autopilot.py monitor --rule strategies/r/rule.json # at bar close
python3 scripts/autopilot.py sweep # Tier 0 housekeeping
python3 scripts/autopilot.py monitor --rule … --dry # rehearsal, sends nothing
```
## The prerequisite that is not negotiable
Tier 1 refuses unless `STRIKEGROK_STATE_TRUSTED=1`, and that flag is the operator asserting the signer runs as its own OS user. **On a shared Grok workspace the Bots and the signer are the same user, so the assertion is false and autopilot must not be run there unattended.** Setting the flag to make standing approvals work hands the slot, replay and daily-loss bookkeeping back to the thing it is meant to bound.
Unattended trading therefore needs your own machine or VPS, and two accounts:
| User | Owns | May |
| --- | --- | --- |
| `strike-signer` | the API walle