> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/context/brand-kit/refresh.md). # Refresh Keep your Brand Kit current with scheduled scans and proposed edits Brand Kit Refresh keeps a Brand Kit current by scanning the sources you choose on a schedule, proposing edits when something changes, and letting you publish or revert each edit from the Brand Kit page. Organizations move quickly. New products launch, audiences shift, positioning gets refined, and competitors pivot. Out-of-date context produces wrong content, like a competitor comparison or product claim that was true months ago and is wrong today. Refresh removes the burden of hand-maintaining that context inside AirOps and lets your sources of truth, wherever they live, drive updates. {% hint style="warning" %} Brand Kit Refresh is available in workspaces with access to Playbooks. If you don't see the Refresh option on your Brand Kit page, contact your account team to confirm Playbooks is enabled. {% endhint %} ## How it works 1. **Enable Refresh on a Brand Kit.** Open the Brand Kit and turn on Refresh. AirOps creates a default playbook that scans public sources for changes. 2. **Add your own sources (optional).** Point Refresh at the places your brand context actually lives. A Notion MCP connector, a documentation site, a GitHub repository, and any source supported by AirOps integrations can be added alongside the public scan. 3. **Choose a frequency.** Pick how often the scan runs. Each run produces proposed edits to the Brand Kit, not direct writes. 4. **Review and act on proposals in the Inbox.** When the scan finds a change, a notification lands in your Inbox. Open the Brand Kit page to publish the proposed edit or revert it. Edits flow through the standard Brand Kit [draft and publish lifecycle](/context/brand-kit.md#versioning-and-history), so nothing changes in production until you approve it. ## What gets proposed Refresh proposes scoped edits to Brand Kit fields when it finds relevant changes in the sources you configured. Each proposal identifies the field that would change so you can review it before publishing. ## Brand Learning Loop AirOps reviews feedback from Playbook chats and Artifact comments and turns reusable guidance into **Suggestions**. A Suggestion can target a Brand Kit or a Playbook, so feedback about writing rules and feedback about the instructions for a specific task reach the appropriate place. Review Suggestions on the Brand Kit page. Each card identifies its target, explains the proposed change, and includes the supporting feedback. Open the evidence to review the original context, then choose **Apply** or **Dismiss**. When you apply a Playbook Suggestion, AirOps checks it against the latest draft. If the change is already covered or no longer relevant, the Suggestion can resolve without an edit. If the draft changes while AirOps prepares the edit, application stops to protect the newer work. Applied changes remain in the draft until you publish the Playbook. ## Enabling and configuring 1. Navigate to the Brand Kit you want to keep fresh. 2. Turn on **Refresh**. AirOps installs the default refresh playbook for the Brand Kit. 3. Open the Refresh configuration panel to: * Add or remove source connectors (for example, a Notion MCP connector pointing at your brand docs). * Set the scan frequency. * Pause or disable refresh at any time. 4. Save your changes. The next scan runs at the configured frequency. ## Reviewing proposed edits When a refresh run produces proposed edits: * A notification appears in your Inbox summarizing what changed. * Open the Brand Kit page to see the proposed edit inline against the current published value. * **Publish** the edit to apply it to the Brand Kit, or **revert** it to keep the current value. * Published edits create a new Brand Kit version with full attribution, the same as any other Brand Kit change. ## Tips * Start with one or two high-signal sources (your product marketing Notion, your pricing page) before adding more. The signal-to-noise ratio of proposals scales with how curated the source list is. * If a proposed edit is wrong, reverting it is one click. Reverts don't disable the source. * Use Refresh for the parts of your Brand Kit that change most often. Foundations like brand voice rarely shift; Product Lines and Audiences move more frequently. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.airops.com/context/brand-kit/refresh.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.