Document Management and Local Folders

How to set up local client folders, save generated outputs to disk, track raw documents, and organize Armbrain's file outputs.

Local Client Folders

Armbrain can create and manage a structured folder for each client on your machine. This gives you a physical location for briefs, content, meeting notes, reports, strategy docs, and handoff materials.

Set Up a Local Folder

"Set up a local folder for Acme at ~/Clients/Acme Corp"

This sets the client's local folder and creates an Armbrain/ subfolder structure:

~/Clients/Acme Corp/
  Armbrain/
    Briefs/
    Content/
    Meetings/
    Reports/
    Strategy/
    Handoff/

The path is stored on the client mind and persists across sessions.

How It Gets Used

Once a local folder is set, anything Armbrain generates lands in the right subfolder automatically:

• Meeting briefs go to Briefs/
• Content pieces go to Content/
• Meeting notes and follow-ups go to Meetings/
• Performance reports go to Reports/
• Strategy documents go to Strategy/
• Handoff exports go to Handoff/

Saving Output

When you ask Armbrain to save something, it writes the document to the client's local Armbrain folder.

Save a Brief

"Save that meeting brief to disk"

Armbrain writes the content to Armbrain/Briefs/2026-03-20-brief.md (auto-generated filename based on date and type).

Save with a Custom Filename

"Save the strategy document as q2-strategy-final.md"

Output Types

When No Local Path Is Set

If a client doesn't have a local folder set up, Armbrain simply skips the save (with a note) instead of erroring -- so you never lose work, you just won't see a file on disk until you set a folder.

Raw Document Tracking

When you ingest a document (a pasted transcript, a folder sync, or an auto-ingest), Armbrain keeps the full original text, not just the extracted memories. That gives you:

• Traceability: Every memory links back to the document it came from
• Re-extraction: Armbrain can re-process the original later with improved prompts to pull out more
• Audit trail: You can see exactly what was ingested and when

List Stored Documents

"Show me the documents stored for Acme"

You'll get the most recent source documents with where each came from, its size, how many times it's been processed, and when it was last processed.

Document-to-Memory Links

Every memory created from a document points back to its source, so you can always trace a fact to where it came from. (The same link is kept for any long note you store by hand.)

Watch Paths (Future)

You'll be able to point Armbrain at extra folders to watch for new documents, so files dropped there get ingested automatically. To set one up:

"Watch ~/Dropbox/Acme/Meeting Notes for new documents"

Practical Example: Organized Client Workflow

Setup (once per client):

"Set up a local folder for Acme at ~/Clients/Acme Corp"

After a meeting:

"Prep my meeting with Acme and save it"

Brief saved to ~/Clients/Acme Corp/Armbrain/Briefs/2026-03-20-brief.md.

Writing content:

"Write a follow-up email to Sarah about the Q3 budget discussion"
"Save that as a meeting note"

Email saved to ~/Clients/Acme Corp/Armbrain/Meetings/2026-03-20-meeting.md.

End of engagement:

"Generate a handoff document for Acme"

Handoff saved to ~/Clients/Acme Corp/Armbrain/Handoff/2026-03-20-handoff.md.

All outputs are organized, dated, and findable without Armbrain running.

Error Reference