> 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/market-pulse.md). # Market Pulse Market Pulse is the Investor Intel home dashboard. It answers one question in a single screen: what is going on in crypto right now, and does any of it touch what you follow? ### What you'll see * **Market regime banner** - a one-line read on the current market environment, so you can frame everything below it. Regime is context, not a forecast. * **Notable movers** - the assets moving hardest right now, with enough context to tell a real move from noise * **Chains you follow** - the current state of the chains you picked in onboarding * **Signal Radar** - explainable signal cards, described below * **Notable news** - the most relevant headlines, each with a short AI analysis of what it could mean for crypto ### Signal Radar cards Every card on the Signal Radar is built to be explainable. Each one shows: * **Signal type** - the kind of move the card describes * **Confidence** - how strong the supporting evidence currently is * **Mention counts** - how many tracked sources are talking about it * **Source diversity** - whether mentions come from many independent sources or a few loud ones * **Why it matters** - a simple explanation of the signal's relevance * **What to watch next** - the concrete thing that would confirm or weaken the signal Signals are classifications of what the data currently shows, not recommendations. A bullish classification means the evidence leans positive right now; it is not a suggestion to buy, and confidence can change as new data arrives. ### Scope filtering Three scope buttons at the top of the page control what everything below them covers: * **Everything** - the whole market * **By chain** - one chain at a time * **Following** - only the chains, assets, and narratives you follow ### How to use it 1. Check the regime banner to frame the session 2. Skim notable movers and the Signal Radar in your chosen scope 3. Expand any signal card and read "why it matters" before reacting to the headline number 4. Take anything that needs a deeper look into [Markets](/thecontentforge-docs/investor-intel/markets.md), [Narrative Radar](/thecontentforge-docs/investor-intel/narrative-radar.md), or [Explain This](/thecontentforge-docs/investor-intel/explain-this.md) ### Tips * Start in **Following** scope for a faster, more relevant read; switch to **Everything** when you want to see what is happening outside your bubble * High mention counts with low source diversity often means one community amplifying itself. Treat that combination with extra care. * "What to watch next" is the most useful line on a card: it tells you what would actually change the picture ### Related * [Narrative Radar](/thecontentforge-docs/investor-intel/narrative-radar.md) - the full lifecycle view behind narrative signals * [Alerts](/thecontentforge-docs/investor-intel/alerts.md) - get notified instead of checking the dashboard * [Daily Brief](/thecontentforge-docs/investor-intel/daily-brief.md) - the same awareness, summarized once a day --- # 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/market-pulse.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.