> ## Documentation Index
> Fetch the complete documentation index at: https://docs.northernlogic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge maintenance

> Give pages owners, review sources, and turn incoming material into dependable reference.

**Outcome:** your team knows which knowledge to trust and how to improve it.

The practices below are a working routine you establish. Writing an owner or
review date in Markdown does not create an automatic assignment, notification,
or verification badge.

## Give important pages a small maintenance header

```md theme={null}
- **Owner:** Operations lead
- **Status:** Draft — awaiting review
- **Last reviewed:** 2026-09-05
- **Review again:** 2026-10-05
- **Source:** Link to the approved procedure or decision
```

Use real names or team responsibilities your colleagues recognize. After review,
update the status and date in the saved page. Keep a clear title, purpose, and
source links near the top.

## Process incoming material

1. Put unreviewed material in your wiki's `inbox/`, or another clearly labeled
   folder.
2. Check the source and distinguish its claims from your team's decisions.
3. Merge useful facts into the appropriate page; preserve provenance in
   `sources/` when using the wiki structure.
4. Update the index and links so people can find the result.
5. Ask an authorized teammate for a focused [review](/collaboration/follow-ups).

## Handle disagreement explicitly

Two pages can contradict each other even without a sync conflict. Ask the
responsible person to decide which statement is current. Record the decision,
update affected pages, and label superseded material. Do not ask an agent to
silently choose an authoritative policy.

A [sync conflict](/knowledge/conflicts) is a different problem: competing edits
to the same entry need resolution.

## Make a weekly review practical

Choose a small set of frequently used pages. Check for outdated steps, broken
references, missing owners, and unanswered questions. Use **Activity** to
inspect changes, especially after an agent edits several pages. Move retained
old material to a clearly labeled archive and fix incoming links; a folder named
`archive` is an organizational convention, not a guarantee that search will
exclude it.

For a Northern Logic Wiki, [maintenance skills](/library/wiki) can assist. Their
schedule runs in your chosen harness. Confirm that it exists, can access the
vault, and actually completed before relying on it.

## Check your result

Pick a page as a reader: can you tell what to do, who maintains it, where its
claims came from, and whether it is current? If not, improve that page before
expanding the wiki.

**Next:** [Request a review and resume work](/tutorials/review-and-resume).