Audit: QRS - GlyNAC for Health & Longevity

Audit conducted on 13/09/2026 01:05 using AI4L / Opus 5

Iterations

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. 🟢  
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. 🟢  
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”). 🟢  
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. 🟢  
1.6 The QRS does not introduce new attributions. 🟢  

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

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. 🟢  
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢  

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 section relevant to the QRS is empty; no empty-state phrasing is required.
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. 🟢  
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. 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. 🟢  

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. 🟢  
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]” 🟢  
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢  
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 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]” 🟢  
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]” 🟢  
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] 🟢  
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] is dense, execution-oriented summary of the ER Conclusion section 🟢  
7.2 [at_a_glance] is no longer than 60 words 🟢  
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢  
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢  
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 🟢  
8.2 [stop_items] represent the Contraindications from the ER 🟢  
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). 🟢  
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’s Key Interactions & Contraindications section uses no ranking notation inside parentheses.
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. 🟢  
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 Contraindications section is not empty; it carries eight items.

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 🟢  
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). 🟢  
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’s Key Interactions & Contraindications section uses no ranking notation inside parentheses.
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. 🟢  
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 Key Interactions section is not empty; it carries twelve items.

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 🟢  
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 Therapeutic Protocol section supplies three distinct actionable aspects; 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. 🟢  

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 🟢  
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 The ER supplies three distinct time-to-effect aspects; all three sets are used.
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 The ER does provide time-to-effect information (Practical Considerations, Expected Benefits).

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. 🟢  
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 carry items in the ER Expected Benefits section.

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. N/A All four risk tiers carry items in the ER Potential Risks & Side Effects section.

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 🟢  
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 🟢  

Issues 13/09/2026 01:05

Pass rate 100.00%. No issues found.

Issues 13/09/2026 00:58

  1. 4.5 — Sheet overflows one A4 page: The combined volume of the 12-item Key Interactions gate (lines 601–620), the 11-row Monitoring table (lines 666–819) and the four-line at-a-glance block renders at roughly two A4 pages rather than one.

