How to Use This Demo

The ecosystem is gated. Open the live demo and sign in as the owner (admin / admin@123) to get the canonical send + route actions and the CONFIGURE tab, or as the read-only viewer to triage and draft without the irreversible steps. Unauthenticated visitors only ever see the sign-in card — the operator console is never sent to the browser for an unauthorized session.

Open the app from the launcher (Customer Experience zone) to land on the OPERATE triage queue: an email list on the left (sender, language tag, subject, status) and the detail on the right. Pick an email and press "Run triage" — the simulated pipeline runs clean → language-detect → classify → enrich → draft + QC, and the panel fills with the stage trace, the classification (category · priority · sentiment · detected language), the enrichment (guest · booking ref · property · loyalty tier), and an editable draft reply.

Edit the draft inline. As the owner you can then "Send reply" — which opens a shared support conversation and fires a confirmation email into #35's sent viewer — or "Route to ticket", which escalates the email into a categorized ticket that shows up in #16. Viewers can run triage and edit the draft, but see both actions disabled with an owner-only label.

Open "Behind the scenes" (the dark inspector) to see the honesty layer: each triage run writes a cost-ledger row tagged with its mode (OSS, recorded at $0 on local hardware) and model, alongside the per-stage trace. You can scope the trace to this app or the whole ecosystem. None of this appears on the triage surface itself.

The owner-only CONFIGURE tab shows the category→team routing table (a two-layer immutable-baseline ⊕ owner-overlay model): booking-change → Reservations, refund → Billing & Refunds, complaint → Guest Relations, and so on. It's read-only to viewers and every edit is audited.