Audit: QRS - Hydrogen Water for Health & Longevity

Audit conducted on 10/09/2026 08:33 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.	🟢	Spot-checked every populated span against the ER: protocol values (ER Therapeutic Protocol), time-to-effect (ER Practical Considerations), benefit/risk tier items (ER headings), all 11 monitoring rows and the cadence (ER Monitoring Protocol & Defining Success), gates (ER Key Interactions & Contraindications), lede (ER 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.	🟢	“No time-of-day comparison has been published” (action_3_sub) and “No established target” (marker_11_target) carry the ER’s hedges 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”).	🟢	Contraindication scope qualifiers (“with magnesium-based tablets”, “specifically for tablet formulations”) are preserved; the lede keeps the ER’s “modest” framing.
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.	🟢	Gates draw only from Key Interactions & Contraindications; risks only from Potential Risks & Side Effects; benefits only from Expected Benefits. No modifying-factor content is repurposed.
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.	🟢	The QRS carries no PMIDs, NCT identifiers, author names or brand names at all.
1.6	The QRS does not introduce new attributions.	🟢	No attributions present beyond the template’s AI4L link.

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 and sceptical throughout, matching the ER’s own register.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Objective and data-anchored; the protocol, monitoring targets and qualitative markers give the reader a self-testable plan.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as what trials did and what markers show, not as instruction.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives or prescriptions; monitoring targets are presented as ranges carried from the ER.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Protocol subs are descriptive (“Trials have used…”, “split dosing dominates practice”).
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms present are unavoidable marker and condition names taken from the ER.
2.8	Information is presented in a concise and very compact manner	🟢	Benefit and risk items are reduced to bare ER headings; gate items are stripped to the key fact.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text search for second-person forms.
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.	🟢	Functional monitoring targets and a formulation-choice framing address exactly this reader.
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.	🟢	Split dosing, pre-exercise timing and an 11-marker panel assume a reader willing to invest 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.	🟢	No general-population simplification; functional rather than conventional lab ranges are used.
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.	🟢	The lede foregrounds the null results and the HDL signal; opportunity cost is carried as an explicit risk item.
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.	🟢	The string “anti-aging” does not occur; the header uses “Health & Longevity”.
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.	🟢	Formulations are named formally (“tablet”, “electrolysis device”); no consumer-grade route or event vocabulary appears.

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 strings match the template byte-for-byte.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variable names are present; the only additions are the legitimate expansions of marker_#_* (11 rows) and qualitative_item_# (6 items).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three website= spans (evidence_review, audit, full_review) are untouched, and lines 15–410 are identical to the template apart from page_title.

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 feeding the QRS is empty.
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.	🟢	“Standard daily dose”, “Single versus split dosing” and “Timing” are the ER’s bold protocol labels verbatim; marker names match the ER Biomarker column verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	The time-to-effect labels condense the ER’s single “Time to effect” bullet, which has no per-aspect ER label to carry; all other labels are verbatim.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji in the file; the ER’s “⚠️ Conflicted” markers were 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.	🟢	Every optional section is condensed to headline facts; the remaining bulk is the mandated full biomarker and qualitative-marker sets required by 14.2 and 15.2.

