SECTION / 02 — CASE STUDIES
4 DEEP-DIVE STUDIES
Every substantial project gets a case study: a deep dive into the problem, architecture, data flow, methods, experiments, results and limitations — the same work the build overview covers, at full depth.
READING THE RESULTS
Results are labelled by how they were produced — BACKTEST, SIMULATION, SELF-BENCHMARK, TEST SUITE or ILLUSTRATIVE, so a simulated figure is never read as live trading.
Studies whose system is still in development are marked as such instead of carrying estimated numbers. Where a visual is a diagram rather than a measurement, it is labelled as a diagram.
THE STUDIES
SELECT ANY STUDY TO READ THE FULL CHAIN
EVERY STUDY FOLLOWS THIS CHAIN
QUESTION → HYPOTHESIS → METHOD → EVIDENCE → RESULT → LIMITATION → CONCLUSION
Each study follows this chain, from the question asked to the conclusion drawn — including any step that is still open or unresolved.
SOURCE OF EVIDENCE
REPOSITORY IS THE RECORD
Case studies summarise. The repositories are the actual artifact — commit history, test suites and build configuration included.
NEXT
FROM THE STUDY TO THE BUILD