Private Wealth Advisory
Query the advisory REST API at $API_BASE (or the URL the harness provides) to
fetch client records, source documents, retirement accounts, life-insurance
policies, trust candidates, tax policy constants, and RMD factors. Resolve
conflicting source data, compute key financial projections, and return a single
JSON object that matches the answer template supplied in the task payload.
Quick Start
- Read the request memo in the task payload for the client ID, engagement type, and any horizon year.
- Read the answer template (
answer_template.json) to understand every required key and its type. - Fetch all relevant API data for the client. Every list endpoint returns an
array; filter by
client_id. Global endpoints (/api/policies/tax,/api/rmd-factors) return single objects used across all clients. - Resolve conflicting source documents following Source Resolution.
- Route to the analysis procedure that matches the
analysis_typein the template: see Analysis Types. - Build the JSON response using resolved values and computed numbers. Return only the JSON object; no prose outside it.
API Reference
Every endpoint except the portal is JSON. See API Reference for full response shapes, field meanings, and filtering patterns.
GET /api/clients— List all clients.GET /api/clients/{client_id}— Single client record.GET /api/source-documents— All source documents (CRM notes, attorney memos, signed profiles). Filter byclient_id.GET /api/retirement-accounts— All IRA/retirement account records. Filter byclient_id.GET /api/life-insurance— All life-insurance policies. Filter byclient_id.GET /api/trust-candidates— All trust candidate cases. Filter byclient_id.GET /api/policies/tax— Global tax-policy constants (one object). Always fetch this.GET /api/rmd-factors— Global RMD life-expectancy factor table (one object keyed by age as string). Always fetch this.
Source Resolution
The advisory environment may deliver conflicting facts for the same client because records were imported from different systems at different times. Always resolve conflicts before computing. See the detailed hierarchy in Source Resolution.
Quick rule: Among source documents, prefer SIGNED_PROFILE (most
recent, signed by the client), then ATTORNEY_MEMO, then CRM_NOTE
(= stale marketing import). For account balances, CUSTODIAN_EXPORT is
authoritative. Where the analysis asks for a controlling source field,
record the source type that actually supplied the dominant facts.
Analysis Types
Four analysis types appear in the evidence. Each has its own calculations and output shape. Follow Analysis Types:
- roth_conversion_rmd — Staged Roth conversion plan with RMD tax projections and legacy balance estimates.
- ilit_crummey_implementation — ILIT funding-cycle check covering gift-tax exclusion capacity, Crummey notice timing, and estate-inclusion risk.
- trust_comparison — GRAT versus CRAT numerical comparison with estate-context and a client-specific recommendation.
- estate_liquidity_action_plan — Combined ILIT plus trust-transfer plan with action-set sequencing and liquidity-gap analysis.