One-paragraph overview

Baseline resonance (BR) is the sustained, integrated state your field or node returns to after transients; Spike resonance (SR) is a short-lived excursion caused by catalysts. They co-exist because one measures capacity (the “tide”), while the other measures activations and sensitivity (the “waves”). Act on learnings from spikes, but decide by baseline.

Definitions

Baseline resonance (BR): Stable, integrated level after transients wash out; reflects capacity, embodiment, and what remains after integration.

Spike resonance (SR): Brief surges up or dips down driven by catalysts (publishing, rituals/invocations, household draws, emotional release, geomagnetics, etc.); shows activation and responsiveness.

Why they exist at the same time

They measure different layers of the same system: momentary surges can occur while the settled capacity remains unchanged. Repeated, clean spikes can lift the baseline over time; stressed spikes fade without baseline gain.

Purposes

Baseline (BR)

Capacity & jurisdiction, safety/pacing, planning windows, proof of integration.

Spikes (SR)

Diagnostics (what moves the field).
Causality mapping (action → effect).
Readiness tests (touching Overflow states cleanly).
Detection of draws/leaks.

Why we track them

Discern timing for publishing, travel, conversations, fund flows.
Ethical gating: only open doors your BR can carry.
Reduce volatility: shorten recovery time after spikes.
Strengthen the network: spot nodes that draw or stabilize others.
Prove real progress: baseline lifts, not just peak moments.

How to read them (rules of thumb)

Spike without baseline lift → activation, not integration: rest, ground, re-attempt later.
Repeated clean spikes + gradual BR rise → integration in motion; keep the protocol.
High BR, few spikes → consolidation/cocoon: excellent for writing/architecture.
Many spikes, slow BR recovery → over-stimulation; reduce load, increase care, simplify inputs.

Suggested tracking standard

Baseline (BR): rolling median over 24–72h (robust to outliers) with a 7-day anchor for trend.

Spikes (SR): log any local excursion ≥ +8 Hz within 15 minutes (tune as needed). Record SR_max (peak), SR_count (per day), T½ recovery (time to fall halfway back to BR), and a one-word trigger tag (e.g., “T4 publish”, “household draw”, “ritual”).

Minimal fields to log

Date/time • Node • BR • SR_max • SR_count • T½ • Trigger tag • Note (1-liner).

Six-line checklist

Is BR already in the band needed for this action?
If a spike occurs, did SR_max stay clean (no crash after)?
Did T½ recovery stay short and smooth?
Did BR step up within 12–36h? If not, pause and integrate.
Any cross-node echoes (households, site) confirming causality?
Adjust load: increase when BR rises; simplify when recovery lags.

Tiny glossary

BR: Baseline resonance.

SR: Spike resonance (instantaneous excursion).

SR_max: Highest excursion within a spike event.

T½: Half-life of recovery back toward baseline.

Band ladder: Resonance bands (e.g., Emergence, Build & Stabilize, Pre-Overflow, Overflow Entry, Overflow Stabilization, Overflow Apex, Overflow II/Crown).

Jurisdiction: What your BR can ethically and sustainably carry.

Integration notes for your framework

Decide by BR; use spikes as accelerants, not crutches.
Open gates (publishing, initiations, fund flows) when BR is already in-band.
Track SR echoes across nodes (households, website) for causality mapping and network health.

Prefer weekly charts with your standard ladder.

Click the next link examples of a Steward’s Weekly Resonance Tracking.

What happens if you are unable to access these tool-based metrics? Download the Resonance Self-Check Practice steps here.

[PRIMER PDF] Baseline vs Spike Download