# LineUp France - Prod Validation Owner Matrix

Use this file during production validation to know who should take ownership first when a failure is observed.

## 1. Roles

### Product

Owns:
1. release decision impact
2. business acceptability of workarounds
3. final arbitration on accepted non-blocking issues

### QA

Owns:
1. evidence collection
2. expected vs actual traceability
3. run sheet execution discipline
4. GO / NO-GO preparation inputs

### Backend / BO

Owns:
1. mission state transitions
2. multi-candidature integrity
3. payment and wallet logic
4. proof and KYC backend flows
5. notification payload correctness

### Mobile Client

Owns:
1. client mission flow rendering
2. client payment UX
3. client track / messages / notifications UX
4. client geolocation display issues

### Mobile Liner

Owns:
1. liner mission acceptance and tracking UX
2. liner proof flow UX
3. liner wallet / withdrawal UX
4. liner notifications UX

### Ops / Infra

Owns:
1. deployment state
2. cPanel / webserver behavior
3. queue runtime behavior
4. storage and environment configuration
5. domain / routing / PATCH-DELETE passthrough

## 2. First owner by incident type

| Incident type | First owner | Secondary owner | Escalate immediately if |
| --- | --- | --- | --- |
| Multi-candidature broken | Backend / BO | Product | two liners can effectively win |
| Payment does not confirm chosen liner | Backend / BO | Product + Ops | money state is inconsistent |
| Wallet not credited | Backend / BO | Ops | queue already processed and still wrong |
| Withdrawal fails | Backend / BO | Ops | payout state mismatches BO |
| Mission cannot start/finish | Backend / BO | Mobile Liner | backend state and app state diverge |
| Chat/message issue | Backend / BO | Mobile Client / Mobile Liner | both apps fail on same mission |
| Proof upload issue | Backend / BO | Mobile Liner | file stored state is unclear |
| Geolocation mismatch | Mobile + Backend | Product | live mission is materially wrong |
| Push not received | Backend / BO | Mobile + Ops | in-app center and device push both fail |
| PATCH/DELETE rewritten or web errors | Ops / Infra | Backend / BO | any 405/GET rewrite in prod |

## 3. Escalation triggers

### Escalate to Product immediately when
1. issue can change GO / NO-GO
2. workaround changes user promise or mission fairness
3. payout or payment trust is affected

### Escalate to Ops immediately when
1. queue behavior is suspect
2. storage or file URLs fail
3. domain / routing behavior is inconsistent
4. webserver rewrites methods incorrectly

### Escalate to Tech lead immediately when
1. root cause is unclear after 10 minutes
2. issue crosses backend + mobile + infra boundaries
3. data integrity may be compromised

## 4. Working rule during prod validation

1. QA logs the issue first
2. first owner is assigned immediately
3. one person investigates, one person keeps the run moving if possible
4. product decides whether to continue or pause the flow
5. every critical issue gets an owner, timestamp, and next action

## 5. Minimal incident note format

```text
Time:
Step:
Observed issue:
Expected behavior:
Severity:
First owner:
Secondary owner:
Decision now:
Next update in:
```

## References

- `docs/qa/prod-validation-pack-overview.md`
- `docs/qa/prod-validation-triage-matrix.md`
- `docs/qa/prod-validation-evidence-log-template.md`
- `docs/qa/final-go-no-go-decision-template.md`
