Mendurim

desk-execution-protocol

The Execution Trader's procedure for turning an approved ticket into one Strike action through the signed API and reconciling it - the pre-send checklist, the preview block, single-send discipline, unknown-result recovery by client order id, and the execution report. Use before and after every send, cancel, replacement, leverage change or close.

desk-incident-response

What the desk does when something goes wrong - a send whose result is unknown, a rejected order, a position that does not match the ticket, a position with no stop, orphaned or stuck orders, an outage or rate limiting, and a suspected compromised API wallet. Contain with the smallest reversible action, rebuild the truth from the exchange record, act only through approved tickets, then review. Use the moment anything disagrees with the ticket.

desk-monitoring

How the desk keeps an eye on markets and the account between trades - scheduled routines, the daily desk brief, book checks, and watches built on polling or the WebSocket feeds - including what a watch is allowed to do and why silence from one is never an all-clear. Use when the user asks for briefings, alerts, "watch X", or scheduled checks.

desk-operating-model

The rules every Bot on the StrikeGrok desk follows - who holds which job, where the desk keeps its files, what counts as evidence, how the user's approval works and why it is not the gate, and the format for handing work between Bots. Use when setting up the desk, when ownership of a task is unclear, or when a request does not fit the ordinary trade lifecycle.

desk-post-trade-review

How the Trade Reviewer keeps the desk journal and reviews trades from the exchange's own record - grading process separately from outcome, measuring what execution actually cost, and drawing one repeatable finding per review - plus the weekly desk review and the incident review. Use after any send, when a trade closes, on the weekly routine, or when the user asks how something went.

desk-risk-limits

How the Risk Manager agrees the desk's limits with the user, sizes each proposed trade from live account state and the market's real constraints, inspects the book, and returns a PASS with exact ticket fields or a REJECT naming the gate that failed. Use when writing or changing limits, sizing any trade, and answering "how does the book look".

desk-signal-scan

How the desk finds and times opportunities without being asked - the Market Analyst's universe scan across every trading market, the Research Analyst's T-minus catalyst alerts, the Strategist's live rule monitors, the shared signals file they all write to, the four clocks that decide whether a fired rule is actionable now, and how a signal becomes a proposal or expires. Use when setting up routines, when the user asks what the desk is watching, or when a signal needs to be turned into a ticket.

desk-standing-approvals

How the desk trades autonomously without losing the approval control - the three tiers (reduce-only always, standing approval per frozen rule, the user's line per trade), the signed standing-approval register the Bots can read but not write, the bounds and kill conditions every approval carries, how one is earned, widened, suspended and revoked, and how scripts/strike_request.py enforces all of it in code before it signs anything. Use when the user asks to "let it run", when granting or reviewing an approval, or when the policy layer refuses a send.

desk-strategy-lab

How the Strategist turns the user's own trading idea into explicit rules, tests it honestly on Strike candle and funding history without fooling anybody, and runs it forward at minimum size through the desk lifecycle. Method only - the desk ships no strategies and makes no claims about returns. Use when the user wants to design, test, compare or forward-test an idea.

desk-trade-lifecycle

How one trade travels the StrikeGrok desk from first idea to written review - the seven stages, who owns each, the proposal file, the ticket format, what counts as approval, and when a proposal is live, closed or void. Use whenever the user wants to open, adjust or close a position, and whenever any Bot is about to write to the exchange.

strike-account

Reading Strike Finance account state through the signed REST API - the account object, balances, portfolio, open positions, open orders, closed positions with realised PnL, order and fill history, funding actually paid, and the transaction ledger. Use before sizing any trade, when checking whether protection exists, when reconciling a send, and when building a post-trade review. Read-only; nothing here changes anything.

strike-advanced

Strike Finance execution features beyond a single order - TWAP strategies, batch and batch-replace orders, cancel-all, isolated-margin adjustment, post-only and price-protect flags, and trailing stops - with the approval each needs and the ones this desk refuses. Use when a ticket calls for a TWAP or a multi-order send, when adjusting isolated margin, or when deciding whether a feature is in scope. Write paths - Execution Trader only.

strike-api-reference

Compact reference for the Strike Finance surfaces the desk uses - every public Price Service endpoint, every signed trading and account endpoint with its parameters, the API wallet signing scheme, order types, flags and time-in-force, order status codes, per-market constraints, rate limits and error strings, plus the optional crowdtime MCP research tools. Use to look up an endpoint, a field, a status code or a flag without re-reading a whole skill.

strike-auth

The desk's Strike Finance API wallet - generating an Ed25519 keypair, registering the public key, the request signing scheme (method, path, timestamp, nonce, body hash), the signed-request helper every authenticated call goes through, what the key can and cannot do, and rotation. Use when connecting the desk to a Strike account, when any authenticated call returns 401, or when a key is rotated. Read this before strike-account and strike-orders.

strike-market-data

Reading Strike Finance market data from the public REST Price Service - mark and index price, order book depth, spread, funding, open interest, 24h statistics, candles and per-market trading constraints. No key, no account. Use for market briefs, liquidity reads before execution, and candle history for backtests. Read-only.

strike-orders

Placing, protecting and cancelling Strike Finance orders through the signed REST API - limit, market with a slippage bound, bracket strategy orders with attached take-profit and stop-loss, standalone triggers, trailing stops, replace, cancel, client order ids, rounding, and reading the order back from the exchange. Use when executing an approved ticket, attaching protection to a position, or amending a resting order. Write paths - Execution Trader only, after a Risk PASS and the user's approval by ticket id.

strike-positions

Managing Strike Finance positions through the signed REST API - leverage per symbol, cross and isolated margin mode, reading margin usage and distance to liquidation, attaching protection to an existing position, and closing with reduce-only orders. Use when setting up a market before a first trade, when a position needs protecting or closing, or when checking liquidation risk. Leverage, protection and closes write; reads are open to the Risk Manager.

strike-setup

Prepare the desk computer to work with Strike Finance - the two surfaces (public market data and the signed trading API), confirm public connectivity, provision the API wallet through the secure secret store when the user asks to trade, run the read-only readiness check, and understand why the desk rehearses with previews and minimum-size orders rather than testnet. Use during desk setup, when moving between research and trading levels, when a key is rotated, or when any Strike call fails with an environment problem.

strike-websocket

Live Strike Finance data over WebSocket - the public price stream (mark price, depth updates, trades, klines) and the authenticated user stream (order fills, position and balance updates) - plus how to run a watch process on the desk computer, keep a local order book in sync, supervise it with a heartbeat, and tell a dead feed apart from a quiet market. Use for monitoring, alert conditions and watching a live position. Read-only.

strikegrok-bootstrap

Build and verify a StrikeGrok trading desk from the pinned public release. Use for first-run setup, repair, or a readiness check. Starts with a live zero-key Opening Bell on Strike's public Price Service, installs the seven role profiles and nineteen shared skills, prepares the Trading Floor, provisions the Strike API wallet only when the user asks to trade, and returns an evidence receipt. Read-only by default; never requests a key or places an order.