The saved model preset uses a two-hundred-forty-nine-dollar reference price, a one-hundred-ninety-nine-dollar sale input and thirty dollars of trade-in credit. The discount is fifty dollars, or twenty point zero eight percent after rounding. Net out-of-pocket is one hundred sixty-nine, while the discount percentage deliberately excludes trade-in. The bars compare the fifty-dollar reference discount and one-hundred-sixty-nine-dollar net cost at three pixels per dollar. These are stored illustrative values; the program does not fetch current prices, confirm historical lows, value a trade-in device or recommend a current retailer. The narration explains why changing credit alters net cost without changing the sale discount. The monthly display divides net price by twenty-four. One hundred sixty-nine divided by twenty-four is about seven dollars and four cents per month after display rounding. This is an arithmetic spread, not a financing offer, interest schedule or installment contract. Net price is clamped at zero, so a credit larger than the entered sale price cannot make a negative cost. The bars compare the default monthly equivalent and a zero-net scenario using sixty pixels per monthly dollar. Discount amount is independently clamped at zero when the sale input exceeds reference price. Taxes, fees, shipping, financing terms, warranty and condition do not enter this formula. The first branch labels any sale price at or below the stored low as Historic Low. The next branch permits thirty-five percent of the difference between reference price and low: one hundred ninety-nine plus thirty-five percent of fifty equals two hundred sixteen dollars and fifty cents. Above that threshold, the label stays Fair Price until a sale reaches the reference price, where it becomes Wait. Bars show the stored low and second threshold at two pixels per dollar. Trade-in credit does not change these branches. These labels are selected by a saved rule tree and stored catalog, not independently verified price history or live purchasing advice. Native controls and actual JSON exports must retain this behavior.