Skip to content

Module 06 · Lesson 23

Build a knowledge base the agent can cite

Curate approved, current information with owners and retrieval boundaries.

Updated August 2026 · AI Agency Academy

What you will learn

Make a clear, safer operating decision.

You will be able to prepare a knowledge base that makes answers traceable to an approved source rather than a collection of loosely related documents.

Why this matters

Good agent work is useful before it is impressive.

Uploading every document is not knowledge management. An agent needs current, scoped material; clear ownership; a way to show what it relied on; and a stop rule when the answer is absent or uncertain.

Field note 23

Make the relationship visible.

Core concepts

The language that keeps the work clear.

Approved sourceContent the business has reviewed for this purpose and agrees is safe to use.
Saved on this device.
FreshnessWhether the source is current enough for the decision or customer question.
Retrieval boundaryThe limits on what collections, customer data, and document types may be searched for a job.
CitationA usable reference to the source or policy that supported an answer or recommendation.
The practical method

Work through the decision in order.

  1. 01

    Choose the first use case

    Build knowledge around a small set of recurring questions, not every document the business owns.

  2. 02

    Curate with owners

    For each source, name the subject owner, review date, audience, and permitted use.

  3. 03

    Make answers attributable

    Require a reference or source name when the agent gives a factual answer or explain that a person must confirm it.

  4. 04

    Retire stale material

    Create a simple review rhythm so old policy, product, and pricing documents stop influencing the workflow.

Worked example

A realistic, bounded implementation.

A SaaS company wants an agent to answer implementation questions. It starts with current onboarding guides, supported integration documentation, and a short escalation matrix owned by product support.

The agent retrieves only the relevant approved source, answers in plain language, and adds the source title to its internal handoff. If the question asks about a beta feature or a custom security condition, it does not infer an answer from a marketing page.

A monthly owner review removes retired guidance and adds the recurring unanswered questions that should become approved material.

Build it in practice

Use this copyable working template.

Adapt it to the client’s evidence, policy, people, and tools. Do not treat placeholders as approved instructions.

Source: [title]. Owner: [role]. Review date: [date]. Permitted question types: [list]. Do not use for: [list]. Citation or handoff format: [format].
Spacebrain implementation

Put the operating system around the agent.

Connect only approved knowledge, keep owner and review information in accessible records, and route unanswered or policy-sensitive questions into a human task with the search context preserved.

Practice

Before you move on

  • Choose ten high-value, approved sources for one pilot.
  • Identify two documents that should not be retrieved by the agent.
  • Test a question with no approved answer and confirm the agent stops.
  • Sources have owners and review dates.
  • The agent can show what supported an answer.
  • Stale or irrelevant material is excluded.
  • Unknown answers have a human route.

Put the learning to work

Build an AI service people can trust.

Create a free Spacebrain account and use the operating layer around your AI service.

Start for free