ferritin drift: how to think about it systemically

public decision surface — 2026-04-12

open the visual dashboard

thesis

the current ferritin story does not read like active iron-overload phenotype.

it reads more like:

the main move is not “interpret ferritin harder”.

the main move is:

close the iron-copper bundle cleanly.

what already looks good

what is strange

that means:

what we already checked

checked enough to downgrade overload panic

what those checks already say

current working hypotheses

hypothesis 1: real drift toward lower iron stores

confidence: medium-high

why it fits:

what would support it:

what would weaken it:

hypothesis 2: iron-copper handling issue

confidence: medium

why it fits:

what would support it:

what would weaken it:

hypothesis 3: intake / loss / throughput mismatch

confidence: low-medium

why it fits:

what would support it:

what would weaken it:

hypothesis 4: active overload phenotype from the genetic prior

confidence: low

why it is currently weak:

what would be needed to reopen it:

what will actually close the question

the minimum closure bundle

only if still ambiguous

how to run the repeat

the point is not to “get the best number”.

the point is to get a clean systems read.

how to interpret the next result

scenario A

read:

scenario B

read:

scenario C

read:

scenario D

read:

dashboard logic

the useful dashboard for this axis should always split into four layers:

current verdict

this is currently a lower-stores / logistics / copper-closure problem, not a proven overload problem.

current action order

  1. keep the ferritin drop as a real signal.
  2. do not treat overload as the current default explanation.
  3. repeat the calm iron bundle with ceruloplasmin + serum copper.
  4. add sTfR only if the calmer repeat still leaves ambiguity.