Audit: QRS - Ferrous Lactate for Health & Longevity
Audit conducted on 23/08/2026 09:03 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 83 |
| Failed | 0 |
| N/A | 10 |
| Pass Rate | 100.00% |
- Total = Passed + Failed + N/A
- Pass Rate = Passed / (Passed + Failed) × 100
- N/A items are excluded from the pass rate calculation
1. General Rules
| # | Description | Result | Comments |
|---|---|---|---|
| 1.1 | Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. | 🟢 | All protocol, time-to-effect, benefit, risk, gate, biomarker and qualitative entries trace to ER lines 296–303, 276–294, 140–186, 204–260, 325–345, 377–383 and 409–429. |
| 1.2 | Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing. | 🟢 | No ER section is empty; speculative-tier items remain in the speculative tier. |
| 1.3 | The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”). | 🟢 | Contraindication and interaction wording preserves ER force (e.g. ER “unless directed otherwise by the treating clinician” → “unless a clinician directs otherwise”). |
| 1.4 | The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc. | 🟢 | Gates draw only from ER Key Interactions & Contraindications; tiers draw only from Expected Benefits / Potential Risks & Side Effects. |
| 1.5 | PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. | 🟢 | No PMIDs, NCT identifiers, author names or brand names appear anywhere in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions present. |
2. Focus, Tone & Audience
| # | Description | Result | Comments |
|---|---|---|---|
| 2.1 | The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing. | 🟢 | Matches the ER’s measured, two-edged framing of iron. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Biomarker targets and protocol cells give actionable, non-alarmist framing. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Entries are noun-phrase statements of fact, not orders. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives directed at a patient; clinician deferral is carried verbatim from the ER. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “recommended”, “advised” or “should” constructions in the QRS body. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns in any populated variable. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are confined to biomarker names, where they are required; “reticulocytes” is glossed inline. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every entry is a stripped phrase; ER bullets of 2–3 sentences reduce to single clauses. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by search for you/your across the file. |
| 2.10 | The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. | 🟢 | Functional biomarker ranges and an alternate-day protocol assume a testing-first, proactive reader. |
| 2.11 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | Fasted pre-10 a.m. dosing, multi-hour medication buffers and an 8-marker panel are retained. |
| 2.12 | The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort. | 🟢 | No simplified “take one a day” framing; the demanding schedule is presented intact. |
| 2.13 | Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. | 🟢 | At-A-Glance carries the ER’s key qualifier that benefit exists only where stores are genuinely low. |
| 2.14 | The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. | 🟢 | “Longevity” appears only in the canonical topic; “anti-aging” is absent. |
| 2.15 | The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Body variables use clinical register; the plain wording in At-A-Glance is mandated by item 7.4 and mirrors the ER Conclusion. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” | 🟢 | All fixed strings verified byte-identical to the template at lines 440, 477, 519, 539, 552, 574, 593, 597–599, 701. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variable names present; marker_# and qualitative_item_# rows expanded to 8 each as intended. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Full diff against the template shows changes only inside variable spans. |
4. Formatting
| # | Description | Result | Comments |
|---|---|---|---|
| 4.1 | When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” | N/A | No source ER section relied on by the QRS is empty. |
| 4.2 | Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. | 🟢 | “Standard repletion protocol”, “Best time of day”, “Single versus split dosing” match the ER bold labels at lines 325, 333, 337 verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Biomarker labels match the ER table column 1 verbatim; time-to-effect labels are drawn from the ER’s own terms at line 377. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji characters anywhere in the file; the ER’s ⚠️ Conflicted markers are stripped. |
| 4.5 | The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page. | 🟢 | Every section is condensed relative to the ER; item counts are those the checklist mandates (all biomarkers, all qualitative markers, all ER interaction bullets). |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | Comment opens at line 2, immediately after the doctype at line 1. |
| 5.2 | Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML. | 🟢 | Opening “—” at line 3, closing “—” at line 13. |
| 5.3 | The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. | 🟢 | Enclosed in an HTML comment; no metadata value is repeated in the header or footer. |
| 5.4 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | Only duration: "00:03" is quoted, and it contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: ferrous_lactate_2026-0823-0657_Opus_ER.md. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md version badge. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | Line 6: qrs_creation_date: 2026-0823-0837. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | Line 7: qrs_creator_ai_nickname: Opus. |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | “Opus” is a single word with no version. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | Line 8: qrs_creator_ai_fullname: Opus 5. |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | “Opus 5” is nickname plus version with no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9 matches the file’s actual name on disk. |
| 5.13 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | All nine keys are clean; no stray whitespace or unnecessary quoting. |
6. Page Title & Header
| # | Description | Result | Comments |
|---|---|---|---|
| 6.1 | [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &) |
🟢 | Line 22: “Ferrous Lactate for Health & Longevity - Quick Reference Sheet”. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | Line 417: “Ferrous Lactate for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 08/23/2026, matching qrs_creation_date 2026-0823. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | Header contains only the title and the template subline; the ER’s “Also known as” line is not carried over. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses all four Conclusion paragraphs (ER lines 451–457) into identity, benefit condition, drawbacks and the replete-state verdict. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | Exactly 60 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to ER lines 451, 453, 455 respectively. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; the ER’s “two-plus form” is reduced to “readily absorbed form” and “gastrointestinal” to “stomach upset”. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial references. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numbers of any kind. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All six items map to the ER “Populations who should avoid Ferrous Lactate” list at lines 298–303. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All six ER avoid-list bullets are represented, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Six <li> elements at lines 542–547. |
| 8.4 | Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. | 🟢 | ER rationales “where free iron supports bacterial growth” and “where iron would mask the diagnosis” are stripped; no dash-trailing clauses remain. |
| 8.5 | Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Ferritin 300/200 µg/L thresholds, TSAT >45%, the no-inflammation caveat, “transfusion-dependent” and “flare” staging are all retained. |
| 8.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | N/A | The ER uses no ranking notation in this section. |
| 8.7 | The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision. |
🟢 | The ER names six such populations and the section is correspondingly populated. |
| 8.8 | If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. | N/A | The section is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All ten items map one-to-one to the ER interaction bullets at lines 276–294. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | No overlap with the six contraindication entries. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Ten <li> elements at lines 555–564. |
| 9.4 | Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. | 🟢 | ER mechanistic sentences and the Lactiplantibacillus citation are stripped; no dash-trailing clauses remain. |
| 9.5 | Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Named example drugs and the 2 h / 4 h separation windows are retained; the longer ER drug lists are trimmed to representatives, not dropped. |
| 9.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | N/A | The ER uses no ranking notation in this section. |
| 9.7 | The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used. |
🟢 | The ER names ten such interactions and the section is correspondingly populated. |
| 9.8 | If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. | N/A | The section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | All three cells map to ER Therapeutic Protocol lines 325, 333 and 337. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose and schedule, time of day, and single-versus-split dosing are the three execution-determining bullets. |
| 10.3 | If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. | N/A | The ER supplies twelve protocol bullets, so all three sets are used. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine variables carry substantive ER-derived content; no placeholders remain. |
11. Time to Effect
| # | Description | Result | Comments |
|---|---|---|---|
| 11.1 | The three sets of [time] items cover the three most important time-to-effect aspects from the ER | 🟢 | Haemoglobin, ferritin and fatigue are the three timelines given in ER line 377. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Order matches the ER High-tier benefit order: anaemia correction, store restoration, fatigue. |
| 11.3 | If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. | N/A | The ER supplies three distinct time-to-effect aspects. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine variables carry ER-derived intervals and context. |
| 11.5 | If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel |
N/A | The ER provides time-to-effect information at lines 377 and 383. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All seven entries correspond to the ER benefit subheadings at lines 142–186. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated at lines 521–532. |
| 12.3 | Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. | 🟢 | Entries are the ER subheadings only; all Magnitude lines are dropped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any benefits entry. |
| 12.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | N/A | All four benefit tiers carry items in the ER. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All nine entries correspond to the ER risk subheadings at lines 206–260. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated at lines 576–587. |
| 13.3 | Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. | 🟢 | Entries are the ER subheadings only; odds ratios, hazard ratios and dose thresholds are dropped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any risks entry. |
| 13.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | N/A | All four risk tiers carry items in the ER. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows mirror the ER Monitoring Protocol & Defining Success table at lines 409–418. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All eight ER biomarkers present, with ranges and rationale carried verbatim. |
| 14.3 | [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. |
🟢 | Line 695 condenses ER lines 405–407 into baseline, 4 weeks, 8–12 weeks, 6 months, then 6–12 monthly. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Items mirror the ER “Qualitative markers worth tracking” list at lines 422–429. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All eight ER qualitative markers present and verbatim. |
Issues 23/08/2026 09:03
Pass rate 100.00%. No issues found.
Issues 23/08/2026 08:57
- 2.6 / 2.9 — Imperative verb in Key Interactions: Two [caution_items] instruct the reader in the imperative mood — “Levothyroxine: separate by 4 h” (line 555) and “…bisphosphonates (alendronate, risedronate): separate by 2 h” (line 557) — where the ER states the same facts descriptively (“Separation of at least four hours … is the standard mitigation”, ER line 276).
Fixes 23/08/2026 08:57
- 2.6 / 2.9 — Imperative verb in Key Interactions: Rewrote the two imperative [caution_items] as noun phrases, matching the ER’s descriptive framing: “Levothyroxine: separate by 4 h” became “Levothyroxine: 4 h separation”, and “…bisphosphonates (alendronate, risedronate): separate by 2 h” became “…bisphosphonates (alendronate, risedronate): 2 h separation”.
Issues 23/08/2026 08:45
- 1.3 — Modal dropped from absorption claim: Line 563 asserts “absorption cut by more than half when taken with the dose” while the ER (line 292) says polyphenols and phytate “can cut iron absorption by more than half”, strengthening a conditional into a categorical claim.
- 4.5 — Sheet overflows one A4 page: The Key Interactions gate (lines 554–565) carries ten items averaging three wrapped lines each in a ~337px column; combined with the eight-row Monitoring table and eight-item Qualitative list the sheet renders at roughly 1.9 A4 pages instead of one.
Fixes 23/08/2026 08:45
- 1.3 — Modal restored on absorption claim: The tea/coffee/phytate interaction item was changed from “absorption cut by more than half when taken with the dose” to “can cut absorption by more than half if taken with the dose”, matching the ER’s conditional phrasing.
- 4.5 — Key Interactions condensed: All ten [caution_items] were shortened (drug-class glosses trimmed, example lists reduced to representative drugs, “separation of at least four hours” → “separate by 4 h”), cutting the gate from roughly 27 to about 18 wrapped lines while preserving every time window and threshold.
- 4.5 — Contraindications condensed: Four of the six [stop_items] were tightened (“confirmed or HFE C282Y homozygous” → “or HFE C282Y homozygous”; “in men”/”in women” → parenthetical; “in the absence of inflammation” → “without inflammation”), keeping all threshold values and qualifiers.
- 4.5 — Monitoring cadence and protocol subs shortened: [monitoring_cadence] was reduced to “Baseline, then 4 weeks, 8–12 weeks and 6 months; every 6–12 months after stopping while losses continue”, and [action_1_sub] and [action_2_sub] were trimmed of redundant wording, bringing the sheet within the one-page budget.
Issues 23/08/2026 08:41
- 2.4 / 2.5 / 2.6 / 2.9 — Imperative phrasing in Key Interactions: Items 1 and 3 of [caution_items] (lines 555 and 557) use bare imperatives — “separate by at least four hours” and “separate by at least two hours” — which address the reader and read as clinical instruction, where the ER uses the nominal form “Separation of at least four/two hours” (ER lines 276, 280).
- 2.7 — Unglossed “hepcidin”: [action_3_sub] at line 472 uses “hepcidin” without explanation, while the adjacent Time-to-effect cells gloss their terms (“Reticulocytes (newly made red blood cells)”, line 489).
Fixes 23/08/2026 08:41
- 2.4 / 2.5 / 2.6 / 2.9 — Imperative phrasing in Key Interactions: Changed “separate by at least four hours” to “separation of at least four hours” (line 555) and “separate by at least two hours” to “separation of at least two hours” (line 557), matching the ER’s nominal form.
- 2.7 — Unglossed “hepcidin”: Rewrote [action_3_sub] from “Twice-daily dosing raised hepcidin further without increasing total absorption” to “Twice-daily dosing did not increase total absorption”, removing the unexplained specialist term while keeping the ER-supported conclusion.