Holiday closures, where an owner can reach them
The field that decides whether a caller is told the office is closed has been read since March and written by nothing. This is the card that writes it — and the caption that tells an owner whether the answer on screen is ours or theirs.
10 Sept 2026 · branch holiday-policy-setting · captured against propflow-stage · at bc70b9e904+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · The card, on a property that has never been asked
This is what every property in production looks like today: no stored answer at all, so the card shows PropFlow's default and says so in the caption under the boxes.
The caption is the load-bearing part, and it is the reason this card is not just eleven checkboxes. “Nobody has been asked” and “somebody ticked exactly these eleven” render identically, and they are not the same stored state: the first follows the default wherever the default goes next, the second does not. Nothing else on the screen can tell a customer which one they are on.
There is no Use PropFlow's default link here, because this property has not left it. The link appears only once the answer is theirs — which is the next section.
The eleven names are chrome, not data: the federal calendar is the same for every property, so the loading skeleton paints the real names and greys only the tick state. One tree, no mirror to drift.
Asserted in the captured DOM — Holiday closures · Columbus Day · Veterans Day · Thanksgiving Day · Using PropFlow's default. The card is really on the property's settings page, the federal names are really rendered, and the caption really says this is the default rather than a stored answer.
2 · Unticking one holiday makes it their answer
Columbus Day unticked — the exact ask a boolean could not express. Turning holidays “off” to open Columbus Day would also have opened Christmas, which is a worse answer than the one the owner was trying to give.
Three things change together, and they change on the FIRST click rather than on save: the caption flips to Set for this property, the way back appears beside it, and the save bar comes up. Nothing is written until Save — and if the boxes are untouched, nothing is written at all, so an owner who came here to edit a tour duration cannot accidentally freeze today's default onto their row.
Not saved in this capture. The evidence run drives the real page against the real API; leaving the save unpressed is deliberate, so this artifact reads the property's state rather than changing it.
Asserted in the captured DOM — Holiday closures · Set for this property · Use PropFlow's default. The caption really flipped, and the way back really rendered — both are DOM text, not just pixels.
3 · Where it sits on the page
Between Calls and Leasing & tours, and that placement is an argument rather than a gap in the stack. A day this card closes is a day tour booking refuses and a day the voice agent reports the office shut — so it belongs above the card that owns tours and below the card that owns the phone, not inside either.
Asserted in the captured DOM — Calls · Holiday closures · Leasing & tours. The three headings are in the rendered DOM in that order.
