Atlas tour calendars
Which calendars a tour booking tries at a building, in order, and whether each one works
1 Oct 2026 · branch p9-calendar-atlas-tour-pool · captured against propflow-stage · at 5e63f980b3e
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 · Fairhaven Residential (TEST), August Court: the company calendar is connected
No team member has a calendar connected here, so a booking tries the company calendar, which is connected. The block shows the order a booking tries calendars in, and each one's state. It does not claim a winner: only a real booking decides that, and the booking records it on the tour.
Asserted in the captured DOM — Tour calendars, in the order a booking tries them · tried first · its own calendar — this rung has no endpoint id
Sections 2–2
2 · Negative control: a test company with no calendar
The company has no calendar connected, and the block says missing. The revoked state (a calendar that was connected and is now broken) is covered by the unit tests, since making one on stage would need a write.
Asserted in the captured DOM — Tour calendars, in the order a booking tries them · missing — no calendar connected
