Property Operations defines the real-world operating context Lucia must support.
Current Founding Client
The founding property context is:
Villa Valentin provides the first real operating environment for Lucia.
Core Operational Domains
Lucia must support:
arrivals
payments
payment policy
maintenance
concierge
guest requests
vendor coordination
property readiness
Current Highest-Value Loop
The current highest-value operational loop is:
maintenance intaketask creationoperator prioritization
This loop proves that Lucia can receive live-world signals and convert them into useful operational work.
Property Context Requirement
Lucia should never operate as if all properties are identical.
Each property needs:
policies
contacts
service standards
vendor patterns
guest journey rules
escalation paths
payment terms
Payment Policy Baseline v0
Implemented in Development:
Admin /property renders Payment Policy Baseline v0.
The section is read-only and draft-safe.
It is labeled POLICY DRAFT / NO PERSISTENCE.
It warns that Admin is not saving this to Engine, Supabase, Signal Stream, or LIEA.
default currency
deposit required
deposit amount or percent
final balance due timing
security deposit policy
accepted payment methods
concierge / extra charges separate
operator payment verification owner
what counts as paid
what counts as pending review
what counts as overdue
notes / policy caveats
durable Engine-owned property payment policy contract
Admin payment policy editing
Admin payment policy persistence
LIEA policy-aware payment judgment
Signal Stream -> LIEA payment policy wiring
Villa Valentin Role
Villa Valentin is not just test data.
It is the founding client and live operating proof of concept.
See Also
