How Armbrain adds shared marketing expertise to search results with client-specific memories.
What Is System Knowledge?
When you search for something in Armbrain, you get results from two sources:
- Your client mind - the specific notes, decisions, preferences, and history you have stored for this client
- System knowledge - a shared corpus of marketing methodology, Business OS operational knowledge, proven playbooks, and templates maintained by the Armbrain team
You do not interact with system knowledge directly. There is no tool to manage it and no setting to configure. It works behind the scenes, adding relevant marketing expertise to search results.
How It Works
When you search with search_memory, Armbrain runs two parallel queries:
- Your active client mind's memories (same as always)
- The system knowledge corpus (new)
Results are blended together and ranked by relevance. Your client-specific memories always outrank system knowledge at equal relevance scores - your notes about your client are more valuable than generic best practices.
Each result is labeled so you can tell where it came from:
- [client mind] - from your client mind. This is information you or your team stored.
- [system] - from the shared knowledge corpus. This is curated marketing expertise.
System knowledge results are capped at 3 per search to keep results focused on your client data.
When You Will See It
System knowledge appears when your search query matches topics in the shared corpus. Examples:
Methodology Searches
"How should I structure a quarterly planning session?"You might get:
- [client mind] Acme Corp's Q1 planning notes and what worked
- [system] Business OS quarterly planning framework and best practices
- [client mind] Your decision to use 90-minute sessions for Acme
Template Searches
"Content calendar template"You might get:
- [client mind] Acme Corp's current content calendar structure
- [system] A reusable content calendar template from the corpus
Process Searches
"Client onboarding checklist"You might get:
- [system] First 90 days onboarding framework
- [client mind] Your notes on what worked during the BetaCorp onboarding
What Is in the Corpus
The system knowledge corpus covers core fractional CMO domains:
| Topic | What It Includes |
|---|---|
| Business OS/Traction | L10 meeting format, rocks, scorecards, quarterly planning, accountability charts |
| Sales | Discovery call frameworks, proposal structures, objection handling |
| Content | Content strategy, calendars, SEO workflows, blog processes |
| Branding | Brand voice development, positioning frameworks, messaging |
| Analytics | KPI selection, reporting templates, attribution models |
| Sequences, deliverability, segmentation strategies | |
| Paid media | Budget allocation, campaign structures, platform selection |
| Strategy | Go-to-market planning, competitive analysis, market research |
| Onboarding | First 90 days with a new client, discovery process |
| Handoff | Engagement wind-down, knowledge transfer, exit documentation |
The corpus is curated and maintained by the Armbrain team. Content is reviewed for accuracy and relevance before being added.
Your Data Always Wins
The most important thing to understand: your client-specific memories always rank higher than system knowledge at equal relevance. A note that Acme Corp prefers 60-minute L10 meetings outranks generic Business OS guidance recommending 90 minutes.
System knowledge fills gaps, not replaces what you know. If you have not stored anything about a topic for a client, the corpus provides a baseline. Once you add your own notes, those take priority.
Tips
- You do not need to do anything. System knowledge works automatically. Just search as you normally would.
- Check the source label. When a result says [system], it is generic best-practice advice. When it says [client mind], it is specific to your client. Both are useful, but context matters.
- Store client-specific variations. If a client does something differently from the standard methodology (shorter meetings, different KPIs, unique reporting cadence), store that as a memory. It will rank higher than the generic version in future searches.
- Use system knowledge as a starting point. When you start a new engagement, system knowledge gives you frameworks before you have built up client-specific data. As you learn about the client, your memories take over.