Everything I could decide myself is decided. What's left needs
you. Each one carries the recommendation of the session that raised it — if you
agree, pick it and press Done. A model's opinion, where there is one, appears on the card
as a receipt line; cards with no receipt were never put to a model. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1Tour calendars: does Fede's 2026-09-14 D1 ruling (Clara books tours on the leasing agent's OWN calendar; the company leasing@ calendar is the fallback — merged dark tonight in #8494 behind Organization.settings.tours.bookOnPeopleCalendars, default off) supersede your 2026-09-10 ruling b89068414 (ONE calendar per operator org)? The touring-engine-architecture doc says D1 'reopens the 9/10 one-calendar ruling' and 'needs Gera's sign-off before step 2 starts'; step 2 (#8494) merged at 22:11Z without it, and portfolio-architecture-phases still records b89068414 as CLOSED with the PERSON# calendar walk called 'the wrong product'. Touring step 3 (merge free/busy across several agents) is holding on this.
In plain terms. Fede decided Clara should check each leasing agent's own calendar when booking a tour and fall back to the company calendar. Four days earlier you decided a company should have just one calendar. Fede's version is already in the code, switched off for everyone. Which ruling wins — Fede's people-calendars, or your one-per-company?
The session raising this recommends: Yes — people calendars with company fallback stands; b89068414 is superseded Your own design (portfolio-architecture-how: 'a person's calendar is a hook on the person, not on the building') already models PERSON#/ATTACH#calendar rows; Fede's C is additive — switch off is byte-identical to today's building-then-company chain — and one-per-org cannot express Western Slope's 'her calendar is the availability'. Tried first, unsuccessfully: Read #8494 (merged f0980106), origin/main tour-calendar-pool.ts, portfolio-architecture-how + -phases, and touring-engine-architecture D1: two founder rulings four days apart point opposite ways, the code now carries both behind a switch, and the phases record still carries the older one as CLOSED — only a founder can say which stands, and recording it in the phases row is your lane.