A fixed crypto sleeve's rebalancing rule buys into a 14.79% losing week
Should the fund's periodic rebalance add to a crypto sleeve that fell 14.79% in a week, or hold the sleeve's existing size until a weekly close stops printing new lows?
The market facts are real; the decision maker is illustrative.
The week and the position
In the week of 3 December 2018, BTC fell from 4,160.55 to 3,545.37 (-14.79%), a 29.70% range, with a -6.89% day on Thursday and a +3.93% day on Sunday. The weekly low of 3,222.00 was set on Saturday at 13:00 UTC, the market closed at 33.80% of its weekly range, and realised volatility was 118.7% annualised. The four prior weeks returned -0.56%, -12.23%, -27.84% and 1.77%. Volume ran 1.19 times the prior twelve weeks, and ETH underperformed BTC by 5.25 percentage points. An illustrative allocator runs a small, fixed-size crypto sleeve and its scheduled rebalance is due.
Judgment
Keep the sleeve at its current size and skip this rebalance's scheduled purchase. The week was the 7th percentile of history, the close sat at 33.80% of the weekly range, just above the boundary of the lower third, and the low arrived on the next-to-last day, so the decline was still resolving into the close. Adding here converts a rule meant to enforce discipline into buying a market that has closed lower in four of the last five weeks. Cutting the sleeve now would also realise a loss in a 7th-percentile week and give up Sundays like the +3.93% day. Accept tracking error against the fixed allocation.
What would change it
Resume scheduled purchases once a week closes above the 4,160.55 open of this week. If the sleeve's cumulative loss breaches the fund's stated loss budget, cut it at the next review rather than mid-week on an hourly move.
What sets this case apart
The decision tests a rebalancing rule that mechanically adds to a falling asset, not a call on BTC's direction.