> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/ireveal/upgrade-path.md). # Upgrade path From iReveal to the full platform: the same spine, with the decision layer turned on. No migration, no re-tagging. iReveal is a complete product on its own. It is also, by design, the first half of the platform already running: the identities it resolves, the events it captures, and the outcomes it joins are exactly what the loop runs on. Upgrading is not a migration; it is turning on the rest. ## What carries over Everything. The tag stays the same tag. The immutable IDs stay the same IDs. The traces you have been accumulating become the history the platform learns from, and the consent state and suppression you enforced ride along untouched; see [Consent](/ireveal/consent.md). ## What turns on * **The loop**: goals, KPIs, and targets over the audience iReveal has been building. See [The loop in one page](/getting-started/the-loop.md). * **iHarness and plays**: decisions stop ending at a resolved-account list and start acting, within the gates and approvals you set. See [What iHarness does](/iharness/what-it-does.md). * **Pulse**: the moments that need you, raised instead of buried. ## When to upgrade The honest tell is what you do with iReveal's output. If resolved accounts are being exported to a spreadsheet and worked by hand, the loop is already running, just with people as the decision layer. Plans and what each unlocks are on [Plans](/getting-started/plans.md). --- # 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.aloop.icustomer.ai/ireveal/upgrade-path.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.