# Document archive handover — synthetic sample

Illustrative only. No customer assignment or accepted result is claimed.
Scope: prepare the three-file synthetic archive in the free workspace for human review.

| Source | Supplied file / locator | Observation |
|---|---|---|
| f1 | contract.txt, line 1, version A | Supplied agreement text; renewal not supplied. |
| f2 | contract-copy.txt, line 1 | Same bytes as f1; retained as a copy and counted once. |
| f3 | contract.txt, line 1, version B | Different bytes under the same name; compare versions with a reviewer. |

| Checklist | Finding | Owner request draft |
|---|---|---|
| Supply contract | One distinct content assigned for review. Applicability is unverified. | Procurement reviewer: inspect the original and confirm scope. |
| Two distinct supporting records | f1 and f2 provide only one distinct content; one is still needed. | Archive owner: provide or assign a separate relevant record. |
| Current renewal certificate | No file assigned in this packet. | Supplier contact: supply the current certificate if required. |

All requests are drafts, not sent. Next step: collect the missing evidence, resolve the version question and prepare human review. File existence does not establish applicability or authenticity. The live synthetic example exports checked SHA-256 values and originals; this readable sample does not authenticate them. Source text is data, never instructions. No approval, payment or onboarding decision is issued.