These counts describe the designed scenario mix. They do not measure real-world model accuracy.
2,000-case formula stress test
Simulated scenarios · not dealer-verified
See what happens when repair costs move.
AvLu’s Outcome Simulation Lab runs 2,000 complete synthetic repair packets through the estimate, variance, and protected-offer math without presenting modeled results as real dealer evidence.
Need the complete structured file? Download JSON.
Planning and product demonstration only. These are not invoices, repair orders, predictive-accuracy results, or purchase approvals.
Complete synthetic packets
Every simulation carries the full calculation trail.
Each case is complete enough to exercise the interface and formula, while its synthetic source prevents it from being promoted as dealer-verified evidence.
Vehicle identity
Year, make, model, and an unmistakable synthetic vehicle ID-never a plausible VIN.
Repair scope
A simulated repair date, scope description, parts estimate, hours, rate, and labor estimate.
Closeout costs
Simulated parts and labor closeout values with a reconciled total.
Variance
Dollar and percentage movement from the AvLu planning estimate.
Formula impact
The same variance flows directly into a revised protected maximum.
Source boundary
The source is always AvLu’s deterministic generator, not a dealer, mechanic, quote, or invoice.
Designed stress patterns
Six ways the cost stack can move.
The library is intentionally balanced across adverse, favorable, and mixed movements. That makes it useful for interface demonstrations and formula QA, not for claiming a success rate.
Loading scenario distribution…
Interactive outcome explorer
Inspect the estimate-to-closeout math.
Filter the 2,000 scenarios, choose a record, and follow every dollar into the protected-offer adjustment.
Repeatable inputs and formula outputs
Identity, date, scope, cost, source, and impact
No synthetic row passes a real evidence gate
| Case | Vehicle and scope | AvLu estimate | Simulated closeout | Variance |
|---|---|---|---|---|
| Loading simulation records… | ||||
Interpret the results correctly
Simulation is not validation.
These cases answer “does the math and interface behave under varied inputs?” They do not answer “does AvLu predict actual repair outcomes?”
- Parts and labor reconciliation
- Variance direction and percentage math
- Protected-offer sensitivity
- Interface behavior across varied cost stacks
- Demonstration and interview scenarios
- Real-world predictive accuracy
- Dealer or mechanic acceptance
- A dated external estimate or final invoice
- Title, condition, transport, or market proof
- Purchase approval or guaranteed profit
DEALER VALIDATION UNDERWAY
The next proof is external.
A completed real-world outcome still requires the same vehicle identity, dated repair evidence, attributable source, repair scope, parts and labor, estimate, closeout, variance, and formula impact.
See the dealer evidence campaignBring a real repair packet
Turn the next simulation assumption into external proof.
The simulation lab demonstrates the workflow. A permissioned dealer or mechanic packet validates the outcome.