> ## Documentation Index > Fetch the complete documentation index at: https://docs.ainomos.ch/llms.txt > Use this file to discover all available pages before exploring further. # Knowledge Health > Find and fix what is wrong with a room's knowledge, and read the room's knowledge graph. Ainomos checks every room's knowledge regularly for problems that make answers less reliable, such as an exception that ran out but is still recorded as approved, or two rules that contradict each other. Each problem is a finding. The **Knowledge Health** page lists the open findings of your rooms so you can fix them, or record why you will not. Who can do this: room owners and curators, including a curator named for the room's memory. The page lists the findings of every room where you hold one of these responsibilities. ## Open Knowledge Health Knowledge Health is not in the sidebar. You reach it in two ways: * On the **Usage** page, select the **open high-severity findings** card, or **View all** under **Findings by status**. * In the [Inbox](https://docs.ainomos.ch/chat/inbox.md), findings arrive as **Knowledge finding** items. You can decide them there too. ## What the page shows The first line counts the **Open high-risk findings**. Below it, findings are grouped by severity: **High**, **Medium** and **Low**. Each row shows: * **The title.** Select it to show the full text with a suggested remedy, in your organisation's content language. * **The affected object**: its kind, name, room and a short ID. An object in a room you cannot see is not named. * **The check** that raised it, and how it was found: **Rule-based** (a fixed check), **Semantic** (a model judged it, with its **Confidence**) or **Runtime** (something failed while Ainomos worked). * **The room**, and the actions **Acknowledge**, **Resolve** and **Won't fix**. When nothing is open, the page says **No open findings.** ## What each finding means and what to do | Check | Severity | What it means | What to do | | - | - | - | - | | **Validity expired, stored approval not cleaned up** | High | An exception's end date has passed. It no longer applies, but it is still recorded as approved. | On the [Exceptions](https://docs.ainomos.ch/knowledge/exceptions.md) page, renew the exception or close it. | | **Inheritance conflict** | High | A room has an approved exception to a hard rule it inherits from a room above. Hard rules allow no exception. | Revoke the exception, or ask the owners of the rule's room whether the rule should be a guardrail instead. | | **Reference to a missing rule** | Medium | A knowledge entry names a rule that has no active rule behind it. | Create the rule, or correct the entry that names it. | | **Stale knowledge object** | Medium | An entry, usually a document, has passed its **Valid until** date. Answers no longer quote it. | Bring in the newer edition, or extend the date with **Edit details** on the [document](https://docs.ainomos.ch/knowledge/documents.md). | | **Semantic contradiction** | Medium at most | A model suspects that two active rules in the same room contradict each other. This is a suspicion, not a proof. | Read both rules. Change or retire one, or choose **Won't fix** if they do not conflict. | | **Orphaned knowledge object** | Low | A memory, other than a room's own, holds no entries at all. | Fill it, or choose **Won't fix** if it is meant to be empty. | | **Evidence gap** | High | An action took effect, but its evidence record could not be written. Ainomos does not write it later. | Once the cause is fixed, saving the change again writes a fresh record. Then resolve the finding. | A semantic finding is filed only when the model is at least 70% confident, and it never counts as high severity. In the Inbox, it opens with both sources side by side. ## Decide a finding Select one of the three actions on the row, then confirm it in the **Decide finding** dialog. | Action | When to use it | What happens next | | - | - | - | | **Acknowledge** | You have seen the finding and will deal with it later, or it is known and accepted. | It leaves the open list. If the problem changes, it opens again. | | **Resolve** | You have fixed the problem. | It leaves the open list. If the next check still finds the problem, it opens again. | | **Won't fix** | You decided not to fix it, for example because the contradiction is not real. | It leaves the open list. If the problem changes, it opens again. | Your decision is recorded with your name and the time. ## Findings that close by themselves Ainomos runs the checks again on a schedule. When the problem behind a finding is gone, for example because someone renewed the exception, the next check closes the finding. A semantic finding closes this way only after a run in which the semantic check itself worked. An evidence gap never closes by itself. > [!NOTE] > > Knowledge Health does not list documents without an owner. The **Usage** page counts **stale or ownerless entries** and links to the **Documents** page, where a missing owner shows as a dash. ## The Graph page The **Graph** page draws a room's knowledge as a map: records, people, exceptions, documents and access grants as dots, their links as lines. Use it to see how a room's knowledge connects and what a change would touch. Who can see this: members of the room, unless your organisation has switched the knowledge graph off for standard users. People with a responsibility keep it. Without access, the page shows the list. See [visibility](https://docs.ainomos.ch/privacy/visibility.md). **1. Open the Graph page** Open **Knowledge**, then **Graph**. On the Knowledge page you can also choose **Map** under **Show as**. **2. Read the map** The room you picked sits in the middle with its records and people, and the rooms above and directly below it sit around it. The key at the top left names and counts each kind of dot. A dashed line is a proposed link that has no effect yet. **3. Select a dot** A card opens with the dot's links. For a record, **Open record** opens it. For a person, the card shows their **Role in this room** and the rooms they are **Also in**. For another room, **Go to room** moves the map there. The filters above the map work as on the list: search, kind and state narrow what the map draws. **Map controls** at the top right opens these settings: | Control | What it does | | - | - | | **Focus: selection + neighbours only** | Hides everything except the selected dot and its direct links. | | **Layers on the map** | Turns **Records**, **People**, **Exceptions**, **Documents** and **Access** on or off. Records and people are on at first. A layer that is off shows as a count on the room. | The buttons on the map frame the view: **Fit selection**, **Show whole graph** and **Back to last focus**. ### Type relations Room owners and curators see **Type relations** below the map. It looks at the room's links that have no relation type yet and proposes one for each. Nothing changes until you accept the proposals in the [Inbox](https://docs.ainomos.ch/chat/inbox.md). ## Related * [Knowledge overview](https://docs.ainomos.ch/knowledge/overview.md) * [Exceptions](https://docs.ainomos.ch/knowledge/exceptions.md) * [Dreaming](https://docs.ainomos.ch/knowledge/dreaming.md) * [Inbox](https://docs.ainomos.ch/chat/inbox.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.