Skip to main content
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: 
arrivals
departures
stay windows
occupied nights
booking identity
payment obligation timing
The booking spine gives every other operational surface a truthful temporal anchor. Current product architecture: 
Calendar = root operational reality
Booking Pulse = granular intelligence lens over booking/calendar reality
Signal Stream = what needs attention
Lucia Workspace = reasoning partner beside the operator
Focus Ops = shared reasoning and conversation
Dynamic Action Workspace = action/save surface
Full Booking Page = record/review surface
Eval Labs = behavioral proof and regression protection
Payment Truth Foundation = policy shape + temporal truth + Stripe movement + durable ledger
Do not describe this milestone as “adding a chatbot.” The product movement is that Lucia’s operating intelligence is becoming rooted in booking reality. The next product movement is that Lucia is no longer dashboard-bound: 
Lucia Workspace + DAW = cockpit
Full Booking Page = record/review surface

​
Current Development Implementation

Admin Calendar v1 is implemented as a monthly booking spine in Development/v0.1.x. Current live-dev truth: 
Calendar is second in the main Admin nav
Calendar route is /calendar
Calendar reads /admin/bookings
Calendar shows monthly booking/stay-window reality
Calendar supports bounded continuous scroll
Calendar scroll bounds: 12 months back, 24 months forward
Booking clicks route to /bookings/:bookingId
Booking clicks do not route to Dynamic Action Workspace
Booking Pulse derives from the same booking source
Villa Valentin is modeled as one rentable inventory unit
The Full Booking Page is the correct destination for Calendar booking review. Dynamic Action Workspace remains the correct default destination for structured Focus Ops actions that need the operator to finish work. Payment timing boundary: 
Calendar/booking truth can tell Lucia when payment obligations may matter.
Stripe movement truth can tell Lucia what was actually paid or attempted.
Durable property payment policy truth is not implemented yet.
Therefore due, overdue, deposit, and final-balance claims must not be inferred from calendar timing alone.

​
Development Demo Fixture

Engine Development now bootstraps a realistic demo fixture for the booking spine. Current fixture truth: 
36 bookings
18 occupied months
no impossible overlaps
no stale arrival_profile days
Villa Valentin modeled as one rentable inventory unit
This fixture exists to make Calendar, Booking Pulse, Signal Stream, and Focus Ops reason over a believable booking world instead of an empty demo shell.

​
Boundaries

Current scope: 
Development / v0.1.x milestone
one property context
one rentable Villa Valentin inventory unit
monthly booking/stay-window spine
booking-backed operational awareness
Not yet claimed: 
production readiness
staging promotion
multi-property inventory
owner-facing calendar workflows
calendar import/onboarding flows
full scheduling system
durable property payment policy truth
full policy-aware due/overdue/final-balance payment judgment
Future work should build from the booking spine instead of replacing it with a generic calendar fantasy. Calendar context awareness is functional in the Workspace OS milestone, but richer visible-month and booking-detail context still belongs to future hardening.

​
See Also