A 4th-percentile week on 1.75 times the prior 12-week volume forces a rebalance buy
Should the allocator let its scheduled rebalance restore the small crypto sleeve's target weight after this week's 14.04% fall, or cut the sleeve's weight first and buy back later?
The market facts are real; the decision maker is illustrative.
The week and the position
In the week of 1 June 2026, BTC fell from 73,674.39 to 63,332.01 (-14.04%), a return in the 4th percentile of 433 weeks, with a 25.30% range and a close in the lower third. Volume was 1.75 times the prior 12-week average. Three of the four prior weeks were down, and BTC is 49.74% below its 52-week high. The worst day was -6.51% on Tuesday, the best +4.02% on Sunday, and the largest hourly move was only -2.33%. ETH fell further, so the sleeve's second asset did not cushion it.
Judgment
The fall was a grind at elevated volume, not one crash hour: the largest 1h move was -2.33%, and the weekly return is extreme only relative to 433 weeks. With a small fixed sleeve, the cost of the week is already bounded by the sleeve's weight, while cutting now converts a rules-based allocation into a discretionary call near the 4th percentile. Keep the target weight, execute the scheduled rebalance, and accept that the close in the lower third and the volume spike may extend into another down week.
What would change it
If the fund's mandate sets a floor on sleeve drawdown that this week breached, the reduction becomes mandatory rather than discretionary. If BTC closes a later week below the 59,130.91 low, the target weight itself should be re-set before any rebalance.
What sets this case apart
This is about a rebalancing rule meeting its worst-percentile week, not about forecasting a bottom or sizing a leveraged position.