Vault and SAM
SAM reads your Vault before it drafts anything, and files good answers back into it with one click.
The Vault arrives with SAM's Surface App capability and has no separate switch.
It Reads the Vault Before Drafting
Naming a path is the fastest way to stop generic output.
Priya14:02
@SAM draft a LinkedIn post about the Nextiva result, using brand/voice.md
SAMApp14:02
Nextiva rebuilt one form with us and 37% more users converted. Same traffic, same offer, different questions in a different order.
That is the whole post. No "excited to share".
Pulled the number from customers/proof.md and the no-throat-clearing rule from brand/voice.md.
You can also just ask what is in there: "what does the Vault say about how we position against Chili Piper?"
If a draft comes back generic, SAM found no voice rules and will say so in a line. Point it at a document, or tell it the rule once so it remembers.
Save in Vault Files the Answer Back
When an answer is a document rather than a number, a Save in Vault button
appears under it. One click files it as a dated Markdown document under
slack/, and SAM reads its own Vault before drafting, so saved answers improve
later drafts.
That button is the only Vault write SAM makes without a second approval card, because it can only ever create a new document. It cannot overwrite or delete an existing one. See Limits and guardrails.
Editing an existing Vault document, appending a rule to brand/voice.md for
instance, is done in the app rather than from Slack. SAM's Vault writes go to
slack/ as new documents.
The Loop This Enables
Someone posts a draft in the channel
Or SAM does, on a schedule.
Someone says what is wrong with it
"This still says 'solution' twice."
The rule goes into the Vault
Either as a saved answer under slack/, or edited straight into
brand/voice.md in the app.
The next draft is right
And so is every draft after it, including the ones written by agents nobody in that channel ever talks to.