Knowledge Foundation: 20 questions about building the knowledge base before AI.

It is the governed basis of knowledge, criteria and responsibilities that prepares an organization to work with AI. It includes source map, authority, versions, permissions, vocabulary, examples, boundaries, owners, and proofs; it is not just a repository or a vector base.

It resolves the documentary dispersal, the contradictory versions and the knowledge that only lives in the head of some people. It allows teams and agents to find a response with context and know when there is not enough evidence.

A search tool retrieves documents. The Foundation explains which documents are valid, for which question, who can see them and what happens when they disagree. It adds governance to content, not just access technology.

It makes sense before agents, internal assistants, RAG or automations that depend on their own information. Also when people waste time searching, duplicate materials or solve the same question differently.

It is not a priority if the use case does not need own knowledge or if the job is purely deterministic. Nor should it be turned into an encyclopedic project without a specific mission that indicates what must be ordered first.

First, it defines the mission to be fed and the questions to be answered. Then sources, owners, conflicts, gaps, permits and quality criteria are identified.

Procedures, policies, brand guides, examples, glossaries, internal FAQs, catalogs and operational records when necessary. Each source needs useful metadata: owner, validity, scope and level of access.

Participants include process experts, document managers, users, technology and privacy or security according to the data. A person must be able to decide which source prevails when there are contradictions.

The AI can classify, extract, propose metadata, detect duplicates, and retrieve relevant fragments. His proposals speed up ordination, but authority and validity cannot be inferred by semantic similarity alone.

People validate authority, permissions, versions, exceptions and criteria. They also decide when a source expires, who can update it, and what the system should do in the face of a vacuum.

Tools are chosen according to formats, volume, permissions, integrations, search, versioning and traceability. The platform is secondary to the knowledge architecture; a well-defined Foundation can evolve technologically.

Ideally respect repositories that are already canonical and avoid uncontrolled copies. Connectors must retain identity, permissions and updates or clearly indicate when working with a replica.

A first Foundation for a delimited mission can be built in phases. Time depends on the number of sources, documentary quality and the ability of experts to resolve contradictions.

The investment depends on the corpus, the complexity of the permissions, the integrations and the level of cleaning or creation of content. It also includes editorial maintenance and governance, not just initial indexing.

It is measured by search time, question coverage, correct citations, errors by source, pending content review and actual use. In agents, also for quality improvement before and after using the Foundation.

The most common mistakes are ingesting everything, ignoring versions, mixing public and restricted documents, or relying on file names. Another flaw is not preparing test questions before building.

It is tested with real queries, questions with absent answers, conflicting versions and users with different permissions. A good test checks both what the system finds and what it must reject or scale.

It needs accountability, review dates, expiration alerts, change log and a way to report errors. If the canonical source changes, the Foundation must reflect it without opaque manual reconstructions.

Yeah. A SME can start with a single process and a few critical sources. The value is to make explicit the criterion and reduce dependencies, not accumulate documentary volume.

Karmina starts with mission, questions, and ownership; then sorts sources, criteria, permissions, and tests. The Foundation is designed to serve people today and agents when the process is ready.