Skip to main content
Property Operations defines the real-world operating context Lucia must support. It does not claim that the Library reads live property data.

​
Founding-client context

Villa Valentin is Lucia’s founding-client context. It grounds domain requirements and product learning, but it is not interchangeable with a synthetic fixture or a dated runtime observation.
No current Villa Valentin booking, guest, payment, maintenance, or inventory fact is asserted on this page.

​
Core operational domains

Lucia must support:
These are durable product requirements, not a report of current activity at a named property.

​
Highest-value loop

The core maintenance loop remains:
maintenance intaketask creationoperator prioritization
This is product doctrine: Lucia should convert property-shaped signals into reviewable operational work. Whether a specific build completes the loop requires dated implementation and runtime evidence.

​
Property context requirement

Lucia should never operate as if all properties are identical. Each property needs:

​
Payment policy baseline

​
Dated product observation — 2026-08-12

The current-system source audit records an Admin /property surface with a read-only Payment Policy Baseline. Its visible boundary is:
The surface describes fields such as currency, deposit terms, final-balance timing, accepted payment methods, verification ownership, and policy notes. It does not prove persisted property policy or live Villa Valentin payment truth. The same audit records these capabilities as not implemented:
This is a dated product-source observation. Reverify it against the owning Admin and Engine revisions before treating it as current after 2026-08-12.

​
Villa Valentin boundary

Villa Valentin’s role is durable founding-client context. Synthetic examples may draw on property-shaped concepts, but they must not imply that fabricated records are client data or that a product behavior has been proven in live operations.

​
See also