Synthetic no-access product demo

Pet resort work, condensed into one safe staff cockpit.

A visual prototype for owned operations: capture messy requests, draft staff-safe replies, gate risky decisions, and prove labor savings — without live customer, PMS, payment, or provider access.

Show technical proof
Today’s synthetic shift23 min

estimated manual work removed from intake, review routing, and manager briefing.

0live sends / PMS writes
3browser API calls
…Postgres read-model rows
…visible JSON artifacts

Step 1 of 4

Inquiry becomes a clean work packet

The system turns a messy customer message into reservation facts, missing info, and a staff task.

Before

Hi — can Miso board July 3–7? She is gentle but nervous with noise. I think her rabies record is attached, not sure if you need anything else.

Owned workflow output

Structured intake packet

Miso • Boarding + enrichment • Jul 3–7 • needs vaccine document review • front desk follow-up created.

missing vaccine proofnoise-sensitiveboarding requestfront-desk task
8 min

manual intake avoided

Locked: this demo cannot send messages or mutate provider systems.

Live technical artifacts

Show the API and DB doing work.

Click once during the presentation: the browser calls the deployed Next.js proxy, the proxy calls the internal Rust API, and one endpoint reads a Postgres view seeded by migrations.

Call trace

Last run: waiting for browser proof

Runtime counters from API
—inquiries—review packets—audit events—outcomes
DB-backed read model

Postgres view: source_quality_backlog

These rows come from the Rust API querying Postgres through the `source_quality_backlog` projection, not hardcoded page text.

Raw JSON excerpt
Run the proof to display an API payload excerpt.

Live readiness

API is checked from the browser.

/v0/readyz
checking…
metrics
checking…
backlog
checking…

Hard boundary

Built to demo without access.

  • No live customer messages
  • No PMS/provider writes
  • No payment/refund actions
  • No autonomous medical/safety decisions

Architecture story

Job-contact version

Staff UI→Next proxy→Rust API→Postgres read model

The page now shows both the product story and the technical evidence: live browser calls, HTTP statuses, latency, counters, DB projection rows, and raw JSON excerpts.