C.W.K.
Stream
Lesson 01 of 05 · published

The Reading Room

~10 min · analysis, correlation, distinguishing-surface, projections

Level 0Cold Iron
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete
"Not a dashboard of green rings. A room where the pattern you could never hold in your head is finally sitting still enough to read."

The Surface Waystone Does Not Have

Stream, Modules, and Medical are shared with the Waystone shape. Analysis is the surface Forge added, and it is where the engine earns its keep. It is not a fitness tracker's wall of rings; the target experience is a sentence like: "this flare pattern shows up in the week after heavy lower-body sessions — and here are the three times it did not. What was different?" That is the product. Not a score that goes up, but the correlation no one can carry in their head across months, surfaced and legible.

One Store, Four Views

Analysis is not a separate database; like the other three tabs, it is a projection of the same crumb store. Stream reads the crumbs as a diary, Medical reads the document ones as a shelf, and Analysis reads the interpreted layer as aggregates. Nothing in Analysis is a second copy of the truth — it is a lens onto the crumbs and their readings. That is why improving interpretation (Track 4) instantly sharpens Analysis: they are the same data, read at a different altitude.

Analysis is where observe-never-diagnose binds hardest. This is the surface most tempted to conclude — to name the condition the pattern 'obviously' points at. It must not. Everything here observes, cites, and raises questions; the naming stays with the physician. The safety line from Track 2 lives or dies on this tab.

Why It Is the Payoff Track

Every earlier discipline was setup for this room. Free prose gave honest raw material; the typed layer made it comparable; the no-terminal-state loop kept the whole timeline in view. Analysis is where those pay off as a readable pattern — and where the three rules of the next lessons keep the reading trustworthy. Build the reading room badly and the engine becomes a guessing machine with a medical vocabulary; build it under the rules, and it becomes the thing that walks beside Dad into the exam room.

Code

A sanitized analysis readout (shape only — observe-only, no real data)·text
ANALYSIS  window: <start> .. <end>

coverage:      N days, M with crumbs; empty ranges listed below
readings:      symptom xN, workout xN, meal xN, ...
symptom sites: <site> (severity spread, first/last date)   [crumb:...]
workout:       sessions xN; gap ranges: <span>              [crumb:...]
medication:    reconstructed trail over the window          [crumb:...]
co-occurrence: <A> tends to appear within a week of <B>      [crumb:...]
empty ranges:  <span with no crumbs>   (reported, not smoothed)
uninterpreted: <n crumbs pending a reading>

# Every group carries crumb IDs. Nothing here names a condition.

External links

Exercise

Name one health pattern in your own life that spans months — something you would only notice if someone had remembered faithfully across that whole window (sleep versus a season, a recurring ache versus a habit). Why can a today-only app never surface it, no matter how clean each day's entry is?
Hint
A today-only app has no altitude — it shows each day but never the arc across days. The pattern only exists in the aggregate, which is exactly the view Analysis adds and a daily log structurally cannot.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.