> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summation.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Refine your business context
> Add definitions and corrections from your analysis so future work reflects how your business operates.
Step 3 of 4. Save useful context from your first analysis for future work.
You don't need business rules set up before your first analysis. Start with a question, then correct [Addison](/features/addison) as you review the answer, and save what's worth reusing.
## Start with one useful correction
Look at the analysis you just created. Does it match how your team actually defines things? If not, tell Addison in the same conversation:
> Use net revenue after refunds, and exclude test accounts. Update the analysis with those rules.
If it's worth keeping, ask Addison to save it as a guide or metric (see [Save what you'll use again](#save-what-you’ll-use-again) below).
## Guides and metrics: the two ways to save context
[Knowledge](/features/knowledge) holds two types of saved context:
* **A guide** is written context in Markdown: a definition, a convention, or background on how your business works. Use it for anything you'd otherwise re-explain in chat, like "revenue excludes test accounts" or "Q4 planning assumes 3% churn."
* **A metric** is one number, defined once with its calculation attached, like gross margin or average order value. Compute it once and it stays consistent everywhere: in a chat answer, on a [dashboard](/features/artifacts/dashboards), in a scheduled [report](/features/artifacts/reports).
Most corrections are guides, a rule rather than a formula. Use a metric when you want a number computed the same way every time.
## Save what you'll use again
Save it once and let Addison do the writing. Open a project's **Knowledge** page, from the buttons at its top-right (or the organization-wide **Knowledge** page, from the left nav), and choose **Add → Create with Addison**. Describe the rule instead of writing it out. For a metric, Addison also finds the backing table, writes the calculation, and validates it against real data. Either way, you're reviewing a draft, not filling in a blank page.
Prefer to write it yourself? **Create Manually** opens a blank guide page, or a metric panel asking for the table and the definition. For a guide, put the rule in the first sentence, since Addison only sees a short excerpt.
Keep the scope clear. Is this a rule for your whole business, or just this project? Excluding test accounts might belong globally; a one-off planning assumption might belong to a single project. A project-scoped guide or metric can be published to the global library later, once an admin approves it.
Start with a few sentences and add more as real questions reveal what's missing.
## Build on what your team already knows
Already have a glossary, metric spec, or analyst handoff? Add it to your project's [Files](/features/projects#files) and ask Addison to turn it into guides and metrics. Addison checks each proposed asset against what already exists, so you don't create duplicates.
For more on scoping and publishing, see [Knowledge](/features/knowledge). Use the [data catalog](/features/tables#catalog) to document what tables and columns mean.
## Next: automate the work
If your analysis was a one-time task, you can stop here. If you want to repeat it, turn the reviewed work into a [workflow](/features/workflows).
Step 4: test a playbook, then choose when it runs and where to send the results.