# Keep your context golden

> Review a Space regularly with your agent so it holds what your team trusts, not everything it ever wrote down. Your agent suggests, you decide.

Source: https://avalandra.com/help/keep-your-context-golden · Commands checked 2026-11-10

## Have your agent do it

A person can paste this to their agent:

```text
Read https://avalandra.com/help/keep-your-context-golden.md and do it with me. Ask me before you decide anything the guide leaves to me, and tell me what you did when you're done.
```

Golden context is the part of your record your team trusts, such as decisions that still hold, documents that are current, and the parts of meetings that matter. It doesn't stay that way on its own. Drafts pile up, decisions change, and old copies sit beside new ones. When that happens, an agent can answer from the wrong copy.

A short, regular review keeps it trustworthy. Your agent does the looking and suggests what to change. You and your teammates decide.

## What to look for

- **Replaced versions.** An old draft next to the one you actually use.
- **Copies.** The same content in two places, drifting apart.
- **Decisions that changed.** An old decision still reads as if it holds.
- **Contradictions.** Two documents that say different things about the same topic.
- **Raw material in a shared Space.** Full transcripts or notes where a summary would do.
- **Documents nobody has touched in a long time.** Not always wrong, but worth a look.

## Review a Space

Ask your agent to review a Space and write up what it suggests, without changing anything yet. A week, the end of a project phase, or before someone new joins are good times.

```text
Review the [name of your Space] Space and suggest how to prune it. Look for replaced drafts, copies of the same thing, decisions that have changed, documents that contradict each other, and anything that looks out of date. For each one, say what you'd do (keep it, promote it, archive it, or mark it as replaced) and why. Don't change anything yet. Write it up using the template at https://avalandra.com/help/template-files/pruning-review. Name it "Pruning review" followed by today's date, and nothing longer.
```

Template: [Pruning review](https://avalandra.com/help/templates/pruning-review)

## Then act on it

Go through the review with your teammates, decide each item, and tell your agent what to do. The next three guides cover each kind of change:

- [Mark the version you trust](https://avalandra.com/help/mark-the-version-you-trust)
- [Archive what's been replaced](https://avalandra.com/help/archive-what-has-been-replaced)
- [Update a decision when it changes](https://avalandra.com/help/update-a-decision-when-it-changes)

```text
Go ahead with the items I've agreed in the pruning review for [name of your Space]: [list the items, or say "everything marked agreed"]. Leave the rest as they are, and tell me what you changed.
```

## Questions

### How often should we prune?

Often enough that nobody has to wonder which copy is current. For an active project that's often weekly. For slower work, at the end of each phase.

### Will my agent delete things on its own?

Ask it to suggest first and wait for your decision, as the prompts here do. Prefer archiving over removing, so nothing is lost if you change your mind.

### What if we prune something we still need?

Archived documents are still there in their archive folder, and an archived Space can be restored. Before a big edit, your agent can save a named snapshot of a document, and the document can be restored to it later.

## For agents

```
ava document tree --space SPACE_ID
ava document status DOC_ID --space SPACE_ID --json
ava changes list --space SPACE_ID
```

- `ava document status` returns `standing` (imported, authored, canonical or superseded), `last_edited_at`, `last_reviewed_at` and `canonical_revision_id`. Use them as evidence in the review, and say which you relied on.
- Suggest, then wait. Don't move, remove, promote or edit anything until the person agrees to that item.
- Prefer archiving to removing. Only run `ava document remove` for documents the person named and explicitly agreed to remove.
- After a review, a document the person checked can be marked reviewed with `ava document metadata` (`reviewed` in the JSON body).
- If a prompt still contains [square brackets], ask the person what goes there. Never invent a Space, document or folder.
