The stable, cacheable answer for a property — what reminder engines re-check with If-None-Match (a 304 costs us nothing; the ETag changes only when schedule content changes, e.g. a bank-holiday reschedule). property_token is the service-issued property_id without its internal p: namespace marker; logs treat both forms as personal data. Old p: path values permanently redirect to the prefix-free form.

Stale-while-revalidate: a stale stored schedule is served as-is (its retrieved_at is the honest staleness signal) while a refresh happens in the background — staleness is NEVER a 404. 404 no_schedule means only "we have never answered for this property" — create a lookup.

This representation is intentionally address-free. A property_id is not authentication, so the exact council-rendered address is returned only inside the private, no-store Lookup resource.