Calendar is Lucia’s temporal spine. Lucia becomes situationally aware because she is rooted in arrivals, departures, and stay windows.
Core Doctrine
Calendar is not just a page.
Calendar is the root operational reality that lets Lucia understand the shape of time around a property:
The booking spine gives every other operational surface a truthful temporal anchor.
Architecture doctrine:
This is not a chatbot layer. The architecture roots Lucia’s operating intelligence in booking reality.
Cockpit doctrine:
The surface names in the two blocks above are the doctrine’s names as written in May 2026. The admin’s September surfaces (the Bookings list, the booking page, the payment record, Lucia beside every step) are documented in wave 2 of Canon Wave 3 (HLLC-41); this page does not rename them.
Property time is the only clock
Founder law, 2026-09-03, verbatim (ALGO-34): “I am the operator and live on the West Coast, and my property is in Central Standard Time. This logic needs to get baked into the product now. This should never be exposed to the property owner.”
The rule:
The property block declares the property’s zone and its check-in and check-out times; one formatting helper renders every owner-facing time in that zone with no zone text (ALGO-34 phase 02). Villa Valentin’s values are property data, recorded on Villa Valentin Property Instance Pack.
A stay begins at check-in. The Villa’s check-in is 2 PM and check-out is noon, set by the property owner in property settings and never hardcoded in the Algorithm (ALGO-23, founder non-negotiable, 2026-09-02). An open item that threatens a specific stay, sits inside the property-local window before that arrival, and has had no owner touch escalates, and one arrival gets one loud card that lists everything still open for it (Unattended near check-in escalates, ALGO-31, founder 2026-09-02).
Money follows the property’s terms. Payment terms live in property settings, differ per property, and the Villa’s replicate the real world: 50% due at booking, the remaining 50% due 60 days before arrival, the first 50% refundable up to 60 days before check-in (ALGO-23). In the living development world the balance is therefore due 60 days before check-in, or at booking when the stay is booked inside that line (lucia-world plays the Villa, ALGO-27, 2026-09-02). Due, overdue, and paid are judged against the booking’s total and the property’s terms, never inferred from calendar timing alone.
Where it stands on 2026-09-10: the clock law’s phases 01 to 06 shipped on 2026-09-03 across the Engine, the Admin, and the Fieldwork API (HLLC-41 audit read; ALGO-34 In Review on that date). The arrival escalation tier is on Development with a served temperature on each card (ALGO-31, In Progress on that date). The Calendar page itself is formally unscoped: what it is, which surfaces render it, and how it binds to truth are a founder planning conversation recorded on Lucia Calendar scoped (LUCI-99, Planned, due 2026-09-14). Nothing on this page claims a scoped Calendar product.
Source and historical implementation boundary
The Admin source read on 2026-08-12 (Admin dev 1aad7157… at that date) implemented a monthly Calendar route backed by the Engine booking endpoint, bounded month navigation, and booking-detail routing. Neither that review nor this 2026-09-10 pass performed a fresh authenticated Calendar interaction; the served identities on 2026-09-10 are Engine dev e2166b86… and Admin dev 1250ec7e… (HLLC-41 audit).
The 2026-05-26 Development/live-dev checkpoint recorded:
Durable routing doctrine assigns Calendar booking review to the booking’s own page. The Calendar click behavior was recorded at the 2026-05-26 checkpoint; the August source implemented the same route, and no fresh interaction was performed on 2026-08-12 or 2026-09-10. The September door grammar (one page, one door, one name) is wave-2 material.
Payment timing boundary:
Historical synthetic fixture — 2026-05-26
The 2026-05-26 Development checkpoint recorded a synthetic booking-spine fixture.
Recorded fixture evidence at that checkpoint:
This fixture was designed to give Calendar, Booking Pulse, Signal Stream, and Focus Ops a believable test world instead of an empty demo shell. It is not live Villa Valentin inventory or booking data. It was frozen in absolute time and has been superseded: since 2026-09-03 Development runs on the living world, which plays the Villa on the real clock through the platform’s real doors. See lucia-world.
Boundaries
Historical 2026-05-26 milestone scope:
Current evidence boundary as of 2026-09-10 — this page does not claim:
Future work should build from the booking spine instead of replacing it with a generic calendar fantasy.
The 2026-05-29 Workspace OS checkpoint recorded functional Calendar context awareness and left richer visible-month and booking-detail context for later hardening. That interaction was not independently re-proven on 2026-08-12.
See Also
