12-week course · for the curious operator

Build your own automated options
trading system.

A bot follows your rules without flinching. You stay the head chef. Twelve weeks, one focus per week — the idea, the outcome, the new vocabulary, the hands-on work, and the real-money war story that anchors the rule of the week.

10 of 12 weeks published
15 concept lessons
1–2 hours per week
Use arrow keys · F for fullscreen

Intro deck course introduction · 4 versions

Intro v1
Course introduction — original
The Gretzky framing: skate to where the puck is going, not where it has been.
/tc/intro
Intro v2
Course introduction — refined
Second iteration with tighter flow and clearer positioning.
/tc/intro-v2
Intro v3
Course introduction — polished
Third iteration. Polished framing of the 12-week journey.
/tc/intro-v3
Intro v4
Course introduction — latest
Current version. Cinematic transitions, staggered reveals, slide counter.
/tc/intro-v4

TA-AI mentorship technical analysis & sizing for AI-era traders

Session 1
The Inner Game of Markets
Cognitive biases, anchoring traps, and emotional shortcuts that turn a working edge into a losing year.
/tc/ta-ai/session-1
Module 01
Foundations of Technical Analysis
Dow Theory and the candlestick alphabet — the two oldest, most durable lenses for reading a chart.
/tc/ta-ai/module-01-dow-candlesticks
Interactive
The Money Management Experiment
A hundred-trial 60/40 game where the edge is yours and ruin still finds most players. Play once, then see your equity replayed at Kelly 20%.
/tc/ta-ai/money-management
All sessions →
TA-AI mentorship index
Landing page with every session in one place. Future modules are added here as they ship.
/tc/ta-ai

The 12-week core one focus per week · weeks 1 → 10 live

Week 01
Why automate, and what "automated" really means
War story: one careless kill command stopped two strategies.
/tc/w1
Week 02
Meet Claude, your coding partner who never sleeps
War story: Claude wrote a confidently wrong table of expiries.
/tc/w2
Week 03
Markets, the way software sees them
War story: a wrong holiday file put a strategy live on a closed exchange.
/tc/w3
Week 04
Setting up your toolkit
War story: lots vs units — "3" in one segment means "195" in another.
/tc/w4
Week 05
Talking to your broker through code
War story: a second broker had no quote API — every later strategy was redesigned around it.
/tc/w5
Week 06
Your first real strategy, coded from scratch
War story: a "wait for breakdown" LIMIT order filled instantly at the current price.
/tc/w6
Week 07
Telegram: your bot's voice, wired before money moves
War story: alert spam got the operator to mute the bot — including the real emergency.
/tc/w7
Week 08
Safety nets: hard limits in code
War story: SL filled milliseconds before our cancel reached the exchange.
/tc/w8
Week 09
Going live with one lot
War story: cancel-and-replace turned into both orders filling.
/tc/w9
Week 10
From script to system
War story: three independent bugs in the first 60 seconds while 99 unit tests sat green.
/tc/w10

Concept lessons supplementary topics · off the numbered track

Concept
Git branching basics
Why main and a feature branch coexist — and when to swap between them.
/tc/concepts/git-branching
Concept
Git's "limbo" state
When git status says clean but a file is missing — what just happened, and how to recover.
/tc/concepts/git-limbo-state
Concept
Deploy: local → Lightsail
Moving a working bot from your laptop to a server that runs while you sleep.
/tc/concepts/deploy-from-local-to-server
Concept
Context management — Claude's working memory
Every file read and tool call fills the same finite window. Compact, clear, be specific, and delegate the journey to subagents.
/tc/concepts/context-management
Concept
Claude Code subagents
A specialist Claude that reviews your order code against 170+ live trading bugs.
/tc/concepts/claude-code-subagents
Concept
CLAUDE.md — the one file loaded first
The most leveraged file in your repo. Why it rots silently, and the three mechanisms that keep it honest.
/tc/concepts/claude-md
Concept
MEMORY.md — the second-layer index
The private notebook Claude builds with you. How it differs from CLAUDE.md, and the self-updating loop that keeps it from bloating.
/tc/concepts/memory-md
Free Session v1
Download free 1-minute historical data (detailed)
Step-by-step: Dhan account setup, install packages, write the script, run it, read the columns, troubleshooting. 14 slides.
/tc/concepts/download-data-v1
Free Session v2
Get free market data in 2 minutes
One prompt to Claude, two commands, and you have a month of NIFTY & BANKNIFTY candles. Then ask questions about your data. 12 slides.
/tc/concepts/download-data
Incident · BUG-175
Phantom fills: when your broker lies about a trade
21 May 2026 · DecayDoctor T0. The API said "filled." The exchange hadn't seen it. We placed a stop-loss for a position that didn't exist — a naked long waiting to lose money on the next trigger.
/tc/concepts/phantom-fills
Incident · BUG-204
Partial fills: when the broker only sells you half
27 May 2026 · RSI Sniper T2. 80 of 100 filled, strategy moved on, the other 20 quietly filled four minutes later — naked short for 4 min 26 s, no SL, found only in the broker app. Manual squareoff cost ₹487.
/tc/concepts/partial-fills
Incident · BUG-083
Double-leg atomicity: both legs fill or neither does
6 Apr 2026 · Option Cracker. One leg of a straddle filled, the other failed to cancel in time, emergency exit also failed — and the live short stayed invisible to every monitor until manual reconciliation. A straddle with only one leg isn't a straddle.
/tc/concepts/double-leg-atomicity
Concept
Watchdogs: the processes that watch the processes
Hedge Runner and the MCX SL Watchdog — two outside actors that check broker truth on a clock, on a separate Telegram channel.
/tc/concepts/watchdogs
Session 2
From Signal to Order — what happens after your backtest says buy
Build a paper trading simulator. Then read a real system's trade log and find the failure.
/tc/concepts/next-session
Interactive
Paper Trading Simulator
LIMIT orders, slippage, stop-losses, expired fills — tweak the knobs and watch the P&L change.
/tc/concepts/simulator
Free Session
Backtest a strategy by talking about it
Connect Volrix to Claude Code in four clicks, then test any strategy in plain English. What you can test, how to word the prompt, how to read the six numbers, and how to get the CSV. No coding. 16 slides.
/tc/concepts/volrix
Detailed version
Backtesting by conversation — the technical walkthrough
The same subject for people who want the machinery: the tool surface, the submit-and-poll loop, and a real 20-run window sweep with the two traps that make a fast wrong answer look like a right one. 15 slides.
/tc/concepts/volrix-mcp
Weeks 11 (backtesting honestly) and 12 (your second strategy) coming soon. Concept lessons grow as supplementary topics surface. — Kapil