The Brain / Capabilities / Folder scope
RECALLOne client’s question reads
that client’s folder, nothing else.
One folder holds brief, deck, sheet, form and chat, whichever app made each. A question about that client reads it and stops.
Twenty minutes before a client call
The folder answers as one thing
Nineteen artifacts, six applications, one list at the same weight, from the signed brief to the channel where decisions were argued.
The spreadsheet opens read only, in place
No app switch, no editing controls in an app that does not own the file. Editing happens in the owning app.
Two things missing, and it says which
Two weeks of the thread were never filed, so the Brain names the gap rather than answering as if complete.
Scope is a boundary in the read
Every artifact type has one owning app
How to open a thing follows from what its app says about itself. A new app says where its files open.
Narrowing is an accuracy control first
An AI asked over everything finds something plausible in the wrong account. Reading one client’s subtree removes that at the source.
The AI never picks the folder
Company and workspace come from who signed in. Anything the AI writes naming a different one is stripped before anything runs.
Three honest limits
Not a permission system; your access rules decide who reads.
It does not pull in what nobody filed.
It does not turn every app into an editor.
Updated 15 September 2026 · WE_AINA
Book a Diagnostic Sprint
Bring one client, and read the folder instead of six apps.