TENET
Self-authored guardrails for impulsive trading.
Rules written after close become explicit interventions at the moment an order is sent. PAUSES AND EXPLICIT HARD LIMITS.
01 · INSIDE THE TRADE — MOBILE TRADING
The broker ticket looks normal until send. Then your own rules step in — a wait, a trim, a queue — with scenario-specific choices: loss and size rules allow an override; pacing allows waiting or cancellation; wind-down has an explicit hard limit.
02 · AFTER THE CLOSE — RULES & HISTORY
Turns interventions into evidence, and evidence into future rules. The options cap is shared with Dart; both brokers write to the same local Record. Also explore
Desktop trading (Meridian) →
WHAT’S REAL, WHAT’S SIMULATED
Dart, Meridian, quotes, fills, and the trading history are fictional. The staged interventions and Record work locally in this browser. Completed interventions and rule edits create events. The broker integration, future rule activation, and cloud sync are not implemented.
WHAT TENET READS & STORES
The integration design places Tenet inside the broker at order submit — an SDK the broker embeds. It reads order tickets at send and fills after the close; never your screen, never other accounts. In this prototype, rules and the Record are saved in this browser. A Tenet account and broker SDK are proposed, not connected.
SYNC & LEAVING
Lowering the options cap updates Dart immediately; increases remain pending. Meridian uses a separate 1,500-share cap. Disconnect and first-run controls preview interface states; account deletion and live broker disconnection are outside this demo.
INSIDE DART — RULES STEP IN AT SEND
» Pick a scenario, size an order, swipe (or Tab to the rail and press Enter). Resolve the size cap and cooldown together, or override with a reason — nothing ever sends by itself.
AFTER CLOSE — RULES & RECORD LIVE HERE
» Tighten the size cap (− on SIZE CAP) and Mobile trading beside it enforces the new number immediately; loosen it and it waits for the open. Draft the Friday rule to preview a future start; open a Record row for notes, errors, and simulated sync retry.