https://roadmap.acuityscheduling.com/schedule/ab65d60b

What was published

Custody — each question answered separately

• Does Junctiq hold the bytes? — Not provencontent not stored: object store did not verify the write (upload http 401)
• Does the origin still serve it? — ProvenRe-checked 2026-10-15 09:20Z: HTTP 200. The origin now serves different bytes; this capture is the record of what it served at 2026-09-18 22:31Z.
• Does any public archive hold it? — UnknownNever checked for this record: no archive-availability row exists for it.
• Is it independently reproducible? — Not measurableNo instrument compares these bytes with a copy Junctiq does not control, so this is not answered either way.
• Has what the publisher served changed since? — Not measurableThe bytes differ in 25 of 25 later captures, first at 2026-09-18 22:47Z. Differing bytes are not a publisher changing the page — many pages vary on every request — and the method licensed to say what was removed has not yet passed its own blindness check, so Junctiq does not say what, if anything, changed.

The record

SHA-256

45f8b83db286428f1e78b8de6f64d72dcd710edc992c27b7ed5e8da3eb95838e

Bytes

8,742

Captured

2026-09-18 22:31ZWhen Junctiq fetched these bytes — never the publisher’s date.

Published

The source did not state one.

HTTP

200 · text/html; charset=UTF-8

Retention

EXCERPT · retention-v0-2026-09-17Rule v0 is a draft (draft pending legal review). A reclassification would be a new capture under a new rule version, never an edit to this one.

Every capture of this page

Compared by digest only. “Differs” is a fact about bytes; it is not a finding that the publisher changed anything.

Provenance