Docs · Model reference
divorce
Verified · spec v1.1.0Inputs
| Field | Type | Valid domain |
|---|---|---|
| combinedAssets | float | 50,000 – 5,000,000 |
| combinedDebt | float | 0 – 1,000,000 |
| homeValue | float | 0 – 3,000,000 |
| homeMortgageBalance | float | 0 – 2,000,000 |
| retirementAssets | float | 0 – 3,000,000 |
| splitRatio | int | 0 – 100 |
| yourCurrentIncome | float | 1,000 – 30,000 |
| alimonyMonthly | float | -5,000 – 5,000 |
| childSupportMonthly | float | -3,000 – 3,000 |
| legalFees | float | 5,000 – 150,000 |
| yourAge | int | 25 – 65 |
| yearsToRetirement | int | 1 – 40 |
| annualReturnRate | float | 3 – 12 |
- annualReturnRate is in PERCENT points (e.g. 7 = 7%), not a decimal
All fields required. Out-of-domain values are rejected with per-field errors — never clamped. Unknown fields are rejected.
Sentinel values
breakEvenAge=99→ sentinel offset: breakEvenAge = yourAge + 99 when the monthly surplus is 0
Responses annotate these in a sentinels array with a triggered flag per run.
Live example — generated from the real engine
Request
POST /api/v1/models/divorce
{
"combinedAssets": 2525000,
"combinedDebt": 500000,
"homeValue": 1500000,
"homeMortgageBalance": 1000000,
"retirementAssets": 1500000,
"splitRatio": 50,
"yourCurrentIncome": 16000,
"alimonyMonthly": 0,
"childSupportMonthly": 0,
"legalFees": 78000,
"yourAge": 45,
"yearsToRetirement": 21,
"annualReturnRate": 7.5
}Response (chart arrays compacted)
{
"ok": true,
"model": "divorce",
"specVersion": "1.1.0",
"contractUrl": "/api/v1/models/divorce",
"specUrl": "/api/v1/models/divorce/spec",
"inputs": {
"combinedAssets": 2525000,
"combinedDebt": 500000,
"homeValue": 1500000,
"homeMortgageBalance": 1000000,
"retirementAssets": 1500000,
"splitRatio": 50,
"yourCurrentIncome": 16000,
"alimonyMonthly": 0,
"childSupportMonthly": 0,
"legalFees": 78000,
"yourAge": 45,
"yearsToRetirement": 21,
"annualReturnRate": 7.5
},
"outputs": {
"yourNetAssets": 934500,
"yourRetirementShare": 750000,
"yourHomeEquityShare": 250000,
"yourDebtShare": 250000,
"monthlyIncomeAfterObligations": 16000,
"monthsToRebuildEmergencyFund": 30,
"projectedRetirementAt65": 5374076.337062095,
"projectedRetirementWithoutDivorce": 4886764.740188517,
"retirementGap": -487311.5968735786,
"breakEvenAge": 47,
"yearlyData": [
{
"year": 2026,
"savings": 844650,
"cumulativeCost": 78000
},
{
"year": 2027,
"savings": 946399,
"cumulativeCost": 78000
},
"… 20 more"
]
},
"sentinels": [
{
"field": "breakEvenAge",
"value": 99,
"meaning": "sentinel offset: breakEvenAge = yourAge + 99 when the monthly surplus is 0",
"triggered": false
}
],
"assumptions": [
"Implements model spec divorce v1.1.0 (dual-implementation verified).",
"annualReturnRate is in PERCENT points (e.g. 7 = 7%), not a decimal"
],
"facts": [],
"record": {
"sha256": "373d504dd54e03cbf67c37feb6d2acfe1edeb6c4682405a2f0540152a3e1574f",
"fields": [
"model",
"specVersion",
"inputs",
"outputs"
],
"howToVerify": "Store this record with any advice or agent output built on these numbers. To verify later: build {model, specVersion, inputs, outputs} from the stored response, serialize as JSON with object keys sorted recursively (no whitespace), and SHA-256 it — a match proves the numbers came from this spec version with these inputs, unaltered."
},
"disclaimer": "Illustrative planning model, not financial advice. Outputs follow the published model spec exactly; read the spec for assumptions and exclusions before relying on any number."
}This example is executed against the production engine when the page builds — it cannot drift from the API's real behavior.