Twitter/X

Corey Ganim prescribes seven non-negotiables for a company knowledge base…

2026-07-27 · 22:11 UTC ·@coreyganim ·2 min read

Brief

Corey Ganim lays out seven non-negotiables for the knowledge layer agents need: a single canonical home per fact, function-based organization, explicit provenance and sensitivity metadata, a protected tier for private data, bounded agent permissions, distillation of raw inputs into durable facts, and ongoing maintenance — arguing a governed KB should precede agent rollout to become a competitive moat.

Why it matters

Corey Ganim prescribes seven non-negotiables for a company knowledge base, starting with the rule “one fact has one home” to prevent duplicates (e.g., pricing must have a single canonical source).

Key details

  • Knowledge must be organized by function (company, customers, offers, marketing, sales, operations, market intelligence, integrations, finance) and every fact needs provenance: source, owner, sensitivity, last review, and status (current/experimental/planned).
  • Sensitive data must live in a protected tier with safe pointers in the KB; agents get bounded access (e.g., sales agents can read sales context but cannot rewrite finance policy), and the KB requires an owner, intake process, validation, and regular cleanup as maintenance.
Source evidence

HOW TO BUILD THE KNOWLEDGE LAYER EVERY AI AGENT NEEDS

before agents can be truly effective they need a strong context layer to operate from.

A real company knowledge base has a few non-negotiables:

  1. One fact has one home.

Pricing does not live in a proposal, a Slack thread, three spreadsheets, and the founder's memory.

There is one canonical source. Everything else points back to it.

  1. Knowledge is organized by function.

-Company.
-Customers.
-Offers.
-Marketing.
-Sales.
-Operations.
-Market intelligence.
-Integrations.
-Finance.

The exact map will change by business, but the rule stays the same: an agent should know where to look before it starts guessing.

  1. Every important fact has context.

-Where did it come from?
-Who owns it?
-How sensitive is it?
-When was it last reviewed?
-Is it current, experimental, or planned?

Without this, an agent can retrieve information but cannot judge whether it should trust it.

  1. Private data has a protected tier.

Credentials, customer records, contracts, and other sensitive information do not belong in the same place as general operating knowledge.

The knowledge base can hold a safe pointer. The protected system holds the actual record.

  1. Agents get boundaries, not unlimited access.

A sales agent can read company context and maintain sales knowledge.

It should not be able to rewrite finance policy because it found a conflicting note in a call transcript.

  1. Raw information has to be distilled.

Calls, emails, CRM updates, and documents are inputs.

They do not become durable company memory until someone or something reviews them, places the fact in the right home, and resolves conflicts.

  1. Maintenance is part of the product.

A knowledge base that is correct once and ignored for six months becomes a more convincing source of wrong answers.

It needs an owner, an intake process, validation, and a regular cleanup cadence.

This is why I would lead with the knowledge base before the agent.

Once the company has one governed source of truth, every future AI project gets easier:

-New agents start with context.
-Humans stop hunting for answers.
-Workflows share the same rules.
-The business is less dependent on one person's memory.

a company's organized, governed, current operating knowledge is a massive moat, one of the few that are left in the AI age.