Villa Valentin is Lucia’s founding-client context. That relationship does not make a development fixture, example, or Library page a source of live property data.
Role
Villa Valentin provides real-world domain context for the kinds of property operations Lucia must understand. This page preserves that durable context without asserting a current feed, inventory state, booking record, or operating condition.
These categories are not interchangeable.
The one property
“Everything is Villa Valentin right now. There is NO OTHER PROPERTY. There will not be another property until Lucia’s entire platform has been functioning exceptionally well at the founding client/pilot property … for an extended period of time.” (founder, 2026-08-04, LUCI-92)
Every record the Engine writes binds to the pilot property, read from property settings under the canonical slug villa_valentin; nothing is hardcoded inline and nothing is inferred from a provider payload (LUCI-92). The property’s name is written Villa Valentin, plain i, on every surface (LUCI-238, 2026-09-09). Multi-property onboarding is months away and explicitly out of scope.
These values are the Villa’s, set by the property owner in property settings, and they replicate the real world. They are property data, never constants inside the Algorithm (ALGO-23, founder non-negotiables, 2026-09-02).
Property settings are read-only today; the owner will change these values through settings later (ALGO-23). The clock law that governs how these times reach the owner is on Calendar and Booking Spine.
Property-domain concepts
The founding-client context informs Lucia’s durable vocabulary:
The list describes the domain Lucia must support. It does not report Villa Valentin’s current operations.
The living development world
Development runs on a synthetic Villa Valentin played on the real clock by lucia-world: fabricated guests, bookings, payments in Stripe test mode, maintenance, and messages, entering through the platform’s real doors. It carries the Villa’s real terms and times as property data so the pressure on the owner is real, and it is never live Villa Valentin bookings or inventory.
Any current claim about that world must identify the owning repository and revision, the environment, the observation date, and the validation result. Multi-property inventory and richer calendar onboarding remain separate product capabilities that require their own verified evidence.
Canon rule
Property examples must name their evidence category. Do not present a synthetic record as client truth, and do not generalize one founding-client context into a universal property rule.
See Current System State for the current evidence boundary, Seed Data and Test Worlds for synthetic-world doctrine, and lucia-world for the living development world.