---

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.	🟢	Lines 2–14, immediately after <!doctype html> on line 1.
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.	🟢	Opening --- on line 3, closing --- on line 13; the descriptive text precedes the opener.
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 an HTML comment; no element repeats the values.
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, and it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: hydrogen_water_2026-0910-0554_Opus_ER.md (line 4).
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, matching 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-0910-0829.
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 with no version.
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.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” — nickname plus version, no context-window or other qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: hydrogen_water_2026-0910-0554_Opus_QRS.html, matching the file on disk.
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.	🟢	Re-verified across all nine keys; no stray whitespace or unnecessary 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., & for &)	🟢	“Hydrogen Water 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., & for &)	🟢	“Hydrogen Water for Health & Longevity” (line 417).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0910-0829 → “09/10/2026” (line 421).
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“Opus 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.	🟢	Header is title plus the template subline only; the ER’s seven alternate names are not carried over.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses all three Conclusion paragraphs: what it is, what moves, what does not, the HDL counter-signal, safety and data thinness.
7.2	[at_a_glance] is no longer than 60 words	🟢	54 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct Conclusion sentence (ER lines 513, 515, 517).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “protective cholesterol” and “blood-sugar handling” stand in for HDL-C and insulin/glycaemic endpoints.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, sample sizes or p-values.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Direction only (“falls slightly”, “dipping”); no numbers.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All three items come from that section’s “Populations who should avoid Hydrogen Water” list (ER lines 355–359).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All three ER avoid-populations are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Three <li> elements inside the span (lines 542–551).
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.	🟢	“because magnesium clearance is inadequate”, “in which added magnesium can worsen neuromuscular weakness”, the myasthenia gravis gloss and the pregnancy rationale are all stripped; no dashes remain.
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).	🟢	The eGFR threshold and CKD stage 4/5 parenthetical is carried intact, as is the tablet-formulation scope on both magnesium items.
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 uses no ranking notation in this section.
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.	🟢	The ER names three avoid-populations and the section is correctly populated, not empty.
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 section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items map one-to-one onto the ER’s seven interaction bullets (ER lines 341–353).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Seven of seven present; no overlap with the three contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Seven <li> elements inside the span (lines 559–574).
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.	🟢	Caution/Monitor labels, mechanisms and all “Mitigation:” clauses are stripped; the ER’s “Other interventions —” dash lead-in is removed for the sauna/cold/fasting item.
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).	🟢	Every named example drug survives, including the vitamin C “above 1 g daily” threshold; the bisphosphonate parenthetical is trimmed to the drug names only.
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 uses no ranking notation in this section.
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.	🟢	The ER names seven interactions and the section is correctly populated, not empty.
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 section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells derive from the ER Therapeutic Protocol bullets (ER lines 383, 391, 395).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, dosing frequency and timing — the three bullets that determine how the intervention is actually taken; the remaining bullets are background or non-actionable (half-life, sex, polymorphisms).
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 supplies well over three actionable aspects and 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.	🟢	All nine spans populated; values (“500 mL – 1 L daily”, “2–3 servings daily”, “30–60 min pre-exercise”) and subs all trace to ER text.

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	🟢	The ER’s Practical Considerations “Time to effect” bullet contains exactly three clauses; all three are carried.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Cell 1 and cell 2 map to High-tier benefits (perceived exertion/lactate; blood lipid profile), cell 3 to Medium and Speculative benefits (functional capacity in over-70s; molecular aging markers).
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 time-to-effect aspects and 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.	🟢	All nine spans populated; the values (“Single serving”, “4–24 weeks”, “6 months”) match the ER’s stated windows.
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 provides time-to-effect information, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Every item is an ER Expected Benefits sub-heading, in ER order.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at the correct tiers: 4 High, 7 Medium, 3 Low, 2 Speculative, matching the ER exactly.
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.	🟢	Headings only, semicolon-separated; all Magnitude figures, conflict-of-interest notes and mechanistic prose left behind.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain in any benefit item.
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 tiers carry items in the ER.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Every item is an ER Potential Risks & Side Effects sub-heading, in ER order.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated: 1 High, 2 Medium, 1 Low, 4 Speculative, matching the ER exactly.
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.	🟢	Headings only; the HDL-C magnitude, the 350 mg upper-intake discussion and the flammability rationale are all omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses remain in any risk item; the ER’s “(HDL-C, the fraction associated with lower cardiovascular risk)” gloss is dropped.
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 tiers carry items in the ER.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows and cadence both come from ER Monitoring Protocol & Defining Success (ER lines 466–480).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 11 ER biomarker rows present in ER order, with names and targets matching.
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.	🟢	Carries the ER’s 8–12 week, 12–24 week and 6–12 month schedule plus the annual magnesium/kidney check for tablet users.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items come from the ER’s “Qualitative markers worth tracking alongside the laboratory work” list (ER lines 484–489).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	Six of six present in ER order.

Issues 10/09/2026 08:33

Pass rate 100.00%. No issues found.