Built on sample data. Document routing is running on real mail; the other screens show where it's headed.
Meridian ResidentialChief of Staff · Demonstration
Vivienne Aster
Principal Broker
Connected your inbox (read-only) · your Drive (Active Transactions) · your notes · listings DB
Setup: one read-only authorization. Nothing to install or learn. Not pooled with any other agent's book.
I — Filing

A signed addendum arrives at 8:12. Nobody opens it.

Two documents, the same morning. The first files itself. The second does not, and the difference between them is the whole product.

Inbox — Vivienne Aster 8:12 AM

Signed addendum — 12 Oak St

From
Dana Okonjo <d.okonjo@merrittitle.example>
To
Vivienne Aster <v.aster@meridian-residential.example>
Received
Thursday, 8:12 AM
Addendum_signed_FINAL(2).pdf — 3 pages · 412 KB · text layer extracted

What was read out of it

Every field chipped to its line
    Filed · 8:12 AM
    Routed to
    Inbox — Vivienne Aster 9:03 AM

    Addendum, executed — Fennimore

    From
    Rafael Iturbe <r.iturbe@bayside-legal.example>
    To
    Vivienne Aster <v.aster@meridian-residential.example>
    Received
    Thursday, 9:03 AM
    addendum_exec.pdf — 2 pages · 288 KB · text layer extracted

    What was read out of it

    Same fields, same chips
      Held · 9:03 AM
      Held for review — no matching folder.
      Filed only when every field is grounded and exactly one folder matches. Anything less waits for a human.
      II — The thread

      A client you already have, four days without a reply.

      Paragraphs are numbered because every claim the system makes downstream will point back to one of them by number.

      The thread so far

      Your inbox · read-only
        Follow-up overdue
        Inbox — Vivienne Aster Unread · 9:47 AM

        Re: Coriander Lane — still the two questions

        From
        Adrian Kessler <a.kessler@halcyonrobotics.example>
        To
        Vivienne Aster <v.aster@meridian-residential.example>
        Date
        Thursday, 9:47 AM
        III — The briefing

        At 9:51, everything the thread is owed, in one place.

        Not a portal and not a new tool — an email. Every line in it opens the record it came from.

        Inbox — Vivienne Aster 9:51 AM

        Briefing — Adrian Kessler, 18 Coriander Lane

        From
        Meridian Briefings <briefings@meridian-residential.example>
        To
        Vivienne Aster <v.aster@meridian-residential.example>
        Re
        Thread of 6 Aug — client, follow-up overdue since Monday

        The client

            The listing he named — 18 Coriander Lane

            Listings DB · record #114

                Comparables

                Listings DB · records #103, #121, #109
                PropertyStatusPrice$ / sq ftSource

                  First question — answered in your notes

                  Your notes

                    Second question — no answer in any connected record

                    Awaiting confirmation

                    The guest house appears in record #114; its permit status does not. Nothing is inferred from the gap, and nothing is written to fill it.

                    IV — Structured reply blocks

                    A reply skeleton and a checklist, every line still carrying its source.

                    Further down the same email. Nothing to open, nothing to log in to — the agent replies from the mail client already in front of them.

                    Drafts are structured blocks, not ghostwritten voice — the agent stays the author.
                    01

                    Reply skeleton

                    Lines to write through, in order. Each factual sentence keeps the chip that sources it, so the chips travel with the words while you edit them.

                    02

                    Send checklist

                      Click any chip to open its source