> ## Documentation Index
> Fetch the complete documentation index at: https://saydo-5cd0e3d7.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Coverage Indicators

> Coverage tags on every wiki section tell you and your agent when to trust the wiki and when to read the raw source files.

## What Coverage Indicators Are

Every section in every topic article carries a coverage tag that records how many source files contributed to that section and how well-synthesized it is. This lets Claude — and you — make a fast, informed decision: read the wiki section and move on, or go deeper into raw files.

## The Three Levels

<CardGroup cols={3}>
  <Card title="High" icon="circle-check">
    **5 or more sources**

    The section is well-synthesized and recently compiled. Trust it directly and skip the raw files.
  </Card>

  <Card title="Medium" icon="circle-half-stroke">
    **2–4 sources**

    Good overview, but may miss detail on granular questions. Check raw sources if you need specifics.
  </Card>

  <Card title="Low" icon="circle-xmark">
    **0–1 sources**

    Sparse data. Read the raw sources listed in that section directly rather than relying on the wiki.
  </Card>
</CardGroup>

## What Coverage Tags Look Like

Coverage tags appear inline in each section heading:

```markdown theme={null}
## Summary [coverage: high -- 15 sources]
...trust this, it's well-sourced...

## Experiments & Results [coverage: medium -- 3 sources]
...decent overview, check raw files for details...

## Gotchas [coverage: low -- 1 source]
...read the raw gotchas.md directly...
```

The tag format is always: `[coverage: {level} -- {N} sources]`

<Tip>
  Coverage varies by section within the same article. A topic might have a high-coverage Summary (synthesized from 15 meetings) and a low-coverage Gotchas section (only one source mentions it). Read accordingly.
</Tip>

## How Your Agent Should Use Coverage

The most effective pattern is to have Claude apply coverage-aware reading automatically. You do this by adding a knowledge base block to your `AGENTS.md` or `CLAUDE.md`:

```markdown theme={null}
## Knowledge Base

A compiled knowledge wiki is available at `{your output path}/`.

**Session startup:** Read `wiki/INDEX.md` for a topic overview, then read
specific topic articles relevant to your current task.

**Using coverage indicators:** Each section has a coverage tag:
- `[coverage: high]` -- trust this section, skip the raw files.
- `[coverage: medium]` -- good overview, check raw sources for granular questions.
- `[coverage: low]` -- read the raw sources listed in that section directly.

**When you need depth:** Check the article's Sources section for links to
raw files. Only read raw sources for medium/low coverage sections or when
you need very specific detail.

**Never modify wiki files directly** -- they are regenerated by `/wiki-compile`.
```

Once this is in your `AGENTS.md`, Claude uses coverage indicators automatically every session — no special commands needed.

<Note>
  The Sources section at the bottom of every article lists backlinks to every raw file that contributed. For medium and low coverage sections, these links tell Claude exactly which files to read — no broad scanning required.
</Note>

## The Practical Tradeoff

Coverage indicators give you the speed of a compiled wiki without sacrificing accuracy on sections that need depth.

| Coverage | Agent behavior                                            | Token cost |
| -------- | --------------------------------------------------------- | ---------- |
| `high`   | Reads wiki section, continues                             | Minimal    |
| `medium` | Reads wiki section, may check 1-2 raw files for specifics | Low        |
| `low`    | Skips wiki section, reads linked raw files directly       | Normal     |

In practice, most heavily-used topics accumulate high coverage quickly. The `[coverage: low]` tag is most useful for newly discovered topics or sections that haven't had many sources classified into them yet.

<Tip>
  Run `/wiki-lint` to get a report of all low-coverage sections across the wiki. This shows you where the compiled knowledge is thin and which raw files you might want to add more detail from.
</Tip>