Built openly. Improved every week.

The private hotel workspace now keeps reservation lifecycle, exact-room inventory, language-aware delivery status and encrypted recovery controls together. Export creation fails closed when protected encryption is not configured.

• One stable reservation reference
• Exact-room conflicts rejected
• No unencrypted backup fallback

Registered hotels receive a private, read-only chat workspace with approved hotel facts, scoped operational totals, visible sources and a real weekly usage meter.

• No guest contact details in model context
• No autonomous booking or payment action
• Provider and billing remain gated

Every optional product now has its own page, product identity, honest launch status, focused demo and one shared interest workflow.

• Original free founding agreements remain honoured
• Product status is visible before the CTA
• One stored enquiry inbox

Aster House uses stored sandbox inventory, atomic reservation creation, a persistent booking, simulated payment status and the same confirmation reference in guest and hotel views.

• No real card fields
• Bookings are stored in isolation
• Hotel and guest see the same status

Production payment, transactional email, external inventory and AI providers remain unavailable until account-level configuration and complete lifecycle tests are recorded.

• No provider logo used as proof
• No automatic activation
• A human launch decision remains required