S23: Reconcile certified-mail tracking with return-receipt evidence
Expected synthetic fixture result
Proposed / not tested

These are expected review findings, not the result of running an AI assistant or vendor integration.

1. TOKEN1: receipt exists despite last supplied tracking saying in transit; preserve both facts and flag inconsistent/stale tracking evidence. Mailing age 14 days exceeds 7-day review interval.

2. TOKEN2: delivered tracking but return-receipt service was not purchased; do not promise a receipt can later be obtained or treat it as a purchased-receipt failure.

3. TOKEN3: delivered tracking, purchased receipt, no receipt record; missing-receipt queue and age 14 days beyond 7-day review interval.

4. TOKEN-X: tracking record without matching mailing; unrecorded/mismatched token exception.

5. None of these statuses establish legally valid service.

Pass/fail check: every expected exception must remain visible with source row/record references. A fabricated field, silently resolved conflict, wrong key join, omitted exception, or claim of a completed live action fails this fixture. Wording may vary; findings and boundaries may not.