Audit: QRS - GlyNAC for Health & Longevity

Audit conducted on 19/07/2026 03:47 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 85
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 (100 mg/kg/day, ≈7 g/70 kg, weeks–months), 1:1 ratio, 1.2–3.6 g commercial, twice-daily split, time-to-effect, tiered benefits/risks, monitoring markers and cadence all trace to ER Protocol, Practical Considerations, Expected Benefits, Potential Risks, and Monitoring sections.
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. 🟢 “Generally well tolerated” and “broad longevity promise remains unproven” mirror ER Conclusion (line 448); speculative tiers preserve ER’s speculative framing.
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”). 🟢 Contraindications kept as absolute (active cancer, pregnancy, asthma, bleeding/surgery, clozapine); no strengthening/softening detected.
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 and Key Interactions both drawn from ER Key Interactions & Contraindications; no modifying-factor content miscategorized.
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. 🟢 QRS carries no PMIDs, NCTs, expert names, or brand names.
1.6 The QRS does not introduce new attributions. 🟢 No new 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-weighted tone matches the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert yet accessible; objective framing throughout.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence, not prescriptions.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Content presents the ER’s protocol and monitoring without advising.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Information is presented, not recommended.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No direct reader address in authored content.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language; unavoidable terms are minimal.
2.8 Information is presented in a concise and very compact manner 🟢 Compact cells, tiered lists, condensed monitoring table.
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. 🟢 Framing targets proactive longevity-oriented 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. 🟢 Protocol/monitoring detail assumes an effort-willing reader.
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 general-population framed.
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. 🟢 “Benefit likely depends on how depleted someone is” reflects the deficiency-dependent signal.
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”/”longevity”; no “anti-aging” language.
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. 🟢 Formal terminology; supplement names (fish oil, garlic) mirror ER usage.

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 present verbatim.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All template spans present, including hidden time_3_* spans.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No non-addressed spans altered.

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 ER source section is empty; no empty-state phrasing needed or misused.
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. 🟢 Interaction drug-class labels (Nitrates, Antihypertensives, Anticoagulants/antiplatelets) preserved from ER bold labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Tier and interaction labels retained; no invented labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators in the QRS; ER emoji markers correctly dropped.
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. 🟢 Content condensed to fit a single sheet.

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 spans lines 2–14, immediately 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 — on 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. 🟢 Enclosed in HTML comment; not rendered.
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; duration quoted (contains colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: glynac_2026-0719-0135_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.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-0719-0332.
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) 🟢 Single word: 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]” 🟢 qrs_creator_ai_fullname: Opus 4.8.
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 4.8” — nickname plus version, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: glynac_2026-0719-0135_Opus_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. 🟢 Frontmatter clean and consistent.

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 &) 🟢 Title: “GlyNAC 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., &amp; for &) 🟢 header_topic: “GlyNAC for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0719 → 07/19/2026.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 4.8”.
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 date, AI4L/model attribution; no badges or AKA line.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Distills ER Conclusion (lines 446–448).
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. 🟢 Rebuild glutathione, age-decline, clearest effect, single-group financial conflict, deficiency dependence, tolerability, unproven longevity all trace to Conclusion/Mechanism.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain terms; no acronyms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial citations.
7.6 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 🟢 Items map to ER lines 298–304.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Active cancer/chemo, pregnancy/breastfeeding, severe poorly-controlled asthma, bleeding disorders/within 1–2 weeks of surgery, and clozapine all from ER line 304; nitrates retained as a Key Interaction consistent with ER’s “Caution” designation (line 288).
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Five <li> items.
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. 🟢 No trailing dash-clauses or rationale.
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). 🟢 “within 1–2 weeks of surgery” and “severe, poorly controlled asthma” qualifiers 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. 🟢 No ranking notation present in the ER contraindications; nothing to normalize.
8.7 If no [stop_items] are present the section is left empty N/A Contraindications are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Items map to ER lines 288–302.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Nitrates, antihypertensives, anticoagulants/antiplatelets, NSAIDs, activated charcoal, additive supplements included; chemotherapy and clozapine correctly excluded (covered under Contraindications).
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Six <li> items.
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. 🟢 No trailing dash-clauses; mechanism/mitigation stripped.
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 parentheticals preserved (trimmed of “such as” instances) but never 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 present; lists are plain comma-separated.
9.7 If no [caution_items] are present the section is left empty N/A Key Interactions are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Dose/schedule/ratio map to ER Therapeutic Protocol (lines 326–336).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, Schedule, Ratio are the three 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 Three actionable aspects are present.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three action sets filled with ER-derived content.

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 🟢 ER provides only two distinct time-to-effect aspects (glutathione days–2 weeks; functional/metabolic 12–16 weeks); both are covered.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Glutathione (High) precedes Function & Metabolism.
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. 🟢 Only two aspects exist; third set is empty and set to display:none (line 503).
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Both used sets filled from ER Practical Considerations (line 377).
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 does provide time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Tiers map to ER Expected Benefits (lines 124–200).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 High (glutathione), Medium (oxidative stress), Low (8 items), Speculative (lifespan) all populated correctly.
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. 🟢 Bare tiered facts only.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 “⚠️ Conflicted” markers and magnitudes stripped.
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 sub-sections contain items.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Tiers map to ER Potential Risks (lines 216–270).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 High (GI), Medium (hypotension/potentiation), Low (3 items), Speculative (3 items) populated correctly.
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. 🟢 Bare tiered facts only.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 “(Low Blood Pressure)” and magnitudes stripped.
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 sub-sections contain items.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Markers map to ER Monitoring Protocol table (lines 405–416).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 10 ER biomarkers listed (hs-CRP, fasting glucose, insulin/HOMA-IR, HbA1c, homocysteine, glutathione ratio, blood pressure, CMP, CBC, lipid panel).
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: baseline, recheck 8–12 weeks, then every 6–12 months (ER line 403).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Qualitative markers map to ER Monitoring Protocol (lines 420–424).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 5 qualitative markers listed (energy/fatigue, physical function, cognition, sleep, recovery/resilience).

Issues 19/07/2026 03:47

Pass rate 100.00%. No issues found.

Issues 19/07/2026 03:40

  1. 2.15 — Colloquial “cheap” in own voice: At-a-glance (line 433) uses “two cheap amino acids”; the ER’s own voice consistently uses the more formal “low-cost” / “inexpensive” (ER lines 383, 446, 448), so the QRS should use formal register.

Fixes 19/07/2026 03:40

  1. 2.15 — Colloquial term in At-a-glance: Replaced “two cheap amino acids” with “two inexpensive amino acids” to match the ER’s formal register.