Front Desk — Chat (iOS)

Online · all capabilities active

9:41

Front Desk 4 experts on call

Local memory On-device AI Routing Dispatch

Today · 2:14 pm

Reply to Lisa about the AGM agenda — she asked yesterday for the final list of items. 2:14 pm

Routing decision 0.3s

Yemaya / Board Prep

Resumed · last active 2h ago · Lisa Petersen, Jonas

"Lisa" + "AGM agenda" matched 3 notes in projects/yemaya/board-prep/. Picked this conversation because it's the only one with Lisa as participant and an open agenda draft.

91%

Ye Yemaya · Board Prep writing now

Pulled the latest agenda from yesterday's draft (v4). I removed the duplicate budget line and added the auditor slot Lisa asked for. Draft below — review and send.

Email draft Awaiting review

To LP Lisa Petersen

Cc board@yemaya.fund

Subject AGM agenda — final (v4)

Lisa,

Final agenda for Thursday's AGM is attached. I folded in the auditor slot, dropped the duplicate budget line, and moved the Q3 capital call before AOB so we don't lose quorum.

Let me know if anything's missing — I'll send the calendar update once you confirm.

— Jonas

0:09 / 0:24 Auto-transcribed · tap to expand

SS Salt & Shade · Ops task channel · live

Generating Q3 catering report Running

Fetched bookings from salt-and-shade.db (148 events) +1.2s

Joined invoices and aggregated by venue +0.6s

Rendering charts and exporting PDF… 3.4s

Upload to Drive & share with team

$ render --format pdf --theme yemaya q3-report.json

· packing 148 events into 6 venue groups

· built revenue.line · margin.bar · top10.table

62%

Send the Q3 numbers to the bank — they need it for the loan extension. 2:18 pm

Routing · your call 4% margin 0.18s

Two close matches. Tap one — I'll remember which signal mattered next time you say "the bank".

Offline · server unreachable — graceful degrade

9:47

Front Desk running on local replica

Local memory On-device AI Routing Dispatch 2 queued

Now

0:11 / 0:18 Transcribed on-device · queued

Tell Lisa the AGM packet is ready — she should review tonight.

Drafted & queued. Will dispatch when online.

Ye Best guess · Yemaya / Board Prep

87% confident on the route from local memory. You'll see the live decision & reply when the connection returns — tap to retry routing now.

← All screens / Chat · iOS

The routing moment.

The thread is a UI for decisions, not for chatting with the desk. Each element below is heterogeneous — a card, a draft, a waveform, a live task channel — strung together by the same hairline border vocabulary.

1 · User asks in plain language

Voice or text. Always optimistic — the message lands immediately.

2 · Decision card

The most-seen element. Shows the route, a one-line "why", confidence, and an "actually, wrong office" undo. Never silent.

3 · Expert reply streaming

The agent's name + project is the badge. Stream cursor pulses while writing.

4 · Email draft

Review / edit / reject / send. Comment-back stays inline. The recipient chip is real (avatar + name), not a string.

5 · Voice note

Played-vs-unplayed regions in the accent. Auto-transcription on tap.

6 · Live task channel

Streaming partial output. Cancel is always a button, never a confirm-dialog.

7 · Voice-primary input

Floating mic, accent color, ripple-ring while listening. Tap-to-toggle keyboard via the field. Compare two affordances →

Capability ladder.

When the network goes wrong, the UI visibly degrades but simple things still work. Memory Q&A from the local replica, draft generation on-device, voice memos to inbox. Nothing lies about state.

8 · Capability chip row

Four chips, always present: Local memory · On-device AI · Routing · Dispatch. Green dot = active, amber = degraded, empty ring = unavailable. The user can always see what the app can do right now.

9 · Outbox count + degraded banner

Yellow banner names the failure mode; outbox pill on the chip row tracks queued actions. Banner copy is specific — "server unreachable" vs. "AI services degraded" — never just "Offline".

10 · Queued-dispatch ack

Drafted on-device, route guessed from local memory, explicit confidence shown. The desk never silently swallows the user's intent — and offers a manual retry.

11 · Conflict-resolution sheet

Target conv deleted while offline → iOS bottom sheet with a tangible thing to act on (the deleted target rendered as a card) and a binary choice: Restore & send / Discard draft. No silent loss.

12 · Muted palette

Thread + input drop to saturate(0.72) when offline. Chip row, banner, outbox stay at full saturation because they're the informative layer. Reads at a glance: "something's wrong, but I can still do things".