Skip to main content
Properties define the operating domain Lucia must support. This page does not claim that the Library or a development fixture contains live property data.

​
Purpose

Property-domain context includes:
These are domain requirements, not a claim that Lucia currently receives a live property feed.

​
Evidence boundary

Villa Valentin is Lucia’s founding-client context and real-world proving ground. That durable relationship is not a current-data claim.
No current Villa Valentin booking, guest, payment, maintenance, vendor, or inventory fact is asserted here.

​
The property’s clock and terms are property data

Since 2026-09-03 the property’s zone, check-in and check-out times, and payment terms are read from the property block and rendered in the property’s own time on every owner-facing surface; the owner never sees a zone name (Property time is the only clock, ALGO-34). The Villa’s values, and the rule that they are the property’s and never the Algorithm’s constants, are on Villa Valentin Property Instance Pack. The clock law itself is on Calendar and Booking Spine.

​
Dated product observation — 2026-08-12

The source audit recorded Admin Development /property with a read-only Payment Policy Baseline labeled:
The audited contract did not persist policy to Engine, Supabase, Signal Stream, or LIEA. Durable Engine-owned property policy, Admin policy editing or persistence, policy-aware payment judgment, and end-to-end policy wiring were not implemented on that date. This is a dated observation of the August admin; the September property block described above supersedes the “no persistence” reading for the clock and terms, and the admin’s property surface is refreshed in wave 2 of Canon Wave 3 (HLLC-41).

​
Rule

Lucia must reason against verified property state from the owning runtime, not generic assumptions or synthetic examples presented as client truth. Payment-specific rule:

​
See Also

​
Upstream / Downstream

​
Upstream

This layer is fed by:

​
Downstream

This layer affects: