Test worlds are synthetic. They can model operational conditions for tests and demos, but they are never evidence of current property state.
The truth since 2026-09-03: Lucia’s development world is not a static seed file. It is lucia-world, a private commandable service that plays Villa Valentin on the real clock and sends every event into Development through the platform’s real doors. The doctrine on this page is what that world obeys. Purpose
Lucia needs privacy-safe, property-shaped test worlds to evaluate:
Evidence categories
Keep these categories explicit wherever a test world appears:
See Current System State for the current system-wide evidence boundary.
From a seed pack to a living world
The earlier design concept, an Operating-Year Seed Pack, was a simulated year of property operations frozen in absolute time. Read against a later clock it became a departed property with nothing live to rank (World fixture becomes time-relative, ALGO-23, 2026-09-02). The concept survives as the world’s shape: a year of arrivals, deferred work, urgent issues, open loops, and guest context. What changed is the clock and the doors.
The world is a fixture design in motion, not a record of a property’s actual year.
Fixture requirements
A useful booking-spine fixture should be internally coherent and privacy-safe. Validation can check properties such as:
No booking count, occupied-month count, or fidelity result is asserted as current on this page. A current claim must name the owning repository and revision, environment, observation date, and validation result.
Villa Valentin is the one property, and the world plays it as one rental unit with the Villa’s real terms and times as property data (ALGO-23). A synthetic world that uses the property’s name must still contain fabricated records and must never be described as Villa Valentin’s live data.
Generated text must speak owner language: synthetic human names, no fixture labels, no engine category words. The world’s own gate refuses engine words in generated titles (ALGO-27, 2026-09-03).
Workspace context fixtures
Workspace evaluation also needs synthetic surface context:
Guest identity and linkage fixtures
Guest-facing evaluation also needs privacy-safe, synthetic identity and linkage scenarios:
Use
Synthetic worlds support, or are meant to support:
The fixture enables evidence collection; it does not make a launch-readiness claim by itself.
See also
