// Track

Tests Pass ≠ System Works

Operational validation as a distinct discipline

Test coverage measures code integrity. Operational validation measures whether the system produces its intended outcome. The gap between them is where the best-tested bot in the ecosystem goes 3 weeks without placing a trade. This track is the cultural correction.

6 lessons~45 min total

Lessons are shown in recommended order. Complete them in sequence for the best experience — or jump to any lesson.

Lesson 284·8 min read

The 340-Test Bot That Never Traded

The Agent Framework story as case study. 95% coverage, 5 docs, a runbook, a watchdog — and zero real trades for weeks. What test coverage measures, what it does not, and why this gap is the cultural failure that defines production ML.

Lesson 285·6 min read

Last Real Trade as a Metric

Bot liveness dashboards. 'Hours since last real trade' as a first-class metric, displayed alongside test pass rate. Separate axis from code quality — and the single number that would have caught Agent Framework before the ceiling analysis debate.

Lesson 286·7 min read

Operational Validation Checklist

What 'done' actually means. Running system produces intended outcome equals done. Merged PR equals not done. Tests passing equals not done. Deployed equals not done. The cultural correction that closes the loop Agent Framework exposed.

Lesson 551·8 min read

Post-Deploy Smoke Tests

The gap between 'merged' and 'working in prod.' A minimal smoke suite hits the real serving surface in 30 seconds and blocks the rollout before a single user sees a broken deploy. How to tag, wire, and keep smoke suites honest.

Lesson 552·7 min read

Write-Path Verification: The Probe Write

Read-path checks lie. A health endpoint can return 200 while every database write silently fails. The probe-write pattern — one minimal, reversible end-to-end write before declaring an integration live — is the only check that cannot be faked by a healthy-looking read path.

Lesson 553·9 min read

The Four-Gate Delivery Validation Pipeline

Every failure class this track documented — the bot that never traded, the broken deploy config, the silent write failure, the gradual drift — has a corresponding gate. This capstone shows how all four compose into a single, non-bypassable delivery validation pipeline.