Memory Sources
Authoritative content enters Memory as immutable, versioned Sources — held in your own account, never edited in place. A new revision supersedes the old one; nothing is overwritten.
A Source is the system of record, not a chat memory. Each upload is scoped (Org or a single Team) and carries one classification. Narrower-classified slices live as governed excerpts — child records with their own ACL — so a public FAQ can be recalled widely while the CUI body stays sealed. Sources are immutable: indexing produces grounding chunks, and a new version supersedes rather than mutates.
Access Grant Policy
ms-refund-policy · v4
OrgFOUO
Review annually · supersede on policy change
Dana Liu (Platform Admin)
Governed excerpts
Auto-approve thresholds (table 3)
ACL · Platform Engineering + Contracts & Proposals
Public-safe access FAQ
ACL · All teams
Proposal Compliance Runbook
ms-claims-runbook · v2
TeamCUIelevated risk → stricter grounding/taint
Retire 3y after supersede
Linnea Park (Team Admin)
Governed excerpts
Risk bands (CUI)
ACL · Contracts & Proposals only
Proposal Voice Guide
ms-brand-voice · v1
OrgPUBLIC
Permanent, supersedable
Dana Liu (Platform Admin)
confluence://proposals/voice (link kept as metadata; not ingested)link kept as metadata · not ingested