A company brain is the shared context that helps people and AI agents understand how a business works. In Hubzoid, that context lives in a Hub: instructions, reference knowledge, reusable procedures and tools maintained together.
It earns its place when people stop repeating the same explanations and agents apply the same current definitions.
At a glance
- Keep definitions, procedures, decisions and owners in the Hub.
- Reach live records through tools instead of treating an old export as today's truth.
- Keep shared knowledge separate from private conversations, credentials and workflow progress.
Keep what changes the answer
Ask a simple question of each piece of material: would an experienced colleague need this to do the work correctly?
| Material | Where it belongs | Why |
|---|---|---|
| Net-sales definition and reporting calendar | Reference knowledge | Several reports need the same meaning |
| How to prepare the weekly briefing | A reusable skill | The steps should stay consistent |
| Today's orders and stock counts | Their source systems, reached through tools | They change during the day |
| Large exports or background documents | Searchable raw material, with dates and sources | Useful to inspect without making every request read it all |
| Sensitive payroll details | A separate Hub or a restricted tool | The audience differs from the general team |
| Passwords and API keys | Protected configuration | The model should not read credentials |
A tool needing a credential is not automatically restricted. Its credential must be scoped to what every caller may do, or the capability needs an appropriate access boundary.
Search helps find material, ownership makes it trustworthy
Search can retrieve an old refund policy because its wording closely matches the question. That is a discovery problem and a maintenance problem, not proof that search is useless.
Keep the current policy easy to identify. Name its owner, effective date and source. Retire the old version from active context, while preserving history where the team can review it.
The Hub's curated notes help establish what is authoritative. Searchable material helps answer questions that need more detail. Both can be useful, provided the agent can distinguish current rules from historical records.
A shared brain is different from chat memory
Three things often get called memory:
- Conversation history helps continue one conversation.
- Workflow state records progress, such as which reporting periods were already handled.
- Shared knowledge describes facts and procedures the whole Hub relies on.
Hubzoid also supports learned knowledge saved when a permitted curator explicitly asks the agent to remember something. Those notes become shared context, so review them carefully. The permission is an access control, not a guarantee that every saved fact is correct.
Private uploads and casual statements should not become company policy by accident.
One maintained context can serve several ways of working
A teammate asks a question in chat. A workflow prepares the morning report. Another person uses their own assistant connected through MCP, the protocol for requesting another system's context and tools.
Each can use the relevant knowledge from the same Hub. They do not automatically share conversation histories, model settings or every capability. Access still applies to the caller and the channel.
Separate teams can have separate Hubs. Shared context is useful because it reduces repetition, not because every person should see every record.
Start with one repeated question
Pick a question the team asks every week. Write down its definition, source, owner and any exception. Add a procedure if the answer needs several steps, then a tool if it needs live information.
That small, maintained foundation is more useful than a pile of documents nobody is responsible for updating.
Next step: read memory and history to keep each kind of context in the right place.
For a practical tour, watch The brain in detail, episode 5 (opens in a new tab).
For the connection to your own assistant, watch Your own Claude, connected through MCP, episode 8 (opens in a new tab).