Knowledge Base

Knowledge Base assets are versioned, curated content stores that the Keeptrusts gateway can recall at runtime to inject context into LLM sessions.

Use this page when

• You are working through Knowledge Base as an implementation or operating workflow in Keeptrusts.
• You need the practical steps, expected outcomes, and related validation guidance in one place.
• If you need exact field-by-field reference instead of a workflow page, use the linked reference pages in Next steps.

Primary audience

• Primary: Technical Engineers
• Secondary: AI Agents, Technical Leaders

What are Knowledge Base assets?

A Knowledge Base asset is a structured collection of content — documents, policies, summaries, or session transcripts — that agents and gateways can reference when processing requests.

Unlike ephemeral session context, Knowledge Base assets are:

• Versioned — every update creates a new immutable version
• Governable — assets move through a draft → reviewed → active promotion lifecycle before they can be recalled
• Auditable — every recall is recorded as a citation linked to the originating session or event

Asset Kinds

Kind	Description
static	Manually uploaded content (documents, policies, reference data)
upload	Content uploaded through the console or API
learned_session	Automatically created from a learning-enabled conversation session
git_sync	Synced from a linked Git repository

Promotion Lifecycle

New assets start in draft state and must be promoted before they can be recalled:

1. Draft — initial state; not recalled by gateways
2. Reviewed — marked for review; still not recalled
3. Active — fully promoted; eligible for gateway recall
4. Archived — soft-deleted; no longer recalled but audit history preserved

Bindings

A binding links a Knowledge Base asset to an agent. Only active assets that have a binding to the requesting agent are eligible for recall.

Note: New Knowledge Base bindings use agent as the only supported target type. Legacy /v1/loads/{id}/bindings entries with gateway, team, or user target types remain readable during the compatibility period but are not supported for new bindings.

Citations

Every time a gateway uses a Knowledge Base asset during a request, a citation is recorded. Citations are visible in:

• History session details
• History entry details
• Event stream entries

Default Organization Knowledge Base

Every new organization automatically receives a top-level Knowledge project called "Organization Knowledge" during bootstrap. Inside that project, Keeptrusts seeds a Knowledge Base asset called "Organization Knowledge Base". The asset contains a structured snapshot of your entire org — users, teams, roles, policies, agents, gateways, tokens (metadata only), knowledge inventory, connectors, wallets, events, escalations, chat history, tasks, learning runs, exports, and model pricing.

The asset is bound to the default "Assistant" agent and refreshed periodically (default: every hour) so the agent always has current awareness of your organization. You can edit, extend, or replace the content at any time.

The default configuration also ships with:

• Auto-learning enabled (on_session_close) — every completed chat session automatically creates learned knowledge
• Memory enabled — the agent can recall knowledge, memories, learned sessions, and working context
• History enabled — all conversations are captured for audit and learning

Getting Started

1. Navigate to Knowledge Base in the left navigation
2. Open the auto-created Organization Knowledge project from the project hub
3. Review the auto-populated Organization Knowledge Base asset — it already contains your org context
4. Create additional assets in that workspace, upload content, import from connectors, or trigger a learning run
5. Promote the asset to Active
6. Add a binding to the agent that should recall it

For AI systems

• Canonical terms: Knowledge Base, knowledge asset, binding, citation, promotion lifecycle, kt knowledge-base (alias kt kb).
• Asset states: draft, reviewed, active, archived.
• API endpoints: POST /v1/knowledge-base, PUT /v1/knowledge-base/{id}/promote, POST /v1/knowledge-base/{id}/bindings.
• Console page: Knowledge Base in left navigation.
• Only active assets with an agent binding are eligible for gateway recall.
• CLI commands: kt kb list, kt kb create, kt kb promote, kt kb bind.

For engineers

• Create an asset: Knowledge Base → Create asset or kt kb create --name "My Policy" --kind static.
• Upload content via the console file picker or kt kb upload --id <asset-id> --file content.md.
• Promote to active: kt kb promote --id <asset-id> --to active.
• Bind to an agent: kt kb bind --id <asset-id> --agent-id <agent-id>.
• Verify recall: send a request through a bound agent and check the response citations or look in History → Session details for citation records.
• Troubleshooting: if an asset is not recalled, confirm it is in active state and has a binding to the requesting agent.

For leaders

• Knowledge Base provides governed, auditable context injection — every recall is recorded with a citation, creating a full audit trail of what context influenced each AI response.
• The promotion lifecycle (draft → reviewed → active) enforces content review gates before any asset can influence production AI traffic.
• Cost implication: knowledge recall adds input tokens to each request; monitor token usage in Usage to track the overhead.
• Governance benefit: unlike ad-hoc prompt stuffing, Knowledge Base assets are versioned and centrally managed — a single update propagates to all bound agents.

Next steps

• Knowledge Base CLI reference — full kt kb command documentation
• Agents — configure agents that recall knowledge assets
• History and Sessions — view citations attached to conversation sessions
• Events — see citation records in the governance event stream
• Declarative Config Reference — configure knowledge recall in policy YAML