THE PORTFOLIO — Allocation & Rebalancing OS Brain
THE PORTFOLIO — Allocation & Rebalancing OS Brain
For a long-term allocation you can actually hold. One orchestrator plus ten specialists that set target weights you can defend, rebalance on drift rather than on the calendar, and sequence the trades so tax does not eat the benefit.
Rebalancing on a fixed date is arbitrary. Rebalancing on drift bands is not, and it trades far less. The script takes your targets and current weights and returns the trades needed, but only for holdings that have actually breached their band, with the tax consequence attached to each. Rebalancing frequently inside a taxable account regularly costs more than the drift it corrects, which is why trades are ranked by benefit net of tax rather than by how far each holding has moved. The uncomfortable output is often that the correct action is nothing.
rebalance.py
Compares current weights to targets, triggers only on breached drift bands rather than dates, generates the required trades, and ranks them by benefit net of estimated tax so the trades that cost more than they fix drop out entirely. Every OS Brain in this drop carries its own executable component, so the judgement calls stay with you and the arithmetic stops being a matter of opinion. Runs anywhere Python runs, and the specialists still work on their own if you never open it.
Say it in plain words — it works out the rest
Inside · orchestrator + 10 specialists
Where it refuses to skip ahead
- No targets without an objective — an allocation copied from someone else has no way of being right for you.
- No rebalance without a breached band — calendar rebalancing trades for no reason and pays tax for the privilege.
- Use new contributions before selling — it corrects drift with no tax consequence at all.
- No plan without the drawdown paragraph — the plan you write during a fall is not a plan, it is a reaction.