Financial claims must be traceable to tested results

Dates, balances, interest, payments, payoff order, milestones, savings, and strategy rankings must come from the tested deterministic engine. Interface components and editorial copy do not calculate or alter those values.

Tests use concrete expected values for financial behavior. Changes to engine rules require specification updates, focused regression tests, and full validation before release.

Content describes what a modeled input changes. It avoids personal recommendations, guarantees, approval predictions, affordability claims, and instructions to purchase a lender or financial product.

Calculator pages state material assumptions and limitations. They distinguish an educational estimate from a lender statement or payoff quote.

The optional AI explanation does not calculate financial results. It receives a narrow validated summary only after explicit consent and may explain existing deterministic output in plain language.

AI output is schema-validated and checked against the deterministic number allowlist. Invalid, unavailable, or numerically unsafe output is rejected, and the calculator remains available without AI.

Material methodology and privacy changes require an updated review date. A review verifies the published description against the current source, tests, and application behavior.

When an error is confirmed, the source statement and its supporting test or documentation are corrected together. Historical review notes remain in the repository task record.