Audit: QRS - MitoQ for Health & Longevity

Audit conducted on 21/10/2026 04:56 using AI4L / Opus 5.5

Iterations

Summary

Items Count
Total 94
Passed 88
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. 🟢 All protocol, time, benefit, risk, gate and monitoring content traces to ER lines 268-453; empty marker targets are stated as “No target given”, matching the ER’s absence of targets.
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. 🟢 “(theoretical)” carried on every ER-theoretical interaction; “No established target” for oxLDL kept verbatim.
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”). 🟢 Severity classes (Monitor/Caution) and avoid-populations match the ER.
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. 🟢  
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 citations or trial IDs; only MitoQ named.
1.6 The QRS does not introduce new attributions. 🟢 “Per the label” (action_2_sub) and “Manufacturer” attributions match ER lines 384, 387, 418.

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 🟢  
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 🟢  
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 🟢  
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms are ER labels/headings carried verbatim (e.g., “P-glycoprotein and BCRP inhibitors”).
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. 🟢 At a Glance notes benefit mainly in older or less fit people with underperforming arteries; baseline-biomarker cell notes little response with normal values.
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 “healthy aging” / “blood vessel 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)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt. 🟢 “blood thinners” is inside the verbatim ER label.

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” 🟢  
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 Span-name diff against template shows only marker_#/qualitative_item_# expanded to numbered rows.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Template diff shows changes only inside variable spans and metadata.

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” 🟢 Only empty ER subsection is Risks High (line 274); it is hidden per 13.5.
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 and interaction labels verbatim (example lists trimmed).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢  
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢  
4.5 The QRS is designed to render on one A4 page: every section is condensed to the shortest form the other checklist items allow, not extended onto a second page. 🟢  

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. 🟢  
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:02” is quoted (contains colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢  
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 26.10.18
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 2026-1021-0416
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢  
5.9 The nickname of the AI is the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT) 🟢 Opus
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢  
5.11 The full name of the AI consists of the model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y) 🟢 Opus 5.5
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢  
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. 🟢  

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., &amp; for &) 🟢  
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢  
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 10/21/2026
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢  
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢  

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 “MitoQ is a dietary supplement … sold for healthy aging.”
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢  
7.3 [at_a_glance] is no longer than 70 words 🟢 70 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢  
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢  
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢  
7.7 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 🟢  
8.2 [stop_items] represent the Contraindications from the ER 🟢 All four ER avoid-populations (lines 360-363) 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. 🟢  
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). 🟢 Transplant time-window qualifier (“no time threshold given”) 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. 🟢 No ranking notation used.
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 populated; ER lists 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 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 8 non-contraindication interactions present; chemotherapy and transplant immunosuppressants covered by Contraindications.
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. 🟢  
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). 🟢 Example drug lists trimmed but retained; “(theoretical)” kept.
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 used.
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 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 Section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢  
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard dose, time of day, baseline biomarkers (ER lines 383-393).
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 provides more than three aspects.
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 🟢 4-6 weeks, within 1 hour, 90 days (ER line 418).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢  
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 provides three aspects.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢  
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 provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢  
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. 🟢 ER headings used.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢  
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 have items.

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. 🟢  
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. 🟢 risks_high is empty with display: none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢  
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 Table markers plus blood pressure, eGFR, AST and lipid panel from ER lines 435-445.
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. 🟢  

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 listed.

Issues 21/10/2026 04:56

Pass rate 100.00%. No issues found.

Issues 21/10/2026 04:52

  1. 2.7 — Unexpanded acronyms in Protocol: The Protocol cell action_3_value (line 469) reads “FMD below 6%” and “PWV above 7.60 m/s” without expanding either acronym; they are first spelled out only in the Monitoring table (lines 599, 610).

Fixes 21/10/2026 04:52

  1. 2.7 — Expanded Protocol acronyms: In action_3_value, replaced “FMD below 6%” and “PWV above 7.60 m/s” with “flow-mediated dilation below 6%” and “pulse wave velocity above 7.60 m/s”.

Issues 21/10/2026 04:51

  1. 14.2 — Companion monitoring biomarkers missing: The ER Monitoring table pairs creatinine with eGFR, ALT with AST and oxLDL with a standard lipid panel (ER lines 443-445), but none of these three measurable markers appears in the QRS Monitoring table (QRS lines 597-662).

Fixes 21/10/2026 04:51

  1. 14.2 — Added companion monitoring biomarkers: Added Monitoring rows for eGFR (paired with creatinine), AST (paired with ALT) and a standard lipid panel (paired with oxLDL), as named in the ER Monitoring table.

Issues 21/10/2026 04:48

  1. 4.3 — Marker labels altered with additions: Monitoring marker names add pairing notes absent from the ER biomarker names: “Oxidized LDL (oxLDL, with standard lipid panel)” (line 632), “Serum creatinine (with eGFR)” (line 643), “Alanine aminotransferase (ALT, with AST)” (line 654).
  2. 4.5 — Optional glosses lengthen table: The same pairing notes at lines 632, 643 and 654 are optional additions that could be dropped without breaking another item, so the Monitoring table is not condensed to its shortest form.

Fixes 21/10/2026 04:48

  1. 4.3 / 4.5 — Marker labels restored verbatim: Removed the added pairing notes from the Monitoring marker names, changing “Oxidized LDL (oxLDL, with standard lipid panel)” to “Oxidized LDL (oxLDL)”, “Serum creatinine (with eGFR)” to “Serum creatinine” and “Alanine aminotransferase (ALT, with AST)” to “Alanine aminotransferase (ALT)”, matching the ER biomarker names.

