> For the complete documentation index, see [llms.txt](https://docs.liquid-pulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquid-pulse.com/readme.md).

# Overview

### Macro Regime Dashboard for the Hashed Liquid Desk

***

LiquidPulse is the live implementation of the Hashed Liquid Outlook framework. It translates a 5-signal macro cascade into a real-time instrument panel — showing regime status, deployment tiers, positioning signals, and a token watchlist.

## What You're Looking At

The dashboard has four pages, each answering a different question:

| Page                                               | Question It Answers                                    |
| -------------------------------------------------- | ------------------------------------------------------ |
| [**Regime Dashboard**](/the-dashboard/regime.md)   | Should we be in the market? What tier are we at?       |
| [**Positioning**](/the-dashboard/positioning.md)   | How aggressive should we be within the active tier?    |
| [**Watchlist**](/the-dashboard/watchlist.md)       | What tokens are we tracking and how do they score?     |
| [**How It Works**](/the-dashboard/how-it-works.md) | How does the framework work? (Interactive walkthrough) |

## Quick Concepts

| Concept                       | What It Means                                                                                                                                                                                           |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Signal Cascade**            | 5 macro signals (P1-P5). The ideal cascade fires P1→P2→P3→P4 in sequence, but v0.25 uses an evidence-anchored cap lookup for each green-gate combo                                                      |
| **Gate Signals**              | P1-P4 determine whether we deploy. P5 only affects BTC/ETH split.                                                                                                                                       |
| **Deployment Tiers**          | Majors (majors only), Majors + Select Alts (+ resilient alts), Majors + All Alts (full deployment) — scope follows gate count, while the exact combo determines the cap and P3+P4 alone remains blocked |
| **Diagnostic Priority Score** | P1=10, P2=5, P3=4, P4=1 (max 20) — explains hierarchy only; P5 is 0-weight                                                                                                                              |
| **ETF Flow Modifier**         | BTC + ETH spot ETF 20-trading-day net flow as % of ETF AUM — modifies the positioning cap, never gate count                                                                                             |
| **Positioning Signals**       | Funding rates, OI, exchange premiums — modulate sizing, never override regime                                                                                                                           |
| **Macro Floor**               | Minimum position when a tier is active, even if positioning says reduce                                                                                                                                 |

## Data Sources

| Signal                 | Source                                                                                                                     | Update Frequency         |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| P1: US M2 (proxy)      | FRED API                                                                                                                   | Cached 24h (weekly data) |
| P2: Stablecoin MCAP    | DefiLlama                                                                                                                  | Cached 1h                |
| P3: DXY                | Yahoo Finance                                                                                                              | Cached 6h                |
| P4: BTC.D              | CoinGecko                                                                                                                  | Cached 1h                |
| P5: ETHBTC             | CoinGecko (derived)                                                                                                        | Cached 1h                |
| Positioning (Funding)  | Coinglass aggregate (canonical) → OKX `BTC-USDT-SWAP` (operational primary, free history) → Hyperliquid / Bybit (fallback) | Cached 1h                |
| Positioning (OI)       | Coinglass aggregate (canonical) → OKX + Bybit + Binance summed (operational primary)                                       | Cached 1h                |
| Positioning (Premiums) | Coinbase, Upbit (vs global index)                                                                                          | Cached 1h                |
| ETF Flow Modifier      | DefiLlama ETF API or SoSoValue ETF API; public Farside/DefiLlama pages as last-resort fallback                             | Daily, T+1               |

The dashboard auto-refreshes every 60 seconds. A **LIVE** badge in the header indicates data is fetched from APIs; **CACHED** means it fell back to a static snapshot.

> **Note on funding source.** The paper (Appendix G.3) specifies **Coinglass aggregate** as the canonical funding source, with OKX / Hyperliquid / Bybit as uncapped-major-venue fallbacks. The dashboard uses **OKX** as the operational primary because Coinglass aggregate funding *history* (needed for the 7d average) sits behind their paid tier — OKX is the highest-quality free, uncapped major venue. **Binance BTCUSDT is excluded** as a primary because Binance has capped BTC perp funding at 0.01%/8h since early 2025, making the framework's TRIM threshold (≥0.05%/8h, \~55% annualized) mathematically unreachable on that venue. Cross-check the live dashboard reading against [Coinglass](https://www.coinglass.com/FundingRate). Full reference: [Data Sources and Calculation Methodology](/appendix/data-sources.md).

## Links

* **Live Dashboard**: [liquid-pulse.com](https://liquid-pulse.com)
* **Documentation**: [docs.liquid-pulse.com](https://docs.liquid-pulse.com)
* **GitHub**: [github.com/n3moxyz/liquidpulse](https://github.com/n3moxyz/liquidpulse)
* **Source Paper**: Hashed Liquid Outlook 2026, Draft v0.25 (Edward Tan)


---

# 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:

```
GET https://docs.liquid-pulse.com/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
