The screenshot and the contract share a clock

The client says the version they approved on the call didn't have that clause. The call was three weeks ago.

The review ran on a container desktop the client watched at ?readonly=true. At each milestone you hit GET /api/v1/display/screenshot; the display keeps every capture, and GET /api/v1/display/screenshots lists them with a timestamp_human. The contract lives in hoody-files, so every save is a journaled revision.

Two URLs settle it. GET /api/v1/display/screenshot/1749541160 shows what was on screen when they said yes. GET /api/v1/files/contract.docx?at=2026-02-23T16:57:02Z returns the file at that same second. ?diff&from_ts=2026-02-23T16:57:02Z shows exactly what changed since, clause included or not.

Screen and file were captured by different services, but they share one clock. The argument is a timestamp.

Screen and file were captured by different services, but they share one clock.