Issues 21/10/2026 04:44

  1. 9.4 — Trailing explanations in interactions: The caution items at QRS lines 553-560 keep consequence/rationale clauses after the ER action level (e.g., “could raise absorption”, “may blunt training gains”, “markedly reduces absorption”) and a study finding for exercise testing (“lowered peak exercise capacity”, line 560).
  2. 4.5 — Interactions not fully condensed: The same trailing clauses in the Key Interactions gate (lines 553-560) could be stripped without breaking any other item, so the sheet is not at its shortest form.

Fixes 21/10/2026 04:44

  1. 9.4 / 4.5 — Stripped interaction trailing clauses: Removed the consequence/rationale clauses after the action level in all eight Key Interactions items (e.g., “Monitor (theoretical); could raise absorption” to “Monitor (theoretical)”); the exercise item now keeps only the ER’s dose threshold, “Caution (single 80 mg dose)”.

Issues 21/10/2026 04:41

  1. 2.7 — Unexplained FMD/PWV acronyms: The Protocol panel value “FMD below 6% or PWV above 7.60 m/s” (line 469) uses specialist acronyms with no plain-language meaning; they are expanded only later in the Monitoring table.

Fixes 21/10/2026 04:41

  1. 2.7 — Unexplained FMD/PWV acronyms: Changed action_3_value from “FMD below 6% or PWV above 7.60 m/s” to “Impaired artery function (FMD below 6%) or aortic stiffness (PWV above 7.60 m/s)”.

Issues 21/10/2026 04:39

  1. 1.1 — 90-day minimum shown as duration: time_3_sub “Suggested duration of daily use” (line 511) presents the maker’s 90 days as a fixed duration, while the ER says “used for at least 90 days” and “the maker suggests 90 days” as time to effect.
  2. 7.5 — Research jargon in lede: At-A-Glance (line 433) says “Its most consistent human signal”, using “signal” in its research sense, which a non-specialist would not use unprompted.

Fixes 21/10/2026 04:39

  1. 1.1 — 90-day minimum shown as duration: Changed time_3_sub from “Suggested duration of daily use” to “Suggested minimum period of daily use”, matching the ER’s “at least 90 days”.
  2. 7.5 — Research jargon in lede: Replaced “Its most consistent human signal” with “Its most consistent finding in people” in At-A-Glance (now 70 words).

Issues 21/10/2026 04:34

  1. 2.5 — Interaction phrased as instruction: The Key Interactions item “Exercise testing and competition” (QRS line 560) ends with “no high dose (80 mg) before peak efforts”, the ER’s Mitigation wording, which advises rather than presenting the interaction’s effect.

Fixes 21/10/2026 04:34

  1. 2.5 — Interaction phrased as instruction: Changed the “Exercise testing and competition” item from “Caution; no high dose (80 mg) before peak efforts” to “Caution; a high single dose (80 mg) lowered peak exercise capacity”, following the ER Conclusion wording.

Issues 21/10/2026 04:29

  1. 1.3 — Safety claim loses dose qualifier: At a Glance (QRS line 433) states “Short-term safety looks reassuring” without the ER Conclusion’s qualifier “at usual doses”, broadening the safety claim to higher doses that the ER links to stomach upset and lower VO2max.

Fixes 21/10/2026 04:29

  1. 1.3 — Restored dose qualifier: Changed At a Glance “Short-term safety looks reassuring” to “Short-term safety at usual doses looks reassuring”, and shortened “the energy-producing structures inside cells” to “cells’ energy-producing structures” to stay within 70 words (69).

Issues 21/10/2026 04:25

  1. 4.5 — Untrimmed interaction example lists: Key Interactions labels (QRS lines 553–558) keep every ER example, e.g. “(blood thinners; aspirin, clopidogrel, warfarin, apixaban)” and “(vitamin C, vitamin E, N-acetylcysteine)”, although 9.5 allows trimming them, so the sheet is not condensed to its shortest allowed form.

Fixes 21/10/2026 04:25

  1. 4.5 — Trimmed interaction example lists: Shortened the example lists in six Key Interactions labels to two ER examples each, e.g. “(blood thinners; aspirin, clopidogrel, warfarin, apixaban)” to “(blood thinners; aspirin, warfarin)” and “(vitamin C, vitamin E, N-acetylcysteine)” to “(vitamin C, vitamin E)”.

Issues 21/10/2026 04:22

  1. 4.5 / 9.4 — Study detail in interaction: The “Exercise testing and competition” Key Interactions item (QRS line 560) ends with a study-detail clause (“a single 80 mg dose 1 hour before maximal exercise lowered maximal oxygen uptake”) instead of only the key fact, leaving content that could be shorter.

Fixes 21/10/2026 04:22

  1. 4.5 / 9.4 — Study detail removed: Replaced the “Exercise testing and competition” trailing clause “a single 80 mg dose 1 hour before maximal exercise lowered maximal oxygen uptake” with the ER mitigation “no high dose (80 mg) before peak efforts”.

Issues 21/10/2026 04:19

  1. 14.2 — Lipid panel marker missing: The ER Monitoring table pairs oxLDL with a standard lipid panel (ER line 443), but the QRS Monitoring table (lines 631-640) omits it while listing the other paired tests (eGFR, AST, blood pressure).

Fixes 21/10/2026 04:19

  1. 14.2 — Lipid panel marker added: Changed marker_4_name from “Oxidized LDL (oxLDL)” to “Oxidized LDL (oxLDL, with standard lipid panel)”, matching the ER pairing and the existing eGFR/AST pattern.