Inside the cloud, and the lateness the confirmations buy
One structural failure state, one designed-in cost, and one problem that is really about the user rather than the system.
Key takeaway
- Inside the cloud the system has no view, and price can stay there for weeks
- Four confirmations mean genuinely late entries — this is the price paid, not a flaw to fix
- Five lines and multiple readings mean a determined user can always find a bullish interpretation
Inside the cloud: the state with no answer
When price is inside the cloud, the system is explicitly saying it does not know. The regime condition fails, the lines chop, and every crossover signal generated there is unreliable.
This is honest and it is uncomfortable. A market can spend weeks inside a thick cloud, during which the correct output is no position at all.
What people do instead is take the crossovers anyway, on the reasoning that a signal is a signal. Inside the cloud they are a stream of small losses — the system's designed way of saying nothing, ignored.
The lateness is the cost of the confirmations
By the time price is above the cloud, Tenkan is above Kijun, the lagging span is clear and the forward cloud is bullish, a substantial part of the move has usually happened.
- In a strong trend this is fine — there is plenty of move left and the system holds it well.
- In a short-lived move it is fatal. The signal completes near the end and the trade is stopped out on the reversal.
- There is no setting that fixes it. Dropping a condition to enter sooner is choosing a different point on the same trade-off, not improving it.
The problem that is really about the reader
Five lines produce many possible readings: crosses above and below the cloud, cloud twists, flat Senkou B levels, the lagging span's relationship to price and to the cloud, cloud thickness, and the future cloud's colour.
A framework rich enough to describe every configuration is a framework in which a determined user can always find support for what they already wanted to do.
The failure pattern
- Signal incomplete, but 'the cloud is thin so it will break through'
- Lagging span obstructed, but 'that's a lagging measure anyway'
- Price inside the cloud, but 'the cross is clearly bullish'
- Every configuration has a bullish reading available
The discipline
- Write the four conditions down before you look at a chart
- All four, or no trade — no partial credit
- Log the signals you declined, not just the ones you took
- Inside the cloud means no position, without exception
What the evidence actually says
Independent testing of Ichimoku is thinner than for simpler systems, partly because 'an Ichimoku signal' has several defensible definitions and results vary considerably between them. What testing exists generally finds performance broadly comparable to other trend-following approaches — which is neither a vindication nor a dismissal.
Common questions
- Is Ichimoku better than a moving average system?
- It gives you more information from one picture — trend, momentum, expected support and a forward-looking element that moving averages have no equivalent of. Whether the extra information improves outcomes is not settled, and the additional complexity introduces its own failure mode in the form of selective reading.
- Do I need all five lines on the chart?
- Many traders remove the lagging span because it clutters the display, and it is the condition most likely to veto a trade — which means removing it systematically increases your signal count in exactly the wrong direction. If the chart is too busy, the answer is fewer instruments, not fewer conditions.
These are documented methods described for study. Nothing here is investment advice, a recommendation, or a claim about future returns — every system on this page has losing periods, and the pages say where.
Reading about a system is not having one.
Plutux is where you write your own rules down, test them against real data, and keep the record your memory would otherwise rewrite. Join the waitlist for early access.