Put a cash forecast YOU computed onto the forecast card.

This tool measures nothing. It takes the settled month-end series, the anchor, the burn and the projection you computed, and returns them for rendering. Call it only after you have computed both halves yourself: the month-end totals under your cash scope, and the burn under your stated policy. Never call it to "get" a forecast.

The projection is WORST CASE: no revenue arrives, and cash declines by the burn each month until it reaches zero, where it stops. Take the anchor and the burn each to the cent, then each point is max(0, anchor − k × burn) for the k-th month after the anchor. The tool re-derives every point from the anchor and burn you state here, in cents.

The card draws the series, the anchor clause and the worst-case caveat. The cash scope, the burn policy and partial are REQUIRED and reach no pixel. All of it comes back in this tool's text result, which is what you write the prose from.

REQUIRED:

• currency, and as_of: the full ISO time of the balances read the series came from

• actuals: one { month, amount } per month, oldest first, ending on the last month that has ended at as_of (UTC). A month no account covered is null, never 0, and it stays in the list.

• anchor: { month, amount, basis }. closed_month_end is the latest settled month-end in actuals. current_position is today's cash when no month has a settled total. It sits on the grid at the last actual month.

• burn: the POSITIVE monthly magnitude, its currency, trailing_months, and the window it averaged (from inclusive and to exclusive, each YYYY-MM-01). The window ends with the last actual month.

• months_forward (at most 12), and projection: one { month, amount } per projected month. When the anchor sits before the last actual month, the months between are projected too, so months_forward must reach past them.

• cash_scope: the counted account types, whether unknown ownership was counted, anchor_missing_accounts (counted accounts with no reading at a closed-month anchor; 0 under current_position), and the four exclusion groups

• burn_policy: the elected convention and its counts, the exclusions (internal_transfers is the sum's excluded_multi_leg, unreadable_rows its malformed rows), and unplaceable_count (the sum's excluded_no_owned_leg)

• partial: the forecast's own floor, which is WIDER than a cash total's is_floor. It is checked against cash_scope and must be true exactly when an account was left out with no readable balance, no rate, OR no reading at the anchor month — that last one is the forecast's alone, and a caller that forwards its cash total's is_floor unchanged is refused on it. It never means a cut-short read: a cut-short balances read or sum stops the run before this call.

REFUSED rather than rendered, each because your own figures disagree:

• a projection point that is not max(0, anchor − k × burn) within a cent

• a projection that does not start the month after the anchor, skips a month, continues after a zero, or has the wrong length

• a projection ending on a month that has already ended. The refusal names which of the three causes fired: the cash ran out (report that), the horizon was too narrow for the gap (widen it), or the gap exceeds every legal horizon (the feed is too far behind to project across)

• a cash currency that differs from the burn's

• a negative burn, a burn elected "magnitude", signed elected from no negative rows, or one of unplaceable_count and internal_transfers null without the other

• a closed_month_end anchor that is not the latest settled actual, or whose amount differs from it

• a current_position anchor beside a settled actual, off the last actual month, or with an account missing at it

• actual months out of order, repeated, skipped, or ending on any month but the last one that has ended at as_of

• a burn window that disagrees with trailing_months, or ends on a different month than the actuals

• a partial that disagrees with the floor your own cash_scope implies

• an as_of in the future

This tool renders its own chart card. Do not re-plot the series with a charting tool.

When the token authorizes one workspace, call this directly — no other tool call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.