Current schedule for a council's own property id (public feeds only)

Echo of the requested property id (mockup amendment 5) — clients should assert it matches what they asked for.

exact includes a citizen's own pick. street/postcode = council publishes at that granularity (notes explain). postcode_representative = a labelled same-postcode neighbour answer. It may follow explicit consent, measured evidence that permits automatic serving, or the narrower provisional interim gate. It is never presented as an exact-property result.

published_calendar = real dates the council publishes. council_projection = dates published by the council's own projected calendar, or one next date calculated by the service's bounded normal-weekday rule (holiday changes may be missing). Council-published dates are retained through the 92-day horizon; only the service's own calculation is limited to one occurrence. next_collection_only = nothing beyond the next date(s) exists — do not imply more is coming.

Separate from validity: next_only is concrete next date(s), limited_horizon is a valid incomplete slice, full_horizon was verified across the serving horizon, and weekday_only contains council-published weekday wording that could not safely be translated into dates. Weekday projections are limited_horizon and contain at most the next date for each collection type. A nearby UK bank holiday does not suppress that date; any explicit council exception the run saw takes precedence.

The level at which the council publishes the schedule evidence; separate from how the requested address was matched.

When we fetched this from the council (answers are cached). Null for historical cached lookups whose original retrieval time was not retained; never substitute the time the cache was read.

The instant this answer stops being fresh under the service's refresh policy — retrieved_at plus 28 days, or plus 7 days while today is within a fortnight of a UK bank holiday. Before it, the answer is an acceptable cache and no refresh is owed. After it, a read of the schedule resource queues a background refresh and still returns the answer as it stands; a later read returns the refreshed answer with a new retrieved_at, refresh_due_at and ETag. It is policy, not a promise of when the refresh runs. Null when retrieved_at is null.

When a shared source artifact was most recently conditionally revalidated.

Opaque content-hash and parser-version identity for a deterministic shared calendar.

Present and true only on an INTERIM answer: a same-postcode neighbour's schedule, served in under a second while the lookup for this exact property is still running. It is always accompanied by address_match: postcode_representative, dates_complete: false on every collection, and a notes caveat naming the neighbour. The lookup carrying it is partial, never done.

An interim is never cached: it does not appear at GET /v1/schedules/{property_token}, in a calendar feed, in a reminder or in an email, and it is replaced in place by the exact answer as soon as that arrives. A client that treats it as final is misreading it — keep polling the lookup.

It is fail-closed: the council must pass the measured zero-mismatch gate and the postcode's held comparable neighbours must also pass the serve-time verification gate. See docs/interim-then-upgrade-serving-2026-08-27.md for the internal evidence thresholds; clients must rely on provisional, not reproduce those policies.

Plain-English caveats written for the citizen (assisted collections, communal bins, granularity, …).

The council's own checker page ("check on your council's site"): the page the serving run actually read, else the council's known checker page from our council intel. https only.

The property's Unique Property Reference Number, present only when the service has verified it against OS Open UPRN AND public feeds are on (PUBLIC_FEEDS=1). It keys the shareable public calendar https://whenisbins.com/{uprn}.ics and the /schedules/uprn/{uprn} form of this resource. Canonical digits, no zero padding.

The council's own identifier for the property (the value its address list uses), canonical form, present only when the service captured it from an exact match AND public feeds are on. Keys https://whenisbins.com/{council.id}/{council_id}.ics and the /schedules/council/{gss}/{id} form of this resource — the public calendar for councils whose identifiers are not UPRNs.

The property's public, subscribable iCalendar feed, present only when public feeds are on AND the Schedule carries a uprn or a council_id. Always the uprn form when there is a uprn, otherwise https://whenisbins.com/{council.id}/{council_id}.ics. Use this value as given rather than assembling a link. It is a website resource, not a /v1 route: collection dates only, no address or personal details, one event per collection date (?per=service for one per service, ?download=1 for a one-off file). Reading it never creates a lookup. Give it to a person to subscribe to; its dates are this Schedule's dates, so read date_confidence and date_completeness here before describing how far ahead it reaches. Absent means there is no public calendar for this property; never build one from property_id.