ferritin axis v2: what we know, how to think, what could actually change the model

public decision surface — 2026-04-12

open the thinking dashboard

thesis

the useful question is no longer:

• “is ferritin low?”

the useful question is:

• “what system is generating the ferritin slope, and what evidence would actually separate the hypotheses?”

right now the picture reads like this:

• the ferritin slope is real
• active overload is currently weak
• transport in calm windows looks okay
• CBC still looks okay
• copper handling is still under-measured
• lifestyle / throughput / loss context is still under-modeled

what we already know

• ferritin moved:
• 175 in Mar 2023
• 76.78 in Aug 2025
• 33 in Dec 2025
• calm transport windows did not show obvious loading:
• TSAT ~25% on 2025-08-06
• TSAT 23% on 2025-12-24
• calm inflammatory context looked quiet:
• hsCRP 0.6 mg/L on 2025-08-06
• hsCRP 0.2 mg/L on 2025-12-24
• CBC was still normal in Dec 2025:
• hemoglobin 14.8
• MCV 86
• one copper snapshot exists:
• serum copper 13.2 umol/L
• ceruloplasmin is still missing

what is actually strange

• ferritin fell a lot without a parallel “clear anemia” phenotype
• iron itself did not collapse, but it also did not look abundant in the calm windows
• genetics create prior concern about iron logistics, but the phenotype does not read like classic accumulation
• copper is too incomplete to tell whether the issue is stores alone or iron-copper handling

broad hypothesis surface

1. lower stores drift

current read:

• strongest working hypothesis

what it means:

• stores are genuinely thinner than before
• the system may still be coping
• anemia has not yet declared itself

what would strengthen it:

• ferritin low again on calm repeat
• TSAT normal-to-low
• CBC still okay or beginning to soften later

2. iron-copper handling problem

current read:

• very real because copper closure is still incomplete

what it means:

• ferritin alone may be misleading about what the transport / mobilization system is doing
• copper and ceruloplasmin may explain awkward logistics better than a pure iron-deficiency story

what would strengthen it:

• ceruloplasmin low or low-normal
• repeat serum copper not convincingly robust
• calm repeat still awkward despite no obvious deficiency pattern

3. throughput mismatch

current read:

• plausible

what it means:

• the system may be burning or losing more than it comfortably replenishes
• examples could include training load, caloric restriction, poor recovery, occult loss, or other logistics friction

what would strengthen it:

• ferritin keeps drifting down
• behavior / history reveals donation, bleeding, restrictive eating, intense training blocks, or recurrent inflammation

4. active overload phenotype

current read:

• currently weak

why:

• calm TSAT is normal
• calm ferritin is lower, not higher
• no strong phenotype signal currently points that way

what would reopen it:

• high ferritin in calm context
• high TSAT in calm context
• liver or imaging phenotype leaning that way

what data could actually sharpen the model

data hierarchy

1. calm repeat labs
2. history / behavior / loss context
3. cbc trend over time
4. wearables as throughput context
5. specialty follow-up only if ambiguity survives

highest value

• repeat calm iron bundle:
• ferritin
• serum iron
• transferrin or TIBC
• TSAT
• CBC
• hsCRP
• ceruloplasmin
• serum copper

high value from you

• any blood donation history
• any noticeable blood loss pattern
• iron-containing multis or supplements over the last 2 years
• major diet shifts, calorie restriction, plant-heavy periods, or lower red-meat intake
• GI symptoms, gastritis, reflux meds, or anything that could change absorption

medium-high value

• training load around the ferritin drop
• body-composition cuts
• sustained stress or under-recovery periods
• repeated infections

medium value

• wearable data like whoop

but only if read correctly:

• whoop is not “proof of iron biology”
• it is useful if it helps connect ferritin slope to:
• sleep debt
• recovery debt
• elevated resting load
• periods of overload or recurrent illness

that means whoop matters mostly as throughput context, not as iron diagnosis

how to use whoop if we pull it in

look for windows with:

• sustained recovery suppression
• higher resting HR
• sleep debt
• unusual training strain
• poor rebound after illness

then ask:

• did ferritin drift happen in the same macro-window?
• was the system paying unusually high recovery cost?
• does that fit “stores are being spent” better than “stores are accumulating”?

questions that would genuinely help

• have you donated blood at all in this period?
• any visible or plausible chronic blood loss source?
• were there major diet cuts, fasting phases, or low-red-meat periods?
• any long high-strain training phases?
• did you ever take iron-containing multis or iron supplements?
• any GI issues, reflux meds, gastritis, or bowel weirdness?
• do you remember periods where recovery felt unusually expensive even when sleep was not terrible?

how to think about the next step

do not try to solve this with one more ferritin number.

the right move is:

1. repeat the calm iron-copper bundle
2. pull the high-value history questions
3. only then decide whether to add sTfR, wearables, or GI-oriented follow-up

current verdict

the ferritin story is currently a systems-interpretation problem, not a one-marker problem.

current action order

1. keep the ferritin slope as real.
2. keep overload as non-default.
3. close copper handling.
4. ask the loss / intake / throughput questions.
5. use whoop only as supporting context, not as pseudo-proof.