# Reading Review Reports



<a id="section-goal"></a>

Nothing the Agent writes becomes knowledge until it passes **Knowledge Review**. The Agent opens one HTML report for the whole current batch of candidate pages and waits for your answer. This report decides both the scope and the quality of what gets published, so it is worth reading with three questions in mind.


<a id="section-layout"></a>

## What is in the report

| Part | What it shows |
| --- | --- |
| Change overview | The batch at a glance, with the existing navigation and the expected file tree of the Context knowledge workspace |
| Navigation | Where each page will sit; pages without a placement are flagged so the Agent can bind them before asking you |
| Pages | Each candidate's title, path, summary and full rendered content, including diagrams and source citations. New pages are marked *New*; changed pages show the changed blocks next to the previous text |
| Revision notes | A note box per page; typing in it marks the page for revision |

Opening a page marks it READ in your browser. Read counts and notes are local conveniences, not approval. The revision counter lists every page with notes, and **Copy** exports them as plain text with article IDs and titles for pasting into the conversation.


<a id="section-three-checks"></a>

## Three things to judge

1. **Structure** — Are the topics, directories and pages divided the way readers will look for them?
2. **Content** — Do the pages carry the intended purpose, depth and style? Can a reader actually complete the promised task with them?
3. **Scope** — Is related material missing that should be included, or is something here that should be dropped?

Citations and placements alone do not prove a page is useful. Spot-check a few pages against their sources, especially defaults, conditions and steps.


<a id="section-answer"></a>

## Answering

```mermaid
flowchart LR
  rep["Review report"] --> a{"Your reply"}
  a -->|approve| ok["Approved into knowledge/"]
  a -->|notes only| fix["Agent repairs"]
  fix --> rep2["Updated report"]
  rep2 --> a
  a -->|notes + approve after fixing| fix2["Agent repairs and verifies"]
  fix2 --> ok
```

Reply in the conversation; no review code or magic phrase is needed.

| You say | What happens |
| --- | --- |
| Approve, or continue | The presented batch is approved |
| Revision notes only | The Agent repairs those pages, checks the result and shows an updated report |
| Notes plus "approve after fixing" | The Agent repairs, verifies the fix, and approves only the agreed pages without asking again |
| "Fix it and show me" | Editing only; it waits for your decision on the new report |

Silence, an ignored card or read progress is never approval. Rejecting a page leaves it out of this batch; it does not retire an already approved article.


<a id="section-partial"></a>

## Taking part of a batch now

You can approve the pages that are ready while others go back for repair. Approval alone does not build; to see the approved pages published before the rest are finished, ask for an early delivery. The Agent runs close and build for them, as long as they do not link to pages still pending, and then returns to the remaining review.


<a id="section-after"></a>

## After approval

Approval writes the pages to `knowledge/`. Close then rebuilds `knowledge/structure.yaml` and verifies the approved knowledge without rewriting its prose, and build produces the package and site. Nothing is published before approval.

---

## Sources

- [context/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md L12–L14 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md#L12-L14>)
- note:20261012/usage-practices.md · usage-practices.md L18–L18
- [context/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md L69–L90 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md#L69-L90>)
- [context/packages/context/docs/guides/agent-guide.md L111–L122 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context/docs/guides/agent-guide.md#L111-L122>)
- note:20261012/usage-practices.md · usage-practices.md L16–L22
- [context/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md L142–L152 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md#L142-L152>)
- [context/packages/context-cli/context-workflow/resources/dialogue/knowledge-review.md L9–L37 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context-cli/context-workflow/resources/dialogue/knowledge-review.md#L9-L37>)
- [context/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md L92–L94 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md#L92-L94>)
- [context/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md L132–L140 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context-cli/context-workflow/resources/procedures/knowledge-review.md#L132-L140>)
- [context/packages/context/docs/getting-started.md L133–L136 · 3b0ce0a](<https://github.com/context4ai/context/blob/3b0ce0a0a1761f5fceb3bb48fb9dc29b54c0786b/packages/context/docs/getting-started.md#L133-L136>)