Recon pressure path
A deal that is still viable, but only if the operator keeps parts, recon burden, and release pressure visible.
This scenario shifts the demo away from polished release and into the harder middle of the operating system where economics and timing pressure are still moving.
Why this scenario should exist
A credible platform demo has to prove that the system is built for pressure, not just for finished success states.
This scenario shows the operator why parts timing, recon proof, and weighted value need to stay linked.
Where the system shifts under this pressure.
Inspection + Recon
Inspection and recon convert surface impressions into structured repair, readiness, and merchandising truth.
Department laneParts Coordination
Parts is not a side note. It is a timing, economics, and release-governance lane inside the same deal packet.
Department laneFinance + Desk
The desk turns packet truth into release-ready structure: lender positioning, margin logic, and controlled promises.
How the workspace should respond.
ETA and repair scope are still changing margin tolerance
Desk confidence is conditional, not final
The system needs to show risk without losing coherence