ONE PLACE TO FIND YOUR WAY
Open an app, follow a guest stay, or see what connects behind the scenes. Know which views use connected records and which tell a scripted story.
EARLIER PLANNING DOCUMENT · SEPTEMBER 15, 2026
Dated proposed scope and presenter notes. This is not the current deployment inventory or a customer-readiness claim.
Proposed baseline | September 15, 2026
Staff sign-in → guest link → request and reply
All three stages, with fictional outcomes
A retained scripted example
THE DIRECTORY
Evidence is dated, not a live health signal.
Open an evidence note for scope and source.
11 views
Paired Concierge and Hotel Operator presentation with its own session data.
Loads fromIndependent synthetic sales sessions
Use the assigned sales access key. This is separate from named AWS development accounts and has no real guest messages or charges.
Kept intact during the AWS platform changes. Its release and acceptance records are separate.
A scripted walkthrough of the hotel and guest experience.
Loads fromIllustrated sample
Retained as an example. Use Sales Kit for sales presentations and the AWS development workflow for product checks.
This route is an illustrated example, not proof of working hotel integrations.
Named staff access, work inbox, service requests, editable replies and response history.
Loads fromAWS Core · scoped sample stays
Sign in with your assigned development account. Create a one-use guest link for the paired workflow. No real hotel provider is connected.
Release checks are recorded with the development-platform handoff. Sample records do not establish customer readiness.
Open a scoped sample stay, send a service request and follow staff replies.
Loads fromAWS Core · stay-scoped access
Start in Hotel Operator to create a one-use guest link. Booking and planning providers are not enabled in this first product slice.
See the paired development-workflow release evidence; a page response alone is not acceptance.
Explore all three property stages with a full fictional population.
Loads fromBundled sample · no Core calls
These are simulated outcomes. The sample does not show current property activity or verified hotel integrations.
84 upcoming, 126 current and 520 completed stays; John and Cindy’s record and stable totals checked.
Build a Solara Cove itinerary and explore the planning flow.
Loads fromAWS Planner API + retained database
Planner booking and change results do not yet return to Core. Native app acceptance is separate.
Earlier acceptance evidence covers Solara fixture persistence, guest prefill and live AI.
Explore the Solara Cove conversational concierge.
Loads fromAWS frontend · Supabase backend
The frontend and its existing backend remain separate. Legacy Core callbacks are unavailable in the development product runtime. Supabase replacement remains planned.
September 13 transport checks describe the previous Core mode. They do not prove integration with the current product workflow.
Authenticated product records for the paired guest and staff workflow.
Loads fromRetained development data
This link shows service health. Product records require scoped access. The old public reporting and tour routes are unavailable in this runtime.
The development runtime uses a separate directory on its existing retained volume. The earlier data remains retained for rollback.
Independent retained service-recovery sample API.
Loads fromRetained Recovery data
The new Operator workflow uses Core service requests. This separate API no longer sends legacy events to Core.
Earlier HTTP and persistence evidence remains historical. Its records are retained; this is not a connected product workflow.
Explore Atlantis, House of Representatives or Solara Cove.
Loads fromAWS API · MySQL · S3 media
This is the separate AWS copy. Existing demos remain unchanged. Core activity/outcome returns are still planned.
Atlantis, Solara Cove and House of Representatives guest screens, daily content and media passed AWS browser/API checks.
Edit daily stories, trivia, era content, beacons and scavenger hunts across three properties.
Loads fromAWS TimeLens API · MySQL · SES
Separate from Hotel Operator. While SES approval is pending, email delivery is limited to verified staff addresses.
Email-code sign-in and property-scoped edits passed live checks. Persistence and logout checks are recorded with the release evidence.
HOW IT CONNECTS
Application relationships, not a network map.
Select a component to find its entry point.
Named staff permissions protect the Core service workflow. Booking providers and cross-app returns remain separate work. Porter keeps its existing backend; TimeLens keeps its own AWS API and storage.
AWS runs the main apps. Some services still depend on external systems. A working route does not prove every integration or business outcome.
PRESENTATION AND PRODUCT DEVELOPMENT
Use the app links above. Reviewed work lands on main, then release-dev points to the selected commit. Core and Guest release together; reporting changes release Core before Operator.
Open Sales Kit ↗. It has its own access key and synthetic session data. The earlier external illustrated tour ↗ stays intact.
This directory describes a demo environment, not production acceptance. Verification dates describe recorded checks; they are not uptime indicators. No account credentials or private network configuration are published here.