Fixes 13/09/2026 00:58

  1. 4.5 — Key Interactions example lists trimmed: Shortened the parenthetical example lists in the [caution_items] gate (nitrates, blood-pressure medicines, anticoagulants, antioxidants, blood-pressure-lowering supplements, sedating supplements, hormetic interventions) to the two or three most representative agents, dropping isosorbide mononitrate, hydrochlorothiazide, clopidogrel, astaxanthin, potassium, garlic extract, L-Theanine and hypoxic training. Every qualifier is still present, as 9.5 permits trimming to fit the one-page budget.

  2. 4.5 — Protocol sub-lines condensed: Tightened all three [action_#_sub] cells — “the cysteine given as N-acetylcysteine” → “given as N-acetylcysteine”, “N-acetylcysteine’s roughly 6-hour half-life and the sheer powder volume both argue against a single sitting” → “Roughly 6-hour half-life and the powder volume argue against a single sitting”, and “lets glycine’s sleep-promoting effect land usefully” → “puts glycine’s sleep-promoting effect to use” — so the row renders two lines instead of three.

  3. 4.5 — Time-to-effect sub-lines condensed: Removed wording that merely repeated the adjacent label or value cell: [time_1_sub] no longer restates “Physical function” or “12–24 weeks”, [time_2_sub] no longer restates “Systolic pressure” or “16 weeks”, and [time_3_sub] no longer restates “within two weeks”.

  4. 4.5 — Glutathione target shortened: [marker_9_target] changed from “No established target; change from the individual’s own baseline is what to track” to “No established target; track change from personal baseline”, matching the phrasing already used in the gait-speed and handgrip rows and saving a table line.

Issues 13/09/2026 00:50

  1. 1.3 — Weight-based dose stated as flat: [action_1_value] (line 453) reads “7 g glycine + 9 g N-acetylcysteine daily”, presenting as a universal fixed dose what the ER (line 383) states as “roughly 7 g and 9 g for a 70 kg adult”; both the approximation and the body-weight anchor are lost.

Fixes 13/09/2026 00:50

  1. 1.3 — Weight-based dose stated as flat: [action_1_value] changed from “7 g glycine + 9 g N-acetylcysteine daily” to “Roughly 7 g glycine + 9 g N-acetylcysteine daily (70 kg adult)”, restoring the ER’s approximation and body-weight anchor.

Issues 13/09/2026 00:44

  1. 2.6 / 2.9 — Imperative addresses the reader: [marker_9_target] at line 778 reads “No established target; track change from the individual’s own baseline”; the imperative “track” addresses the reader, where the ER states the same fact non-imperatively at ER line 483 (“change from the individual’s own baseline is what to track instead”).

Fixes 13/09/2026 00:44

  1. 2.6 / 2.9 — Imperative addressed the reader: [marker_9_target] changed from “No established target; track change from the individual’s own baseline” to “No established target; change from the individual’s own baseline is what to track”, restoring the ER’s non-imperative phrasing.

Issues 13/09/2026 00:35

  1. 4.5 — Sheet overflows one A4 page: At the file’s own print rule (A4, 12 mm padding) the content runs to roughly two pages, with the 11-row Monitoring table plus its 3-line cadence paragraph alone taking about 60% of the available height; the At-A-Glance lede, the protocol and time-to-effect subs, the Benefits “Low” item, and the Qualitative list each carry two to four wrapped lines more than the per-section budget allows.

Fixes 13/09/2026 00:35

  1. 4.5 — Protocol cell subs condensed: action_1_sub dropped the redundant “about 100 and 133 mg/kg — giving roughly 7 g and 9 g for a 70 kg adult” (the gram amounts already sit in action_1_value), and action_2_sub dropped “Every protocol divides the day’s amount in two” while restoring the ER’s attribution of the roughly 6-hour half-life to N-acetylcysteine.
  2. 4.5 — Time-to-effect subs condensed: time_1_sub trimmed the trailing “so a fair trial period is three to six months”; time_3_sub replaced “had moved back toward pre-supplement values twelve weeks after withdrawal” with “fade after withdrawal”.
  3. 4.5 — Monitoring rationale cells shortened: marker_3_why from “The endpoint that moved most in metabolic terms” to “The metabolic endpoint that moved most”, marker_6_why from “The inflammation claim is the most contested; this is the validated way to test it personally” to “The most contested claim; the validated way to test it personally”, and marker_9_why from “The mechanism’s proximate output, and the marker an independent trial failed to move” to “The mechanism’s proximate output; an independent trial failed to move it”.
  4. 4.5 — Glutathione target shortened: marker_9_target from “No established target; change from the individual’s own baseline is what to track instead” to “No established target; track change from the individual’s own baseline”.
  5. 4.5 — Cadence line shortened: monitoring_cadence dropped “for as long as use continues”, keeping both repeat schedules intact.
  6. 4.5 — Decision-gate items trimmed: The liver contraindication became “Liver disease: transaminases above twice normal, or cirrhosis Child-Pugh B or C”, and the blood-pressure-lowering supplements interaction dropped the redundant “or dietary nitrate” and “fatty acids” qualifiers.
  7. 4.5 — Qualitative item trimmed: qualitative_item_4 dropped “rather than improvement”, leaving “where blunting is the signal of interest”.

Issues 13/09/2026 00:29

  1. 1.1 — 70 kg qualifier misattached: [action_1_sub] (QRS line 457) reads “about 100 and 133 mg/kg — for a 70 kg adult”, attaching the body-weight qualifier to the weight-normalised mg/kg figures; the ER (line 383) attaches “for a 70 kg adult” only to the absolute “roughly 7 g and 9 g”.
  2. 12.3 — Species qualifier added to benefit: [benefits_speculative] (QRS line 565) reads “extended lifespan in mice” where the ER heading is “Extended Lifespan” (ER line 228), adding a study detail that item 12.3 requires be stripped.

Fixes 13/09/2026 00:29

  1. 1.1 — 70 kg qualifier misattached: Rewrote [action_1_sub] from “about 100 and 133 mg/kg — for a 70 kg adult, the cysteine given as N-acetylcysteine” to “about 100 and 133 mg/kg — giving roughly 7 g and 9 g for a 70 kg adult, the cysteine given as N-acetylcysteine”, matching the ER’s attachment of the body-weight qualifier to the absolute gram figures.
  2. 12.3 — Species qualifier added to benefit: Changed [benefits_speculative] from “extended lifespan in mice” to “extended lifespan”, the ER benefit heading verbatim, stripping the added study detail.