# Fundamentals

## Overview

The Knowledge Manager is an AI-powered Digital Worker designed to put trusted, relevant answers directly in the flow of work for service and operations teams. It interprets questions in natural language, searches across every connected knowledge source simultaneously, and returns context-specific guidance with citations, so teams can act quickly and with confidence rather than spending time searching, second-guessing, or escalating unnecessarily.

Beyond retrieval, the Knowledge Manager continuously monitors interactions to identify missing, low-confidence, or conflicting knowledge. Where gaps are detected, it flags them automatically and supports structured content creation or enrichment, so the knowledge base evolves based on actual field demand rather than static documentation cycles.

## Key Benefits

**Answers at the point of need:** Guidance is delivered directly in Microsoft Teams or other configured interfaces, no system switching, no manual document browsing, no searching across multiple tools.

**Context-specific, not generic:** Responses are tailored to the specific asset, configuration, and operational scenario rather than returning broad documentation that may or may not apply.

**Trusted results with citations:** Every response includes source links so users know exactly where the guidance comes from and can assess its authority. Confidence indicators help users understand how reliable the answer is.

**Continuous knowledge improvement:** Every interaction generates signals about what knowledge is working, what is missing, and what needs review. Gaps are flagged automatically and draft knowledge can be generated for human approval, ensuring the knowledge base improves over time.

**Consistent outcomes across teams:** All users receive guidance drawn from the same validated sources, reducing the inconsistency that comes from relying on individual expertise or informal knowledge sharing.

**Governed by design:** Role-based visibility, escalation paths, and full auditability ensure that human oversight is maintained where it matters, particularly in high-compliance or safety-sensitive environments.

## The Challenge It Solves

Accessing knowledge across service operations is fragmented, inconsistent, and time-consuming. Engineers and agents typically search across multiple systems, manuals, SharePoint, ERP records, ticket histories, PDFs, often relying on incomplete or outdated information. Critical knowledge gaps go unidentified, leading to repeated issues, slower resolutions, and increased operational risk.

In practice, this looks like engineers spending 15 to 20 minutes per job on information lookup, searching 4 to 6 systems before finding a relevant answer, encountering conflicting guidance that applies to slightly different configurations, escalating to senior colleagues when documentation is unclear, and applying best-guess resolutions that may not fully resolve the issue. Knowledge from resolved jobs is rarely captured in a reusable form, so the same questions surface repeatedly.

## Before and After

### Before

Before the Knowledge Manager, resolving a field issue involves manual searching at every stage:

{% stepper %}
{% step %}
Search across multiple systems, manuals, SharePoint, tickets, emails
{% endstep %}

{% step %}
Interpret incomplete or unclear problem context
{% endstep %}

{% step %}
Review multiple documents and sources
{% endstep %}

{% step %}
Compare conflicting or generic guidance
{% endstep %}

{% step %}
Ask colleagues or escalate for support
{% endstep %}

{% step %}
Apply a best-guess resolution
{% endstep %}

{% step %}
Leave knowledge uncaptured or buried in free-text notes
{% endstep %}
{% endstepper %}

The result is high search effort, inconsistent answers, slow resolution times, and knowledge that never gets reused.

### After

With the Knowledge Manager, the same process runs in four steps:

{% stepper %}
{% step %}
Interpret the query, context, and asset configuration automatically
{% endstep %}

{% step %}
Retrieve, validate, and rank knowledge across all sources simultaneously
{% endstep %}

{% step %}
Deliver precise guidance and surface cited sources in a single response
{% endstep %}

{% step %}
Capture feedback and flag gaps for continuous improvement
{% endstep %}
{% endstepper %}

## How It Works

**When a question comes in:** the Knowledge Manager forms a working hypothesis before retrieving any information, interpreting the intent behind the query, identifying the asset type and configuration, assessing urgency and operational risk, and determining which knowledge sources are most relevant. It then searches all connected sources simultaneously and returns ranked results with confidence signals and citations.

**If the query lacks sufficient context for a high-confidence response:** the system asks a targeted follow-up question rather than returning generic guidance. When the right answer exists, it comes back as specific, actionable steps, not a document dump.

**Every interaction is tracked:** confidence levels, follow-up questions, resolution outcomes, and recurring patterns are all monitored in the background. This continuous monitoring powers the knowledge gap detection capability, ensuring that what engineers keep asking but can't find reliable answers to is surfaced for content review and enrichment.

**When a job is resolved:** the Knowledge Manager can convert the interaction and outcome into structured knowledge, drafted for human review and, once approved, published back into the knowledge base for future use.

## Knowledge Orchestration

The Knowledge Manager operates across five continuous functions:

**Seek:** A question is raised from the field or support desk. The Knowledge Manager captures context at source, asset ID, configuration, fault pattern, location, user role, risk level, and enriches the query before retrieval begins.

**Surface:** Unified search runs across structured and unstructured sources simultaneously, manuals, historical service logs, prior resolutions, bulletins, tickets, and safety updates. Results are ranked by reliability and contextual match. Generic or unsafe guidance is suppressed.

**Monitor:** The system continuously watches for changes that invalidate, improve, or create knowledge, source updates such as manual revisions and safety notices, changes in circumstances such as asset upgrades and firmware changes, and field outcomes such as confirmed fixes, rejected workarounds, and repeat visits.

**Strengthen:** Gaps, conflicts, and low-confidence guidance are detected automatically. The system highlights the difference between what teams keep asking and what the knowledge base can actually answer, flagging missing configuration steps, recurring searches, and unreliable sources for review.

**Generate:** Where knowledge is missing or repeatedly requested, the Knowledge Manager supports structured creation, drafting service log updates, proposing new content, generating configuration-specific guidance, routing everything through a human approval process before it is published back into the knowledge base.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kb.theloops.io/digitalworkers/ifs-loops-digital-workers/digital-worker-guides/knowledge-manager/core-concepts/fundamentals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.