desk-trade-lifecycle

Orchestrates the seven-stage trade lifecycle from proposal to journaled review on the HyperGrok desk.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/swcstudiospace/hypergrok-autonomous-desk --skill desk-trade-lifecycle-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: desk-trade-lifecycle
Source: https://github.com/swcstudiospace/hypergrok-autonomous-desk/tree/main/skills/desk-trade-lifecycle
Command: npx skills add https://github.com/swcstudiospace/hypergrok-autonomous-desk --skill desk-trade-lifecycle-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Trading desks need a consistent, auditable procedure so every position change follows the same path from idea to reviewed result, with no stage skipped and no unapproved order reaching the exchange. This Skill defines that end-to-end procedure for the HyperGrok desk, replacing informal chat approvals with a JSON ticket and a deterministic policy gate. ## Core Features & Use Cases - Seven-stage lifecycle: Enforces the ordered flow idea → evidence → risk sign-off → policy gate → execution → reconciliation → review, with a named owner for each stage. - Ticket and gate workflow: Produces a Markdown ticket plus a JSON ticket file checked by scripts/policy_gate.py against autonomy.json limits and live account state before any send. - Adjustments and protective orders: Treats stop moves, adds, reduces, and closes as new suffixed tickets, with protect and close tickets always passing the gate so positions are never left unprotected. - Use Case: A user asks to long ETH on a retest of 3,000. The Desk Lead opens proposal HG-20260907-01, the Market Analyst gathers evidence, the Risk Manager issues a PASS ticket, the gate validates it, the Execution Trader sends and reconciles, and the Trade Reviewer journals the closed trade. ## Quick Start Ask the desk to open a trade proposal for your idea, for example by saying you want to long ETH-PERP on testnet with a stop below 2,900, and let the lifecycle run each stage in order.

Frequently Asked Questions about desk-trade-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I open a trade on the HyperGrok desk?▼

Open a proposal by assigning an id like HG-YYYYMMDD-NN and creating a Markdown file under proposals/ with market, idea, and status fields. The lifecycle then runs evidence gathering, risk sign-off, the policy gate, execution, reconciliation, and review in order.

How does the policy gate approve a trade ticket?▼

The gate script policy_gate.py reads the JSON ticket, autonomy.json, the halt file, the send ledger, and live account state, printing every check with its numbers. It exits 0 for PASS, 1 for FAIL, or 2 when an input is unavailable, and a PASS is valid for ten minutes.

Can I close or protect a position when the desk is halted?▼

Yes. Protective tickets with kind set to protect and close tickets always pass the gate, halted or not, so an unprotected position never waits on anyone. They are still full tickets with their own Risk sign-off and are journaled like any other trade.

What happens if a trade ticket fails the policy gate?▼

A gate FAIL ends the lifecycle for that ticket, and the failed gate names are recorded under the approval section. Nobody edits the ticket to make it pass; a changed idea requires a new ticket with a fresh Risk sign-off.

Does the trade lifecycle work on testnet before mainnet?▼

Yes, the lifecycle is identical on testnet, which is the default mode in the autonomy.json template. Users see the same tickets, gate output, reports, and reviews with play money before any real key exists.