# Stop Timeline — Synthetic Reviewer Pattern

**Synthetic times and opaque IDs. This timeline is not a provider trace.**

| Time (synthetic monotonic ms) | Event | Observed evidence | Interpretation |
|---:|---|---|---|
| 99,930 | `policy-v3` loaded | local fixture state | policy snapshot exists; does not prove later freshness |
| 99,960 | logical payment `lp-opaque-01` admitted | admission record | admitted under v3 |
| 99,980 | last confirmed dispatch before stop | local dispatch record | latest dispatch confirmed by this local evidence |
| 100,000 | stop requested | stop command record | request exists; enforcement not yet proven |
| 100,020 | local orchestrator receives stop | receipt record | control-plane receipt only |
| 100,050 | admission gate reports stop enforced | gate state | new admissions blocked from this boundary in fixture |
| 100,060 | queued objects inventoried | queue snapshot | local queued work identified |
| 100,070 | child stop requests sent | child-control records | acknowledgement/outcome still separate |
| 100,090 | in-flight object remains `Unknown` | inventory | no rollback/cancel inference |
| 100,400 | reconciliation check | synthetic evidence state | object remains open until independent outcome evidence |

## Timeline questions to record in a real review

- What clock produced each timestamp, and what is the clock uncertainty/skew?
- What exact layer observed the stop command?
- At what layer was enforcement actually demonstrated?
- What is the last dispatch independently confirmed before/after stop?
- Which queue, worker, child, signer, provider and rail are within coverage?
- Which effects were already signed, accepted, committed or settled?
- Which states are still `Unknown`, and who owns reconciliation?