Audit: QRS - Iron for Health & Longevity of the ER frontmatter
Audit conducted on 25/08/2026 09:54 using AI4L / Grok 4
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 87 |
| Failed | 0 |
| N/A | 6 |
| 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. | 🟢 | Protocol doses, benefit/risk headings, stop/caution lists, monitoring table, qualitative markers, and at-a-glance claims all map to ER Protocol, Expected Benefits, Potential Risks, Key Interactions & Contraindications, Monitoring, and Conclusion. |
| 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. | 🟢 | QRS keeps hedges from the source: “can quiet”, “is tied to”, “has not shown a longevity gain”; speculative 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”). | 🟢 | Heart-failure wording stays “tied to fewer hospitalizations”; empty-store vs full-store split matches the Conclusion. Conflicted flags are omitted only because Benefits/Risks items must not carry qualifiers (12.3/13.3). |
| 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. | 🟢 | Stop items come from “Populations who should avoid Iron”; caution items from the interaction bullets; benefits/risks stay in their ER sections. |
| 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 IDs, expert names, or brand names appear in the QRS body. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions added. |
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. | 🟢 | |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Frames repletion when stores are empty and withholds extra iron when they are full. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Footer states not medical advice; body presents ER facts. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person address. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | At-a-glance uses “blood oxygen-carrying protein”; remaining lab and genotype terms are ER labels required as decision-gate or monitoring content. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | |
| 2.9 | It DOES NOT address the reader directly | 🟢 | |
| 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. | 🟢 | |
| 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. | 🟢 | |
| 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. | 🟢 | |
| 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. | 🟢 | Leads with “not a longevity supplement” and no gain from extra iron when stores are already full. |
| 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. | 🟢 | Uses “longevity”; no “anti-aging”. |
| 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. | 🟢 | Uses “oral iron” / “intravenous iron”; ER phrases such as “can sit with the dose” are carried from the source. |
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 listed headings, gate titles, tier labels, and column headers match. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All QRS.md-named variables are present (page/header/at-a-glance, three action sets, three time sets, benefit and risk tiers, stop/caution, six markers, cadence, five qualitative items). |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Website spans (evidence_review, audit, full_review) remain as template hooks. |
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” | 🟢 | No mapped ER section is empty. The empty Low-risks tier is handled under 13.5 (display:none), not with empty-state phrasing. |
| 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. | 🟢 | Protocol labels “Standard repletion (hematology/primary care)”, “Time of day”, and “Baseline biomarkers” match the ER bold labels. Monitoring marker names match the ER table. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Used protocol and marker labels are verbatim ER labels. Time-to-effect cell names use ER terms (Hemoglobin, Restless legs, Fatigue) because the ER presents those timings in prose rather than as Label: bullets. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | ER ⚠️ Conflicted and traffic-light emoji are not carried into the QRS. |
| 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. | 🟢 | Benefits/risks are heading-only; interaction consequence clauses are stripped; sheet CSS includes A4 print rules. |
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. | 🟢 | |
| 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. | 🟢 | |
| 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. | 🟢 | HTML comment only. |
| 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. | 🟢 | duration: "00:08" is quoted because the value contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: iron_2026-0825-0642_Grok_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]” | 🟢 | qrs_prompt_version: 26.7.02 matches QRS.md. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | qrs_creation_date: 2026-0825-0922 |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | qrs_creator_ai_nickname: Grok |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | qrs_creator_ai_fullname: Grok 4 |
| 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) | 🟢 | |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: iron_2026-0825-0642_Grok_QRS.html |
| 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. | 🟢 | Same as 5.4. |
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 &) |
🟢 | Iron 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 &) |
🟢 | Iron for Health & Longevity |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 08/25/2026 from 2026-0825-0922 |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Grok 4 |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | Only the template subline (date, Evidence Review, AI4L, model). |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Distills the Conclusion’s one-way-door framing, repletion-when-empty gains, and no longevity gain when stores are full. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 57 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Maps to Conclusion lines on not a longevity supplement; take-in/throw-out; oxygen-carrying protein, fatigue, restless legs; IV iron in iron-poor heart failure and hospitalizations; no longevity gain with full stores. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Uses “blood oxygen-carrying protein”, “stores”, “intravenous”; no TSAT/ferritin/CRP/hepcidin. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | From “Populations who should avoid Iron”. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All six avoid-populations are present. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | |
| 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. | 🟢 | Inner definitional asides on thalassemia and sideroblastic anemia are dropped; no trailing dash clauses. |
| 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). | 🟢 | HFE/TSAT ≥45%/ferritin thresholds, secondary-overload examples, “especially for intravenous iron”, and “that product only” are kept. |
| 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. | 🟢 | ER stop list does not use ranking symbols of this kind. |
| 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. |
🟢 | Section is populated; ER names avoid-populations. |
| 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 | Stop section is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All seven ER interaction bullets; none duplicated as stop items. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | |
| 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. | 🟢 | Consequence/mechanism sentences stripped; time windows and distinctive parentheticals retained. |
| 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). | 🟢 | Drug examples, 4-hour and 2/3-hour windows, ≥2 hours, 45 mg/day UL, (potentiating), and (monitor) are kept. Redundant “(caution)” on the caution gate is 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. | 🟢 | No “>” ranking notation in the ER interaction list. |
| 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. |
🟢 | Section is populated; ER names interactions. |
| 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 | Caution section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | From Therapeutic Protocol bullets on standard repletion, time of day, and baseline biomarkers. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | 40–100 mg elemental iron (daily or alternate-day), morning timing with absorption constraints, and ferritin/TSAT/hemoglobin/CRP. Alternate-day dosing is in action_1_sub. |
| 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 | ER Protocol lists more than three actionable aspects; all three action 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. |
🟢 |
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 | 🟢 | Hemoglobin, restless legs, and fatigue are the timed outcomes with named benefits; reticulocyte rise is an early lab surrogate of the same hemoglobin benefit. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Hemoglobin (High), restless legs (High), fatigue (Medium). |
| 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 | ER states at least three time-to-effect aspects; all three time sets are used. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | Values from Practical Considerations; subs from that paragraph plus the matching benefit headings. |
| 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 | ER Practical Considerations includes a Time to effect paragraph. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All eight ER benefit headings are present in their ER tiers. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | |
| 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. | 🟢 | Heading-only items; ⚠️ Conflicted stripped from the heart-failure line. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | Magnitude paragraphs are not carried. |
| 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 | High, medium, low, and speculative benefit items are all present. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | |
| 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. | 🟢 | Heading-only; “(low blood phosphate)” and ⚠️ Conflicted stripped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | |
| 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. | 🟢 | ER Low risks subsection is empty; [risks_low] has style="display:none" and is not filled with empty-state phrasing. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | From Monitoring Protocol & Defining Success. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | Ferritin, TSAT, hemoglobin, serum iron + TIBC, CRP, and phosphate (after FCM) match the ER table. |
| 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. |
🟢 | Baseline; 6–8 weeks; 3–6 months after refill; 6–12 months if ongoing risk; delayed ferritin after IV iron; phosphate 2–6 weeks after ferric carboxymaltose. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All five ER qualitative markers are listed verbatim. |
Issues 25/08/2026 09:54
Pass rate 100.00%. No issues found.
Issues 25/08/2026 09:36
- 9.5 — ACE monitor qualifier dropped: The ER ACE-inhibitors bullet is tagged
(monitor)as a severity/handling class. QRS Key Interactions listsACE inhibitors (lisinopril, enalapril)and drops(monitor)entirely (QRS line 561).
Fixes 25/08/2026 09:36
- 9.5 — ACE monitor qualifier: Restored the ER
(monitor)severity class on the ACE inhibitors Key Interaction item (ACE inhibitors (lisinopril, enalapril)→ACE inhibitors (lisinopril, enalapril) (monitor)).
Issues 25/08/2026 09:26
- 2.3 / 2.4 / 2.5 / 2.6 / 2.9 — Imperative protocol subline:
action_3_sub(line 472) reads “Decide whether to treat, the route, and when to stop,” a second-person instruction. The ER states that ferritin, TSAT, hemoglobin, and CRP decide those questions; the QRS should present that fact, not tell the reader to decide.
Fixes 25/08/2026 09:26
- 2.3 / 2.4 / 2.5 / 2.6 / 2.9 — Imperative protocol subline: Replaced
action_3_subfrom “Decide whether to treat, the route, and when to stop” to “These markers decide whether to treat, the route, and when to stop,” matching the ER’s descriptive subject (the labs) instead of instructing the reader.