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.
Property → journey group → stay record
All three stages, with fictional outcomes
Guest and Operator, side by side
THE DIRECTORY
Evidence is dated, not a live health signal.
Open an evidence note for scope and source.
9 views
Guest and hotel views together, guided through one stay.
Loads fromConnected AWS apps
AWS still uses /tour. MC’s Vercel canned tour is a separate presentation.
Page and both AWS frames loaded; no disconnected-service message. Full transaction walkthrough was not repeated.
Source: bspg-org/guest-intelli-site
Property reporting, journey groups, guest records and service queues.
Loads fromAWS Core + Recovery APIs
Open Property. Live-origin is the default; select another origin explicitly. Empty stages can be valid.
Reporting, date filters, journey lists, record drill-down and stable totals during search passed browser checks.
Source: bspg-org/pulse-m1
Recognition, consent, stay requests and recommendations.
Loads fromAWS Core API
Use the guided tour for a coordinated walkthrough. This app shares a release with Core.
Production build, deployment HTTP readiness and tour frame load passed.
Source: bspg-org/guest-intelli
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.
Source: bspg-org/pulse-m1
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.
Source: Phunware Bitbucket · itin-planner-rn + itin-planner-api
Explore the Solara Cove conversational concierge.
Loads fromAWS frontend · Supabase backend
Working transport does not establish answer quality or fulfilled commercial outcomes. Supabase replacement remains planned.
Earlier evidence covers consented ingest, chat/feed, escalation and upsell callback transport with Core.
Source: bspg-org/porter
The JSON records behind property reporting and guest operations.
Loads fromRetained Core data
This opens raw JSON, not a dashboard. Default results contain live-origin stays in the current date window.
Reporting returns 200; invalid origin and date windows return 400. Staff and tour preflight routes respond.
Source: bspg-org/guest-intelli
The Make-It-Right service used by Hotel Operator.
Loads fromRetained Recovery data
This opens raw JSON. Use Operator for the staff-facing recovery views.
Earlier release evidence covers HTTP readiness and data retention across pod replacement.
Source: bspg-org/make-it-right
Guest experience and a separate content CMS.
Loads fromExisting Vercel / Railway + Supabase
The TimeLens CMS is not Hotel Operator. Core activity/outcome returns are still planned.
AWS infrastructure is prepared. AWS deployment, DNS publication, login and saved-data validation remain open.
Source: bspg-org/timelens
HOW IT CONNECTS
Application relationships, not a network map.
Select a component to find its entry point.
Planner returns, TimeLens integration and staff permissions still need work. Supabase remains in use for Porter and TimeLens.
AWS runs the main apps. Some services still depend on external systems. A working route does not prove every integration or business outcome.
KEEP THE TWO DEMOS CLEAR
Use the r2inary links above. Where adopted, reviewed work lands on demo, then release-dev points to the selected commit. Core and Guest release together; reporting changes release Core before Operator.
Open the Vercel tour ↗. Access may require the demo password. Its canned content is separate from AWS records. Updates to main or master can deploy Vercel; AWS work stays on separate branches.
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.