What a company brain captures (and what it doesn't)

The first question in every demo is some version of: "Are you copying all our Slack?"

Fair question. A lot of "AI memory" products sound like surveillance with a chatbot skin. Ignius is built on the opposite premise: capture less, but capture what matters, and only with consent.

For the full overview of what a company brain is and how the capture loop works, start with What is a company brain?.

What gets stored

When someone saves a decision in Ignius, they store a confirmed judgment: a vendor call, a piece of repeatable expertise, a slice of a ticket or PR, or a process that describes how work actually flows. Each decision includes a summary, a source link, a confidence level, and folder membership in your Company Brain.

That is structured memory, not a raw export. Search tools index everything written. A company brain indexes what someone decided was worth keeping.

What does not get stored (by default)

Ignius does not ingest a full Slack workspace history, private messages nobody confirmed for capture, or automatic saves without a human in the loop. There are no employee activity timelines for manager dashboards.

Connect integrations (Office, GitHub, Xero, and others) operate as read-only signals. They identify decisions as they are made and surface candidates in a capture inbox. Nothing becomes permanent until someone approves it. Control access and permission for everyone. If compliance asks "what did you ingest?", the honest answer is: only what a human confirmed.

Private folders stay private until someone publishes to a team layer. Company Brain is opt-in on the same engine as personal memory.

Folders in your Company Brain

A company brain without boundaries becomes another noisy search index. Ignius uses context groups: folders in your Company Brain like Operator, Portfolios, Partner, or Employee.

When someone Ask inside a folder, retrieval stays in that bucket. A finance question does not pull unrelated eng threads. All evidence stays inside the decision it is attached to. How context groups keep answers scoped walks through what goes wrong when everything shares one retrieval space.

A concrete example

Say #finance resolves a $62k shipper dispute on a Thursday afternoon. Finance and legal agree on escalation thresholds. Someone reacts with a checkmark emoji. The thread scrolls away.

By Monday, half the team has forgotten the details. Search might find the thread if someone remembers the right keywords. It will not tell you "this is the current escalation path" with a confidence score.

In Ignius, whoever was in the thread gets a candidate. They confirm it in ten seconds. The decision lands in Operator with a link back to Slack. Next time someone asks in Ask, they get the call and the source, not a paraphrase over 400 messages.

That is the difference between retrieval and memory creation. Glean searches memory. Ignius creates it. goes deeper on the category split.

Can other models use this context?

Yes, in Work, for generation. Ignius still owns the folders, decisions, and graph. Teams can export a context packet to Claude or another model when needed. The brain stays canonical; external models are consumers of scoped context.

Ignius is not trying to be the only LLM a team uses. It is trying to be the place where confirmed judgment lives.

What about employer visibility?

If someone joins a team domain, they choose what to publish. Unpublished personal folders are theirs. Team baskets are shared only when they put decisions there deliberately.

This matters for adoption. Tools that feel like homework or monitoring do not get used. Tools that save time first, then optionally share upward, can spread.

Company brain vs wiki vs search

People often ask how this differs from Confluence or Notion. Wikis want polished pages written after the fact. Search finds what was already written somewhere. A company brain captures the decision while context is still warm, with a human saying yes.

If the wiki graveyard is full of ADRs with three entries from 2021, that is common. Why your wiki doesn't stop Slack pings walks through why mandates fail and what teams do instead.

The line Ignius draws

If using Ignius feels like surveillance, the product missed the point. It should reduce repeat explanations for the person doing the explaining, not create a compliance archive nobody trusts.

For capture from Slack specifically, see When Slack decisions never become docs. For the team layer, see Company Brain.

FAQ

Are you copying all our Slack?

No. Connect integrations surface candidates in a capture inbox. Nothing becomes a decision until a human confirms it. Ignius does not batch-ingest workspace history or scrape DMs. If a thread never gets approved, it never enters the brain. That is by design: the product fails if people treat capture as surveillance.

What is a company brain?

Structured memory built from decisions, expertise, processes, and artifact slices that someone on the team chose to save. Each decision has a summary, a source link, a confidence level, and a folder in your Company Brain. Ask queries those decisions with citations. See What is a company brain? for the full overview and capture loop.

What gets stored in a decision?

Confirmed judgments: vendor choices, escalation paths, repeatable expertise, relevant slices of tickets or PRs, and processes that describe how work actually flows. Not raw chat exports. A decision is typically one paragraph of summary plus provenance, not a transcript.

What are context groups?

Folders in your Company Brain, like Operator, Portfolios, Partner, or Employee. When someone Ask inside a folder, retrieval stays in that bucket. Groups can be private, team-scoped, or published upward. See How context groups keep answers scoped.

How is this different from enterprise search?

Search indexes what was written and retrieves relevant chunks. A company brain captures what was decided, often before anyone wrote a doc, with human confirm and provenance per decision. Search answers "where is the doc?" A company brain answers "what did we decide, and who said so?" Glean searches memory. Ignius creates it. goes deeper.

Can my employer see my private groups?

Not until someone publishes to a team layer. Private folders stay private. Team and company baskets are opt-in. Ignius is not built as an employee monitoring tool.

Which integrations work at launch?

Connect supports Office, GitHub, Xero, Slack, Jira, and others as read-only signals. They identify decisions as they are made and feed the candidate list and capture prompts. Control access and permission for everyone. Confirm before anything becomes permanent memory.

Request early access to try Company Brain with your team.