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

> ## Agent Instructions
> Use the current public BYOM documentation and cite the relevant page. Preserve availability, permission and undo limits.
> The public documentation MCP retrieves guides. Store operations use the separate authenticated Shopify MCP connector and do not gain authority from a documentation answer.
> If a contract, capability or price is not documented, say so. Do not invent endpoints, tools, availability or merchant outcomes.

# Brand Memory

> Use source-backed company context to make work more relevant and consistent.

Brand Memory helps Kina use your product facts, policies and brand guidance without you repeating them in every request. Search the underlying material to check where an answer or draft got its facts.

## Useful context

Brand guidance, product facts, policies and explicit company instructions can make a task more precise. For example, a description draft should use the actual material and care guidance, then follow the brand's tone. A voice instruction cannot make an unsupported product claim true.

Use the sources and search results to check where a fact came from. When a source is outdated or wrong, correct the underlying information or use the supported correction control. Ask Kina to identify conflicting evidence rather than silently choosing a convenient version.

## Source context and explicit memory

Brand Memory helps you inspect what the connected sources say. **Memory** is the separate place to save and govern explicit personal or company facts and instructions. For its scope and review controls, see [Choose what Kina should remember](/product/hq-workspace#choose-what-kina-should-remember).

If a company memory conflicts with a source passage, identify the disagreement and check the authoritative policy. Saving a convenient note should not silently replace a published commitment or create a product claim the source does not support.

## Freshness and limits

A source summary is not a guarantee that every connection has been reread continuously. Check the last-read information and availability of the relevant refresh control. Source access, retention and correction remain governed by your company's permissions and supported capabilities.

## Find the source behind a statement

Open Brand Memory and use **Search** to find what Kina has read. Search for a specific product name, policy phrase or company instruction; use the system filter when you know where the source belongs. Search results describe the source and kind of record so you can distinguish a web page from a conversation or approved change.

Open the result and inspect the passage that supports the fact. Several matching passages from one long record are not several independent sources. If a query returns nothing, that means no matching read was found; it does not prove that the business has no such policy or product.

**Summary** groups context by system. Use it for orientation, then return to the underlying source when a decision depends on an exact number, date, promise or product claim. A summary can compress important qualifications.

## Refresh the appropriate way

The main **Refresh** control reads what has changed when the capability is enabled. The more-options menu also offers **Read everything again**, which starts from the beginning and can take much longer. Choose it for a deliberate complete reread rather than routinely using it to investigate one missing passage.

Check the status line and the individual result when a source is skipped or fails. A refresh request and a completed read are different events. If a control is unavailable, read its reason and inspect the source integration instead of assuming the entire memory is empty.

## Worked example: policy changed, old summary remains

North Coast Goods changes its shipping policy from “dispatch within two working days” to a conditional dispatch promise. Kina's draft still uses the older unconditional phrase.

Search for the phrase and inspect the source and read time. Check the current policy, then refresh the relevant source through the supported control. Ask Kina to redraft using the current policy and to flag the earlier wording. Do not approve a customer promise merely because it appeared in an old summary.

If two current sources disagree, preserve the conflict. An owner's instruction can clarify how work should be handled, but it does not make a public policy page or product specification accurate by itself.

## Correct context without broadening access

When saving a company instruction, specify its scope and wording: “Remember for our company that we describe our tone as plain and practical.” Review the wording and evidence before accepting it as company memory.

Do not use company memory as storage for passwords, full customer records or a personal note intended for one colleague. Before sharing a source, consider who can read the company context and which connected client data classes may expose it. Deleting or correcting context is also distinct from disconnecting the original provider.

Reviewed 2 October 2026.

## Related guides

* [Kina](/product/kina)
* [Improve product content](/guides/improve-product-content)
* [Data and access](/trust/data-and-access)


## Related topics

- [Data and access](/trust/data-and-access.md)
- [Kina](/product/kina.md)
- [Improve product content](/guides/improve-product-content.md)
- [Customer Service](/product/customer-service.md)
- [HQ and Workspace](/product/hq-workspace.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.