Methodology

How LiquidityPulse turns macro context into a readable product layer

LiquidityPulse combines liquidity, growth, and stress inputs into a smaller set of readable signals. The goal is not more raw data, but a clearer working model for regime interpretation.

Framework

Three building blocks shape the interpretation layer

LiquidityPulse does not treat every series as equally important. Instead, it groups signals into a smaller number of macro building blocks that are easier to interpret together.

Liquidity

Fed balance sheet, money supply, and funding-related factors are merged into a clearer liquidity picture instead of remaining isolated data points.

Growth

Industrial Pulse and the yield curve help indicate whether the backdrop looks supportive, cooling, or more fragile.

Stress and regime

Credit, the dollar, and other drivers are condensed into a regime view that names the current market phase more directly.

Signals

What the product is actually trying to produce

The product aims to create a readable signal surface, not an academic macro database. That means each layer should help answer a concrete interpretation question.

01

Measure the backdrop

Liquidity, growth, and stress inputs establish the broad macro environment.

02

Compress the drivers

The strongest inputs are surfaced as the top forces shaping the current picture.

03

Name the regime

The system turns those signals into a more supportive, mixed, or restrictive regime read.

Data Inputs

Examples of the underlying inputs

LiquidityPulse is built on public macro and market data, but the value comes from how these inputs are arranged into a more readable surface.

Liquidity and funding

Fed balance sheet, M2, Reverse Repo, Treasury General Account, and related funding conditions.

Rates and macro

Yield curve, SOFR, and broader macro series that help frame growth and tightening conditions.

Risk and market context

Credit spreads, the dollar, and assets such as Bitcoin to connect macro backdrop with risk appetite.

Chart Guide

How to read the main charts on the site

The website uses a small set of charts repeatedly. Each one is there for a reason and should answer a specific interpretation question.

Composite

Liquidity Index

What it shows
A custom net-liquidity measure built from M2 plus the Fed balance sheet minus reverse repo minus the Treasury General Account.
Why it matters
It brings several core liquidity levers into one readable line and makes shifts in conditions easier to spot.
How to read it
A rising line is usually more supportive for risk assets, while a falling line points to tighter conditions.

Composite

Industrial Pulse

What it shows
A worker composite built from monthly harmonized copper and WTI oil.
Why it matters
It condenses two cyclical commodity signals into a more stable proxy for industrial activity and demand.
How to read it
A rising trend points to stronger real activity, while a falling trend suggests softer industrial momentum.

Derived

Yield Curve 10Y-2Y

What it shows
A derived spread calculated as the US 10-year yield minus the 2-year yield.
Why it matters
It is a classic stress and business-cycle indicator.
How to read it
An inverted or flat curve is usually more defensive than a clearly positive curve.
Key threshold
Zero is the key threshold: below it, the curve is inverted.

Market proxy

Bitcoin

What it shows
A globally traded proxy for risk appetite and market momentum.
Why it matters
It often reacts quickly to liquidity, sentiment, and positioning.
How to read it
A stable uptrend is usually constructive, while sharp weakness is more defensive.

Public paths

How the public pages work together

The homepage shows the current state: regime, drivers, and the key charts.

This methodology page explains how to read those signals. The iPhone app is the more focused path if you want the product in a more compact, native format.

Interpretation Notes

The methodology is designed to support judgment, not replace it

LiquidityPulse is not investment advice. Regimes, lead-lag views, and signal layers are tools for context and interpretation.

Historical relationships can be useful, but they are not guaranteed to persist, and correlation is not proof of causation.

Next Step

Explore the live product layer or the iPhone app

The methodology explains the structure. The live site and iPhone app show how it is experienced in product form.