> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/investor-intel/narrative-radar.md). # Narrative Radar Narratives move crypto: AI season, RWA, restaking, a new chain getting hot. Narrative Radar detects these themes automatically, tracks where each one is in its lifecycle, and checks whether the talk is backed by anything on-chain. The goal is to help you see narratives early and judge them honestly, not to chase them. ### Automatic detection Narratives are discovered automatically from market chatter and activity. You do not have to define them up front; the radar finds emerging themes and starts tracking them, and you can add your own on top. ### Lifecycle statuses Every narrative carries a lifecycle status so you know where in the curve you are looking: * **Early** - newly detected, low attention so far * **Heating Up** - attention and activity accelerating * **Crowded** - widely discussed; late-arriving attention, often elevated risk * **Cooling** - attention fading * **Dormant** - inactive, kept for history and possible revival ### Signal classification Each narrative is classified as **bullish, bearish, or mixed** based on what the underlying signals show. This is classification, not advice: a bullish narrative is one where current evidence leans positive, and a Crowded bullish narrative can still be a poor entry. The classification tells you what the data says; what to do about it is your decision. ### Scores Three scores quantify each narrative: * **Momentum** - how fast attention is growing or shrinking * **Chatter** - how much discussion there is right now * **Breadth** - how many distinct assets, sources, and communities the narrative spans ### On-chain confirmation Talk is cheap. Each narrative carries an on-chain confirmation score that checks chatter against actual on-chain and market activity. High chatter with low confirmation is labelled clearly: that combination is often hype, and the radar will say so rather than dress it up. ### Following and alerts * **Follow** any narrative to pull it into your "Following" scope on [Market Pulse](/thecontentforge-docs/investor-intel/market-pulse.md) and your [Daily Brief](/thecontentforge-docs/investor-intel/daily-brief.md) * **Narrative alerts** notify you when a followed narrative heats up, via the narrative heat trigger in [Alerts](/thecontentforge-docs/investor-intel/alerts.md) * The number of narratives you can follow depends on your plan. See [Pricing](/thecontentforge-docs/reference/pricing.md). ### AI briefs Every narrative has an AI brief: what the narrative is, what is driving it, which assets are involved, what the on-chain picture shows, and what would confirm or weaken it. Briefs are written to be explainable and cite the signals behind them. ### Custom narratives Track a theme the radar has not surfaced yet by creating a custom narrative. It gets the same lifecycle tracking, scores, and briefs as auto-detected ones. ### Filters Filter the radar by **chain** and by **category** to focus on the ecosystems and themes you care about. ### How to use it 1. Scan Early and Heating Up narratives in your chains a few times a week 2. Check the on-chain confirmation score before taking any narrative seriously 3. Follow the ones that matter to you and set a narrative heat alert 4. Read the AI brief before forming a view; check "what would weaken this" as carefully as the bull case ### Related * [Market Pulse](/thecontentforge-docs/investor-intel/market-pulse.md) - narrative signals surface on the Signal Radar * [Thesis Journal](/thecontentforge-docs/investor-intel/thesis-journal.md) - turn a narrative view into a written thesis you can review later * [Alerts](/thecontentforge-docs/investor-intel/alerts.md) - the narrative heat trigger --- # 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://thecontentforge.gitbook.io/thecontentforge-docs/investor-intel/narrative-radar.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.