Body Signals vs Baseline — boundaries that keep data clean

Baseline and Body Signals are adjacent on purpose—and not interchangeable.

Why this matters

If you characterize every complaint at full depth on day one, you drown in detail before you know the frame. If you never deepen beyond a checkbox, you lose the distinctions that change upstream guesses. The split is how Re:Formd keeps signal graded instead of binary.

How it works in the model

• Baseline is intentionally lightweight: enough context to situate the person—sleep pattern, load, stress band, major anchors—without forcing full signal taxonomy up front.
• Body Signals is where duration, severity, frequency, and situational triggers become legible—because those attributes change what is plausible upstream versus downstream.

Entities (what you take) and pathways (repair order) consume both layers. Mix Baseline into Body Signals—or the reverse—and you export ambiguity into everything below.

What people get wrong

Reframe: The split is not bureaucracy; it is gain staging. You set context first, then turn up resolution where it earns its cost. “Everything is urgent” is what happens when those stages bleed together.

What’s next

Strict capture order is how the product stays honest about what it knows. Join the waitlist to get access when Re:Formd opens.