feat: Roth · IRMAA planner tab (PlanningContract v1.0.0 composite)#3
Merged
Conversation
A new pwplan-core tab for the composite multi-year Roth-conversion analysis, where the binding constraint is IRMAA (Medicare surcharges), not the tax bracket. - src/contract/roth-conversion.ts: UI-side mirror of the case contract (@protocolwealthos/planning-contract / nexus-core JSON-Schema), versioned separately as PLANNING_CASE_CONTRACT_VERSION = 1.0.0. PII-free invariant enforced by roth-conversion.test.ts. - analyzeRothConversion gateway method: PII-free transport, opaque case_id generated at dispatch, envelope-version checked. - RothIrmaaPlannerTool: contract-typed form + results. Per year: recommended amount under fill-to-22 / fill-to-24 / just-under-IRMAA (crosses-cliff flag), IRMAA cliff cost, incremental federal + state tax, NIIT + LTCG deltas, breakeven, binding constraint; plus the multi-year roll-up and the do-nothing RMD drag. The projected-IRMAA-with-buffer assumption is a prominent fiduciary disclosure banner, not fine print. - validateRothIrmaa + store slice + App tab. - typecheck / lint / format / 185 tests / build all green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Nick Rygiel <nick@protocolwealthllc.com>
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.
Intent
Add a "Roth · IRMAA" tab for the composite multi-year Roth-conversion analysis, where the binding constraint is IRMAA (Medicare surcharges), not the tax bracket.
Scope
src/contract/roth-conversion.ts(UI-side mirror of the case contract —@protocolwealthos/planning-contract/ the nexus-core JSON-Schema — versioned separately asPLANNING_CASE_CONTRACT_VERSION = 1.0.0),RothIrmaaPlannerTool.tsx(form + results).planning-gateway.ts(+analyzeRothConversion, PII-free, opaquecase_idat dispatch),tool-validation.ts(+validateRothIrmaa),store/scenario.ts(slice),App.tsx(tab).Test plan
typecheck / lint / format / 185 tests / build all green. Engine side in nexus-core (
analyze_roth_conversion); the tab works once that deploys.Compliance notes
PII-free contract by construction;
assertNoPIItripwire +auditCallseam unchanged. "Software, not investment advice" disclaimer retained; the projected-tier assumption is surfaced as a fiduciary disclosure.Handoff
Cross-repo ABI:
shared/architecture/roth-irmaa-planning-abi.md.🤖 Generated with Claude Code