Experiences & Activities · Documentation
Architecture
Experiences & Activities's pipeline, its owned data, the events it emits/consumes, and what is out of scope.
← Experiences & ActivitiesOwned data + the coupling spine
The app owns `demo_eco_experience` (the generated, POI-anchored catalog) and writes experience bookings through shared-core `booking` plus the payment and notification shells, via the one typed C1 adapter. It reads `poi` / `property` / `guest_profile` and emits `experience.booked`. The data invariant holds: owner writes canonical; a viewer's bookings are credential-scoped, ephemeral, and reset-clearing.
Deterministic + out of scope
Catalog browse and booking are deterministic with no metered stage (the honest AI-assist design). Simulated + labelled: the payment is a simulated capture (no PSP) and the confirmation email lands in the in-app sent viewer (no SMTP); scene art is illustrated, never real imagery. No PII; experience categories and per-city counts are generated from the synthetic property set.