desk-standing-approvalslisted

# Standing approvals Earlier versions of this desk approved every trade by hand. That is the right control for a discretionary idea and the wrong one for a frozen rule that fires at 03:00 UTC. This skill moves the approval from the trade to the rule, and moves the gate from the prompt to the code. ## Why the prompt cannot be the gate Every Bot shares one computer and one filesystem. A Bot can write to `desk.md`, to a proposal file, and to the floor. So a Bot could write itself an approval. The earlier design leaned on Grok Bot's Require Approval rule for exactly this reason. Once that rule is relaxed so the desk can act unattended, the only enforcement left is inside `scripts/strike_request.py`, which is the one thing that holds the API key. `scripts/desk_policy.py` is that enforcement. It refuses to sign anything that opens exposure unless a file **the user signed, with a key the computer never holds**, says it may. ## The three tiers | Tier | What | Approval | Enforced by | | --- | --- | --- | --- | | **0** | reduce-only: place or tighten a protective stop, exit on a rule's stated invalidation, cancel orphaned stops, cancel an expired unfilled entry, **add** margin to a position | none needed | policy: `reduce_only`/`close_position` true, cancel with a symbol, or margin add | | **1** | open or add exposure when a frozen rule fires, inside signed bounds | a standing approval `SA-NN` in the signed register | policy: register signature, bounds, kill conditions, rule hash,