Slack rollout thread
visible to Support
Source
The source must be visible.
MemoryCrow checks the original system before it returns an answer or citation.
TRUST MODEL
MemoryCrow lets every AI use the same company memory without turning that memory into a leak. If the source is hidden, stale, or outside the requester's scope, the answer does not return.
Cited
Answers carry visible sources.
Current
Old facts stop winning.
Scoped
Access follows the asker.
Support asks
What should we say about workspace invites?
Keep invite links off by default.
Domain join can be enabled after admin approval. Both sources are current and visible to this requester.
Answer, source, and scope travel together.
THE GATE
Permission safety is not a redaction pass after retrieval. It is the condition for retrieval. If any check fails, MemoryCrow abstains instead of guessing.
Slack rollout thread
visible to Support
Source
MemoryCrow checks the original system before it returns an answer or citation.
March invite policy
current version
Version
Superseded facts stay in history, but they stop becoming the answer.
Admin settings note
workspace admins only
Scope
Combining sources can narrow who sees the answer. It never widens access.
SAME MEMORY
That is the point. MemoryCrow does not make a private source public just because an AI can ask nicely. The answer is shaped by the requester, not only by the prompt.
Support asks
Can we tell customers imports are fixed?
Only CSV imports are fixed.
The current PR and rollout thread are both visible to Support.
Contractor asks
What renewal discount did Northstar get?
I can't answer from visible sources.
The evidence exists, but it is outside this requester's scope.
Start with one memory
Start the trial, connect one source, and ask the next question from Claude, ChatGPT, Cursor, or any MCP client. If MemoryCrow cannot prove it, it will not guess.