# LineUp France - Prod Validation Triage Matrix

## Goal

Give the team a fast decision aid during production validation when a failure is observed.

## Severity levels

### Critical

Use `Critical` if one of these is true:
1. core mission flow is blocked
2. payment or wallet is inconsistent
3. more than one liner can effectively win the same mission
4. production data integrity is at risk
5. the issue directly invalidates the release decision

Action:
- stop validation on that flow
- classify provisional result as `NO-GO candidate`
- capture evidence immediately
- escalate to tech + product + ops

### Major

Use `Major` if:
1. main flow still works but with significant degradation
2. workaround exists but is not acceptable long term
3. one major screen or sync point is broken without full data loss

Action:
- continue validation only on unaffected flows
- log owner and workaround
- decision can still become `NO-GO` depending on business impact

### Minor

Use `Minor` if:
1. issue does not block the critical path
2. workaround is simple and safe
3. no payment / wallet / mission ownership risk exists

Action:
- continue validation
- log it as accepted or backlog candidate

## Failure matrix

| Failure observed | Default severity | Immediate action | Likely owner |
| --- | --- | --- | --- |
| Client can pay without deterministic liner selection | Critical | stop finance flow, mark NO-GO candidate | backend + product |
| Two liners remain accepted for same mission | Critical | stop validation, capture BO + client evidence | backend |
| Chosen liner cannot start mission | Critical | stop mission flow | backend + liner_app |
| Chosen liner cannot complete mission | Critical | stop mission flow | backend + liner_app |
| Wallet not credited after queue processing | Critical | verify queue, finance records, stop payout validation | backend + ops |
| Mission shows wrong location in prod | Critical | stop geoloc validation, capture coordinates and screenshots | backend + mobile |
| Payment succeeds but BO data mismatches mission | Critical | stop finance validation | backend |
| Chat fails but mission flow still works | Major | continue mission validation, log issue | backend + mobile |
| Proof upload fails but mission can still complete | Major | continue with evidence gap noted | backend + mobile |
| Notification missing but action visible in app | Major | continue core flow, log device + payload | backend + mobile |
| Cosmetic UI deviation only | Minor | continue validation | mobile |

## Recommended diagnostic order

### If the issue is finance-related
1. confirm mission id
2. confirm chosen liner id
3. inspect payment record in BO
4. inspect wallet / payout state
5. inspect queue processing

### If the issue is mission-state-related
1. confirm mission current status in BO
2. inspect timeline / status events
3. compare client track vs liner track
4. verify chosen liner ownership

### If the issue is geolocation-related
1. capture displayed address
2. capture displayed coordinates if available
3. compare client app, liner app, BO
4. verify mission source address used at creation

### If the issue is notification-related
1. identify sender action
2. identify expected recipient
3. check in-app notification center
4. check device push reception
5. compare payload type / mission id

## Decision shortcuts

### Immediate NO-GO candidate
If any of these is observed:
1. multi-candidature integrity broken
2. payment/settlement integrity broken
3. liner cannot run mission lifecycle
4. geolocation materially wrong on live mission

### Continue-with-logging only
If all are true:
1. issue is non-blocking
2. workaround is safe
3. no finance inconsistency
4. no mission ownership inconsistency

## Required evidence for every critical issue

1. timestamp
2. mission id
3. user account used
4. screenshot or recording
5. BO state screenshot
6. exact expected vs actual
7. provisional owner

## References

- `docs/qa/prod-e2e-run-sheet.md`
- `docs/qa/prod-validation-evidence-log-template.md`
- `docs/qa/final-go-no-go-decision-template.md`
