Audit: QRS - Omaveloxolone for Health & Longevity

Audit conducted on 09/10/2026 14:06 using AI4L / Opus 5.5

Iterations

Summary

Items Count
Total 94
Passed 86
Failed 0
N/A 8
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. 🟢 Lede, protocol cells, time-to-effect cells, tier items, gates, markers, cadence and qualitative items all trace to ER Conclusion, Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks, Key Interactions and Monitoring passages.
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)” kept for St John’s wort, statins, acetaminophen/alcohol, Nrf2 supplements, goldenseal; “(caution)” kept for pregnancy, breastfeeding, kidney impairment; “only nominally significant” and “exploratory” kept in time cells.
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”). 🟢 No ER claim strengthened or softened; “Avoid”, “Monitor”, “Caution” verdicts match ER wording.
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. 🟢 Contraindications come from “Populations who should avoid”; interactions from the interaction bullets; tiers match ER tiers.
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, citations, expert names, NCT IDs or brand names appear.
1.6 The QRS does not introduce new attributions. 🟢 No attributions introduced.

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. 🟢 Measured, evidence-qualified tone mirrors the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert and objective, plainly worded, states benefit and limits without alarmism.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents facts and ER verdicts rather than orders.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No clinical advice beyond ER-derived verdicts; footer disclaimer is template text.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Information is presented; verdict words come verbatim from the ER.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No “you”/”your” anywhere.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Lede and tier items in plain language; technical terms limited to ER labels, thresholds and marker names.
2.8 Information is presented in a concise and very compact manner 🟢 Items stripped to key facts.
2.9 It DOES NOT address the reader directly 🟢 No direct reader address.
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. 🟢 Content (monitoring, interactions, healthy-adult evidence gap) suits risk-aware, proactive adults.
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. 🟢 Presents a demanding protocol (fasting dosing, lab schedule) without dumbing down.
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. 🟢 Not pitched at the general population.
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. 🟢 Lede separates the Friedreich’s ataxia signal from the absence of healthy-adult evidence (line 433).
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. 🟢 No “anti-aging” wording.
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. 🟢 “prescription oral medication” and “orally” used; no lay route terms.

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 headings, gate headings, tier labels and column headers unchanged (lines 440, 477, 519, 539, 554, 578, 597, 601-603, 716).
3.2 All “<span data-qrs-var="NAME">...</span>” from the [qrs_template] are present in the the QRS. 🟢 All 34 template span names present (marker_# and qualitative_item_# expanded to 9 and 6 instances).
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Diff against template shows changes only in addressed spans and the hidden High tiers.

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 ER source section mapped to a QRS section is empty; empty High tiers are governed by 12.5/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. 🟢 Action labels (“Standard regimen”, “Reduced doses”, “Time of day”) and interaction bold labels use ER bold labels, trimmed only in their parenthetical lists.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels are ER labels or ER benefit headings; none invented.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji found in the file.
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. 🟢 Sections condensed: interactions reduced to those changing use with trimmed example lists, tier items reduced to headings, markers to short targets.

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. 🟢 Metadata comment is line 2, directly after doctype.
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. 🟢 YAML delimited by “—” at lines 3 and 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. 🟢 Inside an HTML comment; not surfaced elsewhere.
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. 🟢 Values trimmed; only duration “00:01” is quoted (contains colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: omaveloxolone_2026-1006-0252_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]” 🟢 qrs_prompt_version: 26.10.8 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-1009-1349
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: 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.
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: Opus 5.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.5” = nickname + version.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches the file name.
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. 🟢 Values trimmed; quoting only where required.

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 &) 🟢 “Omaveloxolone for Health & Longevity - Quick Reference Sheet” (line 22).
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Omaveloxolone for Health & Longevity” (line 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 10/09/2026 from 2026-1009-1349 (line 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Opus 5.5 (line 425).
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 template header elements present.

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 🟢 Opens “Omaveloxolone is a prescription oral medication that switches on the body’s own antioxidant and anti-inflammatory defenses” and names its use in Friedreich’s ataxia.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the three Conclusion paragraphs: use, evidence limits, main risks, interactions, healthy-adult verdict.
7.3 [at_a_glance] is no longer than 70 words 🟢 67 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each fact maps to ER Conclusion/Motivation passages (lines 38, 452, 454, 456).
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms or specialist classifications; disease briefly explained.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, sizes or p-values.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 From ER Key Interactions & Contraindications “Populations who should avoid”.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All 8 ER populations listed (lines 542-549).
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each item is an <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. 🟢 Trailing rationales (“given animal developmental toxicity”, “a trial exclusion”) stripped.
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). 🟢 Child-Pugh Class C, (caution), BNP/LVEF thresholds and eGFR threshold preserved.
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 ER uses no ranking notation in this list.
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 populations to avoid.
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. <!-- empty: ER names no population that should avoid the intervention --> 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 🟢 From ER Key Interactions & Contraindications bullets.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 12 use-changing interactions listed; no-change items (digoxin/metformin, QT drugs, cimetidine) omitted; no overlap with contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each item is an <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. 🟢 Mechanistic and dosing tails stripped; only verdicts kept.
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 and “(theoretical)”, “(high doses)”, “(supplement)” qualifiers preserved in trimmed form.
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 ER uses no ranking notation in interaction bullets.
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 use-changing 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. <!-- empty: ER names no interaction that changes how the intervention is used --> N/A Section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells come from ER Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard regimen, reduced doses and empty-stomach timing are the key actionable aspects.
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 at least three actionable aspects.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All label/value/sub spans filled with ER-derived content (lines 444-472).

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 🟢 Neurological decline (months/48 weeks), daily functioning (48 weeks), exercise efficiency (12 weeks) from ER Practical Considerations and Expected Benefits.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered Medium, Medium, Low 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 Three time-to-effect aspects are available.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All time spans filled with ER-derived content (lines 483-511).
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 🟢 From ER Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four benefit spans used.
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. 🟢 Items are ER headings only.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 benefits_high span set to display: none (line 521).

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 From ER Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk spans used.
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. 🟢 Items are ER headings only.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 risks_high span set to display: none (line 580).

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 From ER Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 9 ER table biomarkers listed (lines 607-705).
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. 🟢 Cadence filled from ER Monitoring cadence paragraph (line 710).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 From ER Monitoring qualitative markers.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 6 ER qualitative markers listed verbatim (lines 719-734).

Issues 09/10/2026 14:06

Pass rate 100.00%. No issues found.

Issues 09/10/2026 14:00

  1. 1.2 / 1.3 — Cautious daily-function phrasing dropped: time_2_sub (line 500) reads “Daily-activity scores favored omaveloxolone at 48 weeks (nominally significant)”, dropping the ER’s “numerically favored” and “only nominally significant” (Expected Benefits, Better preserved daily functioning), which strengthens the claim.

Fixes 09/10/2026 14:00

  1. 1.2 / 1.3 — Cautious daily-function phrasing restored: Changed time_2_sub from “Daily-activity scores favored omaveloxolone at 48 weeks (nominally significant)” to “Daily-activity scores numerically favored omaveloxolone at 48 weeks (only nominally significant)”, matching the ER wording.

Issues 09/10/2026 13:57

  1. 11.2 — Time-to-effect not benefit-ranked: time_3 (lines 505-511, “Side effects & liver enzymes”) covers adverse effects rather than a benefit, while the Medium benefit “Better preserved daily functioning in Friedreich’s ataxia” (ER Expected Benefits, 48 weeks) is omitted in favor of the Low exercise benefit.

Fixes 09/10/2026 13:57

  1. 11.2 — Time-to-effect re-ranked by benefit: Replaced the side-effect cell with the Medium benefit “Daily functioning” (48 weeks, nominally significant) as time_2 and moved the Low exercise benefit (12 weeks) to time_3.

Issues 09/10/2026 13:53

  1. 4.5 — Sheet exceeds one A4 page: Key Interactions (lines 557-568, 12 items with long parentheticals, e.g. line 562), the long Cadence text (line 710) and the long action_2_sub (line 461) are not condensed enough, pushing the sheet well beyond one A4 page.

Fixes 09/10/2026 13:53

  1. 4.5 — Condensed overlong sections: Shortened action_2_sub, trimmed the example lists in the strong/moderate CYP3A4 inhibitor, inducer and hormonal contraceptive interaction items (qualifiers kept), and compressed the monitoring cadence text to reduce page length.

Issues 09/10/2026 13:50

  1. 1.2 / 9.5 — Statins theoretical qualifier dropped: The Key Interactions item “Statins (atorvastatin, simvastatin): Monitor” (QRS line 564) omits the ER’s “(theoretical)” qualifier (ER line 318), presenting a theoretical interaction as established.

Fixes 09/10/2026 13:50

  1. 1.2 / 9.5 — Statins theoretical qualifier restored: Changed the Key Interactions item from “Statins (atorvastatin, simvastatin): Monitor” to “… Monitor (theoretical)” to match the ER’s qualifier.