Guides
Context & the Brain
The living company memory that makes every answer consistent, current, and sourced.
The Brain is HiveBase's shared memory. Instead of context scattered across Slack, docs, meetings, and tickets, the Brain holds it in one place — structured, sourced, and current — so every person and every agent answers from the same truth.
- 01Your toolsSlack · Gmail · Meetings · …
- 02Signal EngineCapture
- 03Typed claimsWith provenance
- 04Company BrainShared truth
- 01
Your tools
Slack · Gmail · Meetings · …
- 02
Signal Engine
Capture
- 03
Typed claims
With provenance
- 04
Company Brain
Shared truth
How context gets in
You don't fill the Brain by hand. As you connect tools, HiveBase reads what's happening and extracts typed, sourced claims through its Signal Engine. Each claim links back to exactly where it came from.
Capture
Signals stream in from connected tools — messages, transcripts, PRs, records.
Understand
HiveBase extracts typed claims (accounts, decisions, people, dates) and attaches provenance — the source, the actor, and the evidence.
Reconcile
New signals update the record. Conflicts are held for review instead of overwriting.
Reuse
Every answer, brief, and agent draws on the same record.
Better than a pile of notes
A folder of Markdown notes is just text. The Brain is a structured record — which is what makes answers trustworthy and reusable.
| Markdown notes | HiveBase Brain | |
|---|---|---|
| Structure | Free text | Typed claims (entity, kind, confidence) |
| Provenance | Maybe a link | Source, actor, and quoted evidence on every claim |
| Freshness | Whatever you last edited | Continuously updated from live signals |
| Conflicts | Silently overwritten | Held for review; history preserved |
| Reuse | Copy-paste | Read by FYI, Tasks, Squads, and any AI |
Anatomy of a claim
Every fact in the Brain is more than a sentence. It carries the metadata that makes it auditable:
statementtextThe fact itself — e.g. "Acme's renewal is at risk over SSO."
entitytypedWhat it's about — ACCOUNT · Acme Corp — so it connects to everything else
about Acme.
provenancesourceWhere it came from: the source, who said it, and the quoted evidence.
confidencesignalHow sure HiveBase is, so low-confidence claims don't masquerade as fact.
validityhistoryWhen it was true. Superseded claims are kept, not deleted.
What makes it trustworthy
- Every claim carries its source — answers are auditable, not vibes.
- Freshness matters: newer signals update the record, and history is kept.
- When two sources disagree, the contradiction is held for review, not silently resolved.
- Nothing is overwritten — prior versions remain.
Held, not guessed
When a new signal contradicts an existing claim, HiveBase flags it for review rather than picking a winner. You stay the source of truth on the calls that matter.
Searching and asking
Ask the Brain in plain language and get a sourced answer instead of a list of links:
| You ask | You get |
|---|---|
| "What changed with Acme this week?" | A sourced summary of recent signals |
| "What did we decide about pricing?" | The decision, who made it, when — with evidence |
| "What's blocking the launch?" | Open risks pulled from messages, docs, and meetings |
Because the same Brain backs every surface, you get the same answer in the app, in your daily FYI, and through any connected AI client.
Decisions
Important calls can be recorded as decisions — immutable, searchable, and linked to the context behind them. Later, you (or an agent) can see not just what was decided but why, and close the loop on how it turned out. Developers can read and write decisions over the API.
Shared substrate, not the whole product
Tasks, FYI, and Squads all run on the Brain — the more accurate and sourced it is, the better every surface gets. Memory alone is not enough: HiveBase also coordinates what agents do (approvals, receipts, verification, undo). Context layers decide what agents can see; HiveBase also governs action.