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

# Where context lives

> Brand Kit, content types, Knowledge Base or the task description. A decision table for where a piece of context belongs.

Context lives in several places, and each one has a different lifespan. An instruction typed into a task description applies to that task and stops there.

## Every place context can live has a different lifetime

<Frame caption="Each place has its own lifetime. The Brand Kit is read on every task. A task description is read once.">
  <img src="https://mintcdn.com/writesonic/DNhoXkvgtobPwX9I/images/agents/where-context.webp?fit=max&auto=format&n=DNhoXkvgtobPwX9I&q=85&s=5babc48bfe6a4519664cbce65f27956b" alt="Brand Kit, content types, Knowledge Base and the task description, and what each is for" width="2000" height="1219" data-path="images/agents/where-context.webp" />
</Frame>

Context has a lifetime. The Brand Kit carries company-wide truth into every task, for every agent. Content types carry format rules into work such as blog posts or LinkedIn posts. The Knowledge Base holds source documents, while the task description carries details for this job alone.

Company-wide truth includes who you are, your audience, your voice, and your authors.

The right place depends on **how long the context should keep applying**.

## Each place matches a different lifetime

| Put it in        | When it applies                  | Example                                                            |
| ---------------- | -------------------------------- | ------------------------------------------------------------------ |
| Brand Kit        | Every task, across every agent   | Company identity, audience, voice, and authors                     |
| Content types    | Whenever that format is produced | Blog posts use H2s for main sections                               |
| Knowledge Base   | When source documents are needed | A product brief or customer research                               |
| Task description | This job only                    | Update this page from the attached file without changing its title |

## The Knowledge Base holds documents, not rules

The Knowledge Base holds your own documents so agents can ground their work in them. Use it for source material and facts. Voice, formatting and standing instructions belong in the Brand Kit instead.

## Standing rules belong in the Brand Kit

`Never mention a competitor by name` is a standing company rule, so put it in the Brand Kit. Every agent reads the Brand Kit on every task. If you keep pasting that instruction into task descriptions, its lifetime is wrong. The rule disappears when the task ends, and someone has to remember it next time.

A company-wide rule you repeat per task belongs in the Brand Kit.

## What's next

<CardGroup cols={2}>
  <Card title="Set up your Brand Kit" href="/agents/set-up-brand-kit" icon="palette">
    Work through the six sections.
  </Card>

  <Card title="Writing good tasks" href="/agents/writing-good-tasks" icon="pen">
    Learn what to put in a task description.
  </Card>
</CardGroup>