The cascade in the order it actually happens
Immunology is one story told in an alphabet soup of CD numbers and interleukins. Once the story is straight the vocabulary attaches to it; until then the vocabulary is the wall.
Why the mainstream APIs fail here
The story involves pathogens, autoimmune damage and vaccine mechanisms, and hosted models start appending disclaimers exactly when the material gets mechanistic, which is when you needed it plain. Half the confusion in immunology is material the model was willing to say differently.
How MagmaRouter is used for this
Ask for the narrative first: what happens, in order, in one paragraph. Then ask where each named molecule sits in that story. Then ask what goes wrong in the disease on your course list. Three passes, one thread, whole topic.
A working loop
- Narrative before nomenclature, always.
- Attach every CD number and interleukin to the step it acts at.
- Finish with the pathology; the exam question is always what goes wrong.
Prompts are not stored. A signed receipt of the hash comes back on every call, so you can prove later what MagmaRouter logged. Details are on the privacy page. Per-model prices are on /models and the pricing model is on /pricing.