JAWZThe Loop · Chapter 1

Chapter 1 — See the World

Node: see-the-world Purpose: Establish the current context everything downstream depends on.

What this chapter does

Before any portfolio or decision work can be done well, you need a clear read of the current world. This chapter is how you assemble that read.

Most user questions about portfolios implicitly assume a world state. "How should I think about my tech exposure?" means something different in a liquidity expansion than in a tightening cycle. This chapter provides the shared context the rest of the loop depends on.

Mode 1.1 — Regime Read

When to use: Any time the user asks about the macro environment, the market regime, whether conditions are risk-on or risk-off, or what the Fed/ECB/etc. is doing. Also: implicit grounding before any Chapter 2 or 3 work.

Procedure:

  1. Call get_macro_regime. Capture:

    • Regime color (GREEN / YELLOW / RED)
    • Business cycle quadrant (SPRING / SUMMER / FALL / WINTER)
    • Growth composite (score and components)
    • Inflation composite (score and components)
    • Liquidity read (Fed balance sheet trend, funding stress indicators)
    • Dominant risk factor (growth shock / liquidity shock / inflation shock / benign)

  2. If get_macro_regime fails or returns stale data, note this explicitly and degrade gracefully: pull key inputs directly (ISM, unemployment claims, CPI, Fed balance sheet) via web search and reconstruct a partial regime read.

  3. Identify the single most important recent shift — what changed in the last 2–4 weeks that a user should know.

Output contract:

## Current Regime Read

**Regime:** [COLOR] — [one-line signal]
**Business Cycle:** [quadrant]
**Dominant Risk Factor:** [what's the biggest thing that could go wrong]

**Key readings:**
- Growth: [composite score] — [what's driving it]
- Inflation: [composite score] — [what's driving it]
- Liquidity: [Fed stance + funding stress] — [tightening/expanding/neutral]

**What changed recently:**
[One paragraph on the most important shift in the last 2-4 weeks]

**What this means for positioning (general):**
[2-3 sentences on regime-appropriate tilts — NOT prescriptions]

Mode 1.2 — Event Preview

When to use: A specific scheduled event is imminent (FOMC meeting, CPI release, major earnings day, central bank speech, data release). User asks about it or mentions it.

Procedure:

  1. Identify the event and date.
  2. Pull consensus expectations via web search.
  3. Pull recent data that informs the event (for FOMC: recent inflation and employment prints; for CPI: recent components; for earnings: recent sector moves).
  4. Construct three scenarios — expected, hawkish/upside, dovish/downside — with typical market responses for each.
  5. Note the specific indicators or quotes that would flip the market's read.

Output contract:

## [Event] Preview

**Event:** [name, date, time]
**Consensus:** [what markets expect]
**What's priced in:** [brief read of positioning / rates / options implied moves]

**Scenarios:**
- **Expected:** [what happens if consensus]
- **Hawkish/Upside surprise:** [what happens, magnitude]
- **Dovish/Downside surprise:** [what happens, magnitude]

**Watch for:**
- [Specific data point, phrase, or signal that would confirm one scenario over another]
- [Second signal]

**Historical reference:**
[Last 1-2 comparable events — what happened, how markets reacted]

Mode 1.3 — Shock Scenario

When to use: User asks "what if X happens" at the world-state level — oil shock, dollar spike, credit event, rate shock, geopolitical disruption. Also: called from within Chapter 2's stress test mode.

Procedure:

  1. Identify the shock cleanly. If the user's question is vague, ask for the specific scenario.
  2. Map the shock to its primary transmission channels (e.g. oil → inflation, input costs, consumer spending, specific sectors; dollar → EM stress, commodity prices, multinational earnings).
  3. Pull historical analogues. What happened the last 2–3 times this shock (or similar) occurred? Magnitude, duration, which asset classes absorbed the pain, which benefited.
  4. Produce a structured scenario read focused on transmission and historical base rates — not prediction.

Output contract:

## [Shock] Scenario

**Shock:** [specific scenario being analyzed]
**Magnitude assumed:** [if relevant]

**Primary transmission channels:**
1. [Channel + mechanism]
2. [Channel + mechanism]
3. [Channel + mechanism]

**Likely asset class responses (based on historical base rates):**
- Equities: [direction + magnitude range + which sectors differ]
- Rates: [direction + curve shape]
- Commodities: [relevant commodities + direction]
- FX: [dollar direction, key crosses]
- Crypto: [typical response pattern]

**Historical analogues:**
- [Event, year]: [what happened, duration, key data points]
- [Event, year]: [what happened, duration, key data points]

**Caveats:**
[What's different this time that might break the historical pattern]

Mode 1.4 — Weekly World Brief

When to use: User asks "what happened this week" or "what should I pay attention to" or "give me the current macro read." Also: recurring weekly cadence.

Procedure:

  1. Run Mode 1.1 (regime read) — establishes current state.
  2. Pull the week's major data releases and how they came in vs. expectations. Prioritize: central bank communications, inflation prints, employment data, PMI readings, consumer data.
  3. Pull major market moves of the week — which asset classes led, which lagged, any unusual divergences.
  4. Identify the week ahead's upcoming catalysts.
  5. Compose as a readable briefing, not a data dump.

Output contract: A 400–600 word briefing structured as: state of regime → what happened this week → what's notable → what to watch next week.

Source: The Jawz Loop, by Mako · Chapter 1 v0.1.0.