Goldcrest: Conversational State to Monte Carlo Parameters A developer built Goldcrest, a household financial planning tool that replaces spreadsheet forms with a chat interface, where an LLM extracts income, expenses, assets and timeline assumptions and passes them to a deterministic Monte Carlo engine. The architecture keeps the model away from arithmetic: it extracts structured fields, a validation layer enforces type, range and consistency constraints, and a server-side parameter store pseudonymizes data before it reaches the LLM. A two-pass extraction approach asks follow-up questions only for low-confidence fields, and conflicting inputs across turns are flagged for the user to resolve. Goldcrest is a household financial planning tool that replaces spreadsheet forms with a conversational interface. You answer short questions in a chat. The agent extracts income, expenses, asset values, and timeline assumptions, then feeds them into a Monte Carlo simulation that projects your financial trajectory across thousands of market paths. The interesting plumbing is the boundary between the LLM-driven conversation layer and the deterministic financial engine. The agent must maintain dialogue state across multiple turns, validate inputs, resolve ambiguity, and serialize a complete parameter set without letting the LLM touch arithmetic or generate advice. The system splits into three layers: The agent never performs calculations. It extracts values and categories from user responses, writes them to the parameter store, and hands off to the engine. The engine produces every number in the projection. User input natural language ↓ LLM extracts structured fields ↓ Validation layer type checks, range constraints, consistency rules ↓ Parameter store server-side, pseudonymized for LLM calls ↓ Monte Carlo engine deterministic, no LLM involvement ↓ Year-by-year projections + probability distributions The LLM sees pseudonymized data when it needs context for follow-up questions. Actual dollar amounts and identifiable details stay on the server. The model receives tokens like