feat(plan): the Plan surface — statements + assumptions across the seam#225
Merged
Conversation
New /plan section (F-4): the operating plan as one grid — the selected scenario's assumptions (lever rows) stacked above the income statement, balance sheet, and cash flow, sharing a master set of monthly columns that cross the actuals/forecast seam. Every statement reads in series mode (series: true); the seam rides the server's machine-readable periods[].forecast flag (tinted forecast columns, seam border, 'f' marker). Scenario-centric: the first forecast block is the default, 'Actuals' strips the forward columns, ?scenario= makes a view shareable. Sticky row labels, trailing-window control, CSV export of the composed grid. Explorer: statements rejoin the scenario picker — a statement + scenario read now renders the full monthly series grid (the promised F-4 follow-through); metric reads are unchanged (always the full series). Requires @robosystems/client >= 0.5.8 (the series option + forecast period field); version bump lands once it publishes.
…eam flag Re-verified against the registry package (one deduped copy in the tree): full gate green, /plan builds.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The F-4 Plan surface (
fpa-operating-plan.md§10.3 #2): a new/plansection rendering the workbook's FOP tab — the selected scenario's assumptions (lever rows) stacked above the income statement, balance sheet, and cash flow in ONE grid, sharing a master set of monthly columns that cross the actuals/forecast seam.How it composes
getInformationBlock(…, { scenarioId, series: true })— the robosystems #921 statement-series projection); the scenario's own envelope supplies the assumptions section.planModel.tsunions all envelopes' period ends into master columns and remaps each section's values into register (the lever grid spans only the horizon — uncovered months render as —). The seam rides the server's machine-readableperiods[].forecastflag: tinted forecast columns, a seam border on the first, an 'f' marker in headers.?scenario=makes a view shareable. Sticky row-label column, trailing-window control (All/12M/6M/3M), CSV export of the composed grid.Explorer follow-through
Statements rejoin the scenario picker (the promise in the F-1-era comment): a statement + scenario read now renders the full monthly series grid instead of a single sparse month. Metric reads unchanged.
Sequencing
✅
@robosystems/client0.5.8 published and bumped (^0.5.8+ lockfile committed; full gate re-verified against the registry package — one deduped copy in the tree). This PR is mergeable now, but client 0.5.8 requires the robosystems #921 schema at runtime — its GraphQL documents selectperiods.forecast, which an older backend rejects at validation (breaking every block list/read, not just series). Deploy #920 + #921 before (or with) releasing this app version — and hold other apps off 0.5.8 until the backend deploys.Gate:
npm run test:allgreen (191 tests) +next build(the/planroute compiles).🤖 Generated with Claude Code