Records and memory
ERIS keeps several kinds of record. They are not interchangeable: org policy and engineering truth live in indexed reference docs; personal facts you ask ERIS to remember follow a confirm path; live roster data comes from personnel tables, not from chat guesses.
Reference memory
When the memory module is enabled, ERIS can search approved documentation (top-level docs, ops runbooks, and curated corpus files) and return cited snippets. Staff gateway phrasing such as /recall or recall: targets this slice when assistant and memory are loaded.
Visibility labels on documents (public, internal, restricted) filter what a given operating context may retrieve. Nested planning or assessment folders are intentionally excluded from the public index.
Personal memory and notes
Personal facts the owner asks ERIS to retain use an offer → confirm flow before they are stored for later recall. Website notes (personal, project, clearance-scoped org notes) are a separate notes module with sharing and ACL rules—not the same as dumping chat into policy.
In Discord assist, tool naming can overlap colloquially (“recall”); saved notes and reminders in assist are not the same capability as institutional memory.recall. See Notes and memory for everyday use.
Subject record (privacy)
The portal Privacy / record surface lets you review privacy holdings tied to your account where that feature is enabled. Deletion or opt-out paths that involve Second Life may require in-world confirmation flows documented for operators—not shortcuts around verification.
Cross-platform notices
Memos, tasks, and reminders can enqueue inbox notices for delivery on the next linked Discord DM, Corrade IM flush, or the Assistant notice hub when those modules are enabled. That queue is delivery metadata, not a substitute for reference memory.