> ## Documentation Index > Fetch the complete documentation index at: https://helloluciallc.com/llms.txt > Use this file to discover all available pages before exploring further. # lucia-world > The living development world: a commandable synthetic Villa Valentin that plays the property on the real clock against Development through the platform's real doors. lucia-world is the development world Lucia is judged against. It is not seed data. It is a small private service that plays Villa Valentin on the property's real clock and sends every event into Development through the same doors a real guest, employee, or payment would use. Everything on this page is a description of an internal instrument as of 2026-09-10. lucia-world has no deployment, no production role, and no owner-facing surface. Its generated guests, bookings, payments, and messages are fabricated. They are never Villa Valentin's live records. *** ## Why it exists The founder set the north star on 2026-09-02 (ALGO-27): > "…allow us to easily command `Lucia World` with the number of bookings, maintenance issues, concierge requests, guest agent comments/inquiries, etc. That has got to be the north star." The reason is the product's reason. The earlier development fixture was frozen in absolute time, so the property it modelled had already departed and the Signal Stream had nothing real to rank (ALGO-23). Lucia exists to answer "Hey Lucia, where should I start this morning?", so the world she reads must put real pressure on the human who owns the property: cognitive overload, competing priorities, a same-day turnover with an unpaid balance and an arriving guest's question all at once. That pressure is the point (founder, ALGO-23, 2026-09-02). A world in constant movement is what makes the pressure real. *** ## What it is ```text theme={"dark"} a commandable world, not a script one private repository (hello-lucia/lucia-world, created 2026-09-02) a separate service, never an in-engine scheduler plays the Villa on the property's clock every event enters Development through a real platform door it never plays the operator deterministic from a seed plus an append-only journal replays itself after Development state is wiped Stripe test mode only ``` The rulings above were ratified with the founder's design on ALGO-27 (2026-09-02). Codex built the scaffolding and lower-level architecture headless; the Algorithm Evaluator owns the world's behaviour and its gate. ### The command surface The world is driven from one command line. Its verbs, as recorded at the phase 01 integration request (ALGO-27, 2026-09-02): ```text theme={"dark"} status epoch, seed, day zero, dials in force, counts, next events play execute the events that are due, in order, through the chosen door dry-run print a window of days as a table instead of sending anything set change one dial, or apply a season preset send fire one intent now: inquiries, a booking, maintenance, a question, a request, a payment, a cancellation snapshot capture the world at a day; optionally write it out as a de-materialized fixture reset start a new epoch, on demand only, never automatically replay rebuild the world from the journal; verify mode fails on any drift install-profile materialize the day-zero profile at an anchor day for the Engine ``` The cadences the Algorithm Scientist designed are the **defaults of the dials**, not constants. Dials cover inquiries, bookings, stay length, calendar density, deposit and balance behaviour, cancellations, requests, questions, maintenance and its urgency, and season. Presets exist for a busy season and a quiet season. The exact dial values are internal and are not published here. ### Day zero and the clock Day zero is the ratified 44-booking map installed through the Engine's profile path (ALGO-27). Every date in the world is an offset from an anchor "today", so every scenario exists every day and a replay pins one anchor (ALGO-23, Scientist design). Generated stays never overlap the day-zero calendar, and the world plays the future of the inherited day-zero stays rather than rewriting their ratified mornings (ALGO-27, 2026-09-02). Money follows the Villa's real terms: a booking is confirmed a drawn lead time before arrival, the deposit follows the booking, and the balance is due 60 days before check-in or at booking when the stay is inside that line. Deposits, balances, late payments, failed cards, refunds and disputes all run in **Stripe test mode** against real Stripe test objects, never synthesized state (ALGO-27; LUCI-215 feedback law). Because the Engine's committed day-zero profile is anchored to one absolute day, real time ages it: the arrival the founder tests against becomes "in-house since yesterday" overnight (ALGO-43, 2026-09-05). The standing drill is a re-seat on the founder's word, moving the whole house one day later so the loud card stays in place while the elements inside it are worked (LUCI-213, founder 2026-09-06: "age it."; ALGO-43 founder direction 2026-09-07). The automatic daily re-anchor is recorded on ALGO-43 and was not built as of 2026-09-10. *** ## The doors The generator enters the platform only through real doors (ALGO-26, founder-ratified 2026-09-02). On Development those doors are: ```text theme={"dark"} the seed-booking door, carrying a real total the Stripe seam can judge Stripe test-mode payments with scenario metadata Fieldwork intake and employee replies the guest question and request paths cancellation ``` The world's guests carry addresses on a reserved test domain with no mail server, so Development can never reach a real person (LUCI-231, 2026-09-08). Every guest-facing email sent from Development is redirected to one testing inbox with the intended recipient written into the subject, and production refuses to boot with that redirect set (LUCI-231, completed 2026-09-09). Door credentials are placed by the founder's hand; only their names appear on records, never a value. The doors are flag-gated on Development only. The first live day opened on 2026-09-03 with the seed door, Stripe test mode, and the intake path reachable at Engine Development `c047c0b` (ALGO-27 checkpoint, 2026-09-03). On 2026-09-04 the seed door refused the world's first generated inquiry until Development's allow-list carried the reserved guest domain; Main placed it and the door opened the same day (ALGO-27, 2026-09-04). The remaining door work and its round 03 review live on ALGO-26 (In Progress on 2026-09-10) and are not written here as finished. ### The ticker The world is played on a schedule by deterministic code, in keeping with the company's cheap-watcher rule: a ticker plays the due events through the live doors every few minutes and wakes a person only when something is delivered or refused (ALGO-27 checkpoint, 2026-09-03). As of 2026-09-10 that ticker runs from an engineer's machine. The hosted scheduler named as phase 03 on ALGO-27 has not been created, and lucia-world has no deployment. *** ## The gates the world passes * **Owner language on generated text.** Every string the world sends is human: synthetic guest names, no fixture labels, no engine category words. The generator's own gate refuses engine words such as "readiness" in generated titles (ALGO-27, merged to lucia-world main `6d5050d9` on 2026-09-03; the rule family is Signal Stream speaks owner language, ALGO-29). * **Determinism.** `replay --verify` must rebuild the journal byte-identically; a manual state wipe followed by replay is part of the live-day proof (ALGO-27). * **Coverage by construction.** The world was designed so that every lifecycle state, category, and declared reason code of the Algorithm is reachable, which makes the contract's reachability rule provable (ALGO-23, referencing One honest Algorithm contract, ALGO-8). * **The behaviour gate stays the Algorithm's.** The world supplies the corpus; the replay harness (Algorithm changes show their effects, HLLC-29, completed 2026-09-03) is what proves an Algorithm change did only what it claimed. See [Validation Battery](/lucia/evaluation/validation-battery). *** ## What lucia-world is not ```text theme={"dark"} not a product surface, and never owner-facing not Villa Valentin's live data not multi-unit: the Villa is one rental unit, and bookings are sequential stays (ALGO-23) not a second property: "Everything is Villa Valentin right now. There is NO OTHER PROPERTY." (founder, LUCI-92, 2026-08-04) not production evidence: doors round 03 on ALGO-26 comes before any production use not a replacement for Eval Labs or the replay harness ``` *** ## See also * [Seed Data and Test Worlds](/lucia/evaluation/seed-data-and-test-worlds) * [Validation Battery](/lucia/evaluation/validation-battery) * [Calendar and Booking Spine](/lucia/operations/calendar-and-booking-spine) * [Villa Valentin Property Instance Pack](/lucia/properties/villa-valentin-property-instance-pack) * [Current System State](/lucia/start-here-lucia-ai/current-system-state)