Drift SpoonA little closer
to target.
Holdings move. Your reference stays.
Measure the gap, then make a plan you can take back.
One currency. Your prices.
No orders. No live feed.
Start with your holdings, or load a clearly labelled synthetic example.
Target
% of portfolioSet the weights you want to maintain.
Deviation
The distance between now and your reference.
Current
% of portfolioAdd quantities and prices to measure it.
Your assumptions
All quantities are fractional. Enter every price in the same currency. Cash is a separate asset, priced at 1.
Threshold uses percentage points. Fees apply to each included trade.
Cash held back = the larger of your cash target value and cash floor.
Adjustment plan
No plan yetYour plan will open here. Generating one never changes your holdings.
Version notebook
Keep up to 8 local snapshots to compare fee scenarios. Saved versions remain estimates, including when revoked.
Small moves.
Explicit assumptions.
What the plan calculates
Value = quantity × price. Weight = value ÷ total value. Deviation is current weight minus target, in percentage points. Overall drift is half the sum of absolute deviations, including cash.
We sell eligible overweight positions first, then allocate available cash proportionally to eligible underweights. Each included trade pays notional × fee basis points ÷ 10,000 + fixed fee. Small trades are removed. This is a deterministic heuristic, not an optimal portfolio solver.
Where the estimates stop
Prices are your inputs, held constant through the plan. There is no live data, order routing, tax, slippage or market impact model. Desired amounts use the initial total; final weights use the total after fees. Residual drift can remain or increase. No return is predicted or guaranteed.
Why an application token?
Drift Spoon Plans is a proposed application token for portable access to independent cost engines and team review services, with contribution records attached to plan versions. A shared access layer could connect those services across applications.
No token has been issued and no token is needed here. Local calculation, version comparison and exports work directly. Remote attestation and token-based service access are not connected.