A field investigation, not a victory lap. One drawdown, traced from the ledger - who actually did the work, how much it was worth, and the part of our own model that turned out to be incomplete.
ACT I - Everything looked wrong
On 24 June 2026, an investor opened the app and saw this:
Three days. SOL down ~13%. BTC and ETH falling with it. And next to that red chart, the book had barely moved.
The message we got was one word:
Why?
Not explain the strategy. Not what's my APR. Just - why is the thing that should be hurting, not hurting?
That is the right question. This is the investigation into its answer. We did not know it cleanly until we read the ledger back ourselves - and the answer was not the one we expected to write.
ACT II - First suspect: the Weather
The obvious answer - the one we'd have liked to give - is Liquidity Weather. It is the market sensor we talk about most: a 0-100 read on whether conditions are healthy enough for the engine to work normally. Surely Weather saw the storm and pulled the book down.
So we pulled its log for those exact days.
That is not the chart of a system reacting to danger. That is the chart of a system that saw nothing to react to.
At the very bottom - the 24th, with SOL at its low - Weather's structural sub-signals read flow toxicity 99/100 and volatility quality 77/100. In plain terms: the market was falling, but it was not broken. Depth held, spreads stayed orderly, flow stayed clean, the venues kept paying the engine for its work.
Which forces an uncomfortable sentence, and it is the hinge of this whole report:
Weather did not save the book. It stayed green the entire way down - correctly - which means whatever protected the capital, it was something else.
ACT III - So what actually saved the book?
If the headline signal was silent, something quieter did the work. So we stopped looking at signals and started reading actions - the timestamped rebalance log.
The story turns on 23 June, the day the drawdown deepened. The ledger shows three moves, in order:
- the book's risk multiplier dropped to about 0.83 - roughly a 17% cut in carried risk;
- SOL exposure fell from ~42% of the book to ~33%;
- the USDC buffer rose from ~30% to ~42%.
This is the protagonist we did not introduce at the top, because the system itself did not announce it: the Tactical Rebalancer. Unlike Weather, it does read price. When an asset falls far enough below its recent high, it mechanically carries less risk and raises cash. No forecast. No view on the bottom. Just: this asset has fallen past a line, so hold less of it.
The rebalancer did not try to be smart.
It tried to be less exposed while the market was busy being violent.
ACT IV - How much did it actually matter?
Reducing risk is easy to claim and hard to prove. So we don't narrate it - we mark it.
We run a continuous ghost book: a neutral twin that makes none of these tactical moves, priced against the same live market. The gap between the real book and that twin is the avoided damage. Not a model. A subtraction.
Peak avoided damage (24 Jun low): ~+$792,000
Carry cost during the calm (20-22): ~ -$100k to -$300k (transient)
Now, post-bounce: ~+$255,000 and normalising
That is the answer to Why?. Not Weather. A drawdown reflex worth nearly $800,000 at the low - and a hedge book of 40 puts (~$4.1M of cover) standing quietly underneath, which on this episode never needed to fire.
This is not profit. It is avoided damage.
In a risk system, the best trade often looks like something that never happened.
ACT V - Then why do we even have Weather?
Here is the fair objection. If Weather sat out the most dangerous week of the month, what is it for?
Because Weather and the Rebalancer answer two different questions, and June only asked one of them.
| The Rebalancer asks | Weather asks |
|---|---|
| Has price fallen past a line? | Has the market itself stopped working? |
| reacts to direction / magnitude | reacts to structure - depth, spreads, toxicity |
| the right tool for a drawdown | the right tool for a liquidity crisis |
June was a drawdown, not a crisis. Price fell hard while depth held and flow stayed clean - so the Rebalancer acted and Weather, correctly, did not. A liquidity crisis is the other shape entirely: the order book thins to nothing, spreads blow out, flow turns toxic, and trying to de-risk into it only feeds the fire. That is the event Weather exists to catch - the one where the right move is to stop trading, not to keep rebalancing into a vacuum.
Weather does not say "the market is falling."
It says "the market is broken."
Those are different emergencies, and they need different reflexes.
An honest footnote: Liquidity Weather has only been live since mid-June, so June was its first real market stress - and what it correctly reported was that this particular stress was not structural. We have not yet watched it catch a true liquidity crisis in production. When it does - or fails to - that will be its own entry in this log.
ACT VI - What we got wrong
Now the part most funds delete before publishing.
For weeks we have pointed investors at Liquidity Weather as the market-risk signal. June proved that framing was incomplete:
We discovered that our headline market signal is blind to an entire class of drawdowns - the ones where price collapses but liquidity stays healthy.
The book was fine, because a different system caught it. But "fine by accident of a second system" is not the same as "covered by design." If the Rebalancer's threshold had been set differently, or if we had ever leaned on Weather alone to de-risk, the book would have held full exposure straight into a 13% fall and called the dashboard green the whole way down.
That is not acceptable, and we are not going to file it under "wording."
Three more things we will say plainly while we're here: the risk cut was modest and reactive (it followed price down rather than leaning ahead of it); the re-entry was fast (the cash buffer came back in a single day - premature if the 25th had been a false bottom); and the overlay's carry cost in calm markets is real and compounds. The +$792k headline is only honest standing next to all three.
ACT VII - What changes tomorrow
Today the risk stack reads like this:
Weather → is the market broken? (structure)
│
▼
Tactical → has price fallen past a line? ← did all the work in June
│
▼
Protection → the standing airbag (puts)
The gap is visible: the only thing watching price magnitude was buried inside the Tactical layer, invisible to the headline view. So we are giving it its own eyes.
Weather → is the market broken? (structure)
Drawdown Signal → how far has price fallen? (magnitude) ← NEW
│
▼
Tactical → acts on both
│
▼
Protection → the standing airbag
As of today there is a new, measured drawdown signal sitting beside Weather - recording how far SOL, BTC and ETH have fallen from their recent highs, on the same thresholds the Rebalancer already uses. It is observe-only: logged and shown, but not yet allowed to move a single position. It will earn that right only by being replayed against this exact episode (and others) and shown to help more than it hurts. It is a measured condition, never a price prediction - we still refuse those. When it graduates to live - or fails the test and we delete it - that will be a dated line right here.
What the ledger proves
Every number above was read back from timestamped rows: the price series, the Weather scores and their sub-signals, the rebalance moves, the composition by day, the ghost-book mark, the open hedge book. Nothing was reconstructed from memory or rounded toward a nicer story - including the parts that are unflattering.
The point is not that we can tell you what happened.
The point is that the ledger can replay it - including the chapter where we were wrong.
Closing
Systems earn trust in calm markets.
They earn conviction when they survive discovering they were incomplete.
June was not valuable because the book avoided nearly $800,000 of additional damage.
It was valuable because it showed us, in public, where the architecture was still missing a piece.
The ledger kept the trade.
This Journal keeps the lesson.