AI Activity Record
The AI Activity Record is the broker's one-page answer to "show me what the AI did under my name." Every action EVE takes across your brokerage lands in an append-only record: who or what acted, for whom, on what channel, and under what authorization. You reach it from the Compliance desk header.
Why this page exists
MLSs are writing AI terms into their data licenses, and insurance applications increasingly ask how a brokerage uses AI. Whoever asks, the answer depends on whether the record of what the AI actually did exists. A record like this cannot be created retroactively: it either accumulated while EVE worked, or it did not. In REALM it accumulates automatically from the day EVE is switched on.
Reading the page
The summary tiles count the window you have selected (7, 30, or 90 days): how many actions were flagged by the escalation classifier, how many EVE performed itself, how many a person performed, and how many agents were active.
What this record covers states what the record rests on. Native capture is always on: everything EVE does inside REALM is recorded, structurally. The extension, connected mailbox, and API counts show which additional capture mechanisms are live for your brokerage, so the record's coverage is stated rather than implied.
MLS data & AI: authorizations in force is the per-MLS control. AI use of MLS listing data is denied by default, in code. An MLS appears here as authorized only after its written authorization is recorded, and each row cites the document it rests on. A source not listed is not authorized: absence means no.
Held for review is the escalation ceiling at work. Anything touching an offer, a price, contract terms, financing, legal, or an unhappy client routes to the agent before it goes out, in every autonomy mode, with no setting that disables it. This panel shows what was held and how each item resolved.
The activity list is the ledger itself at the supervision grain: the action, who or what performed it, the contact and transaction it concerned, the channel, and any escalation flags. Click a row to expand its full detail and jump to the contact or transaction it belongs to.
What the record deliberately does not show
Message bodies. Supervision needs to know what was done and for whom; it does not need to read every client message, and showing every body to every broker would be a much larger disclosure than oversight requires. Full content lives where it belongs: in the client's thread in Connect, and sealed per-transaction in the Vault when the file is archived. The record links you to the contact and transaction, where authorized surfaces hold the content.
The attestation packet
The Export attestation packet button produces a ZIP for the period you have selected: the activity ledger as a spreadsheet, plus a summary carrying the full authorization table with each written basis and plain statements of what the packet does and does not contain. Every export is fingerprinted and logged in its own append-only trail, so a packet produced today can be matched to its export event years later. It is built to be handed to an MLS auditor, an E&O underwriter, or whoever asks next.
What the record means for your obligations is between you and your counsel. REALM's job is that the record exists.