Use only after an expert names the source, acceptance rule, and record owner.
AvLu authority map
Trust the source before you trust the number.
“Authority” means the source the industry accepts for a specific decision. AvLu needs a defensible chain from the vehicle, to the repair estimate, to the final actual cost, without turning marketplace listings or simulations into outcomes.
Same vehicle
Dated source
Visible scope
Permissioned use
Current evidence status
500marketplace evidence rowsScreening evidence
500synthetic outcome packetsFormula stress tests
30open dealer-validation leadsOutreach campaign
9 / 9fields required per completed casePromotion gate
Marketplace records show what was publicly listed. Synthetic packets show how the formula behaves. Neither is a dealer-verified repair outcome.
The source map
One decision chain. Three different kinds of authority.
A credible dealer case must connect the same vehicle and repair scope across every layer. A strong source in one layer does not automatically prove the others.
Current state: a possible source is visible, but expert confirmation is still pending.
No defensible source has been identified. The case cannot be completed.
Layer 01Identity authority
Candidate · Authority review pending
Is this the same vehicle?
The identity source ties the evidence to one vehicle, not merely a similar year, make, or model.
- Candidate sources
- VIN record, stock record, title record, OEM or accepted vehicle database
- Minimum fields
- VIN or accepted identifier, year, make, model, source, capture date
- Failure signal
- Partial VIN, conflicting trim, unmatched vehicle, or unattributed screenshot
Layer 02Repair authority
Candidate · Authority review pending
What should the repair cost?
The repair source makes the scope, parts, labor, rate, assumptions, exclusions, and date visible.
- Candidate sources
- Labor guide, OEM procedure, parts quote, inspection, shop estimate, dealer service department
- Minimum fields
- Dated scope, parts, labor time, labor rate, total, and named source
- Failure signal
- Round-number allowance, unknown provider, no scope, or no parts-and-labor breakout
Layer 03Outcome authority
Candidate · Authority review pending
What did the repair actually cost?
The outcome source proves the final authorized or completed amount and preserves any change in scope.
- Candidate sources
- Final repair order, paid invoice, dealer closeout, or attributable written outcome summary
- Minimum fields
- Same vehicle, final scope, parts, labor, actual total, date, source, and permission status
- Failure signal
- Verbal recollection, different vehicle, estimate-only document, or missing closeout amount
The acceptance test
A source earns authority by surviving six questions.
Source reputation matters, but the record still has to be vehicle-specific, dated, attributable, complete enough to audit, and usable with permission.
Identity
Does it tie to the same VIN or accepted vehicle record?
Date
Can the timing of the estimate or outcome be established?
Scope
Does it state what was inspected, estimated, authorized, or completed?
Cost detail
Are parts, labor, rate, total, and meaningful exclusions visible?
Attribution
Can the shop, dealer, estimator, system, or document owner be named?
Permission
Is private, anonymized, or named use explicitly understood?
Quote-backed recon
The recon quote is not a footnote. It changes the deal.
AvLu keeps the quote amount, source, scope, parts, labor, date, and formula impact together. If the documented recon total rises, the protected maximum falls by the same amount when every other input stays fixed.
ProviderEvidence dateRepair scopePartsLaborWritten total
Compare a written quote in Dealer Validation →
Authority review canvas
Capture the authority stack while the expert is in the room.
These notes stay in this browser page until you copy or print them. Nothing is submitted, stored, or sent by AvLu.
Meeting objectiveName the accepted source at each layer and one path to a real case.
Local-only notes · all authority badges pending
This canvas does not change the public badge state or submit evidence. It prepares the exact notes needed for a reviewed update after the meeting.
Four questions to ask directly
- Which source do dealerships accept for labor time, repair method, and rate?
- Which written estimate or repair record is strong enough to support a vehicle-specific decision?
- Which final record proves the actual parts, labor, and total?
- Who controls permission for private review, anonymous use, or named publication?
Ready for meeting notes.
Case promotion gate
No completed label before every field is present.
A completed dealer case must contain the real evidence and the comparison math. If one item is missing, the record stays an open lead.
VIN or accepted identity source
Attributable written record
Work, condition, and exclusions
Amounts, time, rate, and total
Shop, estimator, dealer, or system
Pre-closeout planning amount
Written or final closeout amount
Dollar and percentage movement
Effect on the protected maximum
500 marketplace rows, 2,000 synthetic scenario packets, release checks, and visible evidence gates.
Useful for interface and formula testing. Not predictive accuracy and not dealer outcomes.
30 validation leads remain open until a real record reaches 9 of 9 with permission.
The immediate milestone
One dated estimate-to-actual repair packet.
Name the authority stack, identify the record owner, and open one credible evidence door.