← Case studies

Chapter 1 — Vision & Philosophy

Why systematic over discretionary. The survival-first principle. What KaizEn refuses to be.

March 23, 2026

Where It Started

I'm a software engineer, not a trader.

I don't read charts with intuition. I don't rely on gut calls with real money.

What I do trust is a well-designed system.

So when I decided to build a trading engine, I treated it the same way I would treat any serious software project: define the rules, test them rigorously, and only ship when the system earns that trust.

That mindset became the foundation of KaizEn.


Why Systematic

There are two broad approaches to trading.

Discretionary — human judgement drives every decision. Experience, pattern recognition, and intuition guide the trade.

Systematic — rules are defined upfront. The system follows them consistently, every time.

For me, systematic was the natural fit.

I think in code. I trust what can be tested, measured, and reproduced. A systematic approach lets me validate every decision before it touches real capital, version-control the logic, and improve it over time with data rather than memory.

It plays to my strengths as an engineer — and that alignment matters.

KaizEn is systematic by design and by conviction.


Survival First

KaizEn starts with one question: how do I protect capital first?

This is the survival-first principle.

It sounds conservative. But there is a simple mathematical reason behind it: a 50% loss requires a 100% gain just to break even. Deep drawdowns don't just hurt a portfolio — they destroy the compounding curve. Recovery takes years.

A system that grows steadily with controlled drawdowns compounds far more effectively over time than one that swings wildly.

Preservation of capital is the edge.

That shapes every design decision in KaizEn:

  • Hard stop losses on every trade
  • Daily maximum loss limits
  • Circuit breakers that halt execution under abnormal conditions
  • A kill-switch that can stop everything immediately

These are not optional features. They are the system's immune system.


The Benchmark: S&P 500

KaizEn measures itself against a simple alternative: buy an S&P 500 index fund and leave it alone.

That baseline returns roughly 10% per year on average, with low cost and minimal effort.

Any system more complex than that needs to justify its complexity. It must clear a higher bar — better risk-adjusted returns, lower drawdowns, or both.

This is why the performance gate exists. The S&P 500 is not just a benchmark. It is a forcing function that keeps the system honest.


Design Boundaries

Some design decisions were made early and deliberately.

Fixed position sizing. Every trade is sized relative to the defined risk per trade — not based on recent performance or confidence level. Consistency matters more than optimization.

No prediction. KaizEn does not try to forecast where the price will go. It identifies conditions where the edge has historically existed and acts within those conditions. Reaction over prediction.

Models must be validated. Any model used must be traceable — training data, version, live vs. backtest performance. If a model drifts from expectations, the system falls back to rule-based logic automatically.

Sitting out is a valid decision. If the market regime is unfavorable — choppy, ranging, or unclear — the correct output is NO_TRADE. Not every market condition offers an edge worth taking.


The Philosophy in One Sentence

Build a system rigorous enough to trust, and disciplined enough to survive when the market doesn't cooperate.

Everything else follows from that.