Execution on Thetabruv

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Setup (broker, margin, products)#

This page is the system’s bill of materials: what you need, why exactly that, and where the breaking points are. I split it into three layers: the account at the broker, the hardware at home, and the software running on top. Fair warning: it’s the page that will age faster than the rest of the site — the models and prices quoted are valid today — but the selection criteria will hold.

The TRPS bot

Mon, 01 Jan 0001 00:00:00 +0000

The TRPS bot (Tail Risk Protection Selling)#

The TRPS bot is conceptually simple: the strategy on the TRPS page is already a list of rules with times attached, and the code does nothing but execute it. The hard part isn’t the trading logic — a hundred lines or so — but everything around it: reconciliation, handling broker errors, behavior in degenerate cases. I’ll describe it the way the bot lives it: a state machine moving through the New York day, where every transition has explicit preconditions and every failure has a safe destination (Principle 2 on the Execution page). Times are in the America/New_York timezone, naturally, and the exchange holiday calendar is the first thing the bot consults on waking: on market holidays it doesn’t transition at all, and on half-days (early closes) the evening times shift accordingly.

The DHCS bot

Mon, 01 Jan 0001 00:00:00 +0000

The DHCS bot (Delta-Hedged Convexity Selling)#

If the TRPS bot lives on fifteen-minute windows, the DHCS bot has a single appointment a day — but the numbers have to balance to the decimal. The strategy from the DHCS page — front-month ATM/−1σ put, daily delta-hedging with Micro futures, monthly roll — translates into an architecture shorter and more relaxed than the one described in The TRPS bot, and the difference between the two bots is itself instructive: it replicates, at the software level, the comparison between the two strategies on the TRPS vs DHCS page. Here too, all times are in America/New_York.