Audit: QRS - St. John’s Wort for Health & Longevity

Audit conducted on 27/09/2026 09:39 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.	🟢	All QRS statements trace to ER text (Conclusion, Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks, Key Interactions & Contraindications, Monitoring Protocol).
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.	🟢	Cautious wording preserved (e.g., “about 500 mg/day”); empty ER risk tiers are hidden rather than rephrased.
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 labels (avoid or monitor closely, avoid combining, caution, monitor) match ER; contraindications mirror ER “Populations who should avoid”.
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 ER avoid-list/absolute contraindications; interactions from ER interaction bullets; no modifying factor relabeled.
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.	🟢	Only ER-present brand/extract names (Ze 117) and scales (PHQ-9) 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.	🟢
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	🟢	Directive words (“avoid combining”, “caution”) are ER severity labels.
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	🟢	No second-person address.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms limited to decision-relevant drug classes/biomarkers named in the ER.
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 closes on the medication-load trade-off central to 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.	🟢	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.	🟢	Lay glosses (“blood thinners”, “stomach-acid reducers”) appear only inside ER-verbatim labels following the formal class name.

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 match the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template spans present; marker_# and qualitative_item_# expanded to 1-6 and 1-7.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff against template shows changes only inside variable spans and metadata values.

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”	🟢	ER Medium and Speculative risk tiers are empty; QRS hides them per 13.5 without introducing any non-ER empty-state wording.
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 labels and interaction labels use ER bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time labels use ER wording (“Mood effects”, “persistent unexplained physical symptoms” from ER Conclusion, hot-flash).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji.
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.	🟢	Each section condensed to label + severity/key fact; ER context columns and rationale dropped.

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 html>.
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 is quoted (“00:02”), which contains a 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.9.25 matches QRS.md version.
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	2026-0927-0912
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., & for &)	🟢	St. John’s Wort 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., & for &)	🟢
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/27/2026
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Opus 5.5
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	🟢	Opens “St. John’s wort, a yellow-flowering plant whose standardized extracts are sold for low mood”.
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 (script count).
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 nine ER avoid-populations 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).	🟢	PHQ-9 threshold and two-week windows 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.
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 names 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 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 non-contraindication ER interactions present (14); surgery and absolute-contraindication drug classes excluded as already in 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 parentheticals preserved, trimmed where duplicative.
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.
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 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 regimen, low-hyperforin regimen, time of day.
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 aspects available.
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	🟢	Mood, somatoform symptoms, hot flashes.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Two High-tier benefits first, then Medium-tier hot flashes.
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 aspects available.
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.	🟢
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_medium and risks_speculative set to 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	🟢	All six ER biomarkers 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	🟢	All seven ER qualitative markers listed.

Issues 27/09/2026 09:39

Pass rate 100.00%. No issues found.

Issues 27/09/2026 09:36

1. 2.15 — Colloquial term in lede: At a Glance (line 433) uses the consumer-grade “blood-thinning … medications” instead of the formal wording; the ER Conclusion uses “clot-preventing medications”.

Fixes 27/09/2026 09:36

1. 2.15 — Colloquial term in lede: Replaced “blood-thinning” with “clot-preventing” in At a Glance, matching the ER Conclusion wording; word count stays at 70.

Issues 27/09/2026 09:31

1. 2.7 — Unnecessary jargon on sheet: “Somatoform symptoms” in benefits_high (line 522) and time_2_label (line 494), and “Detects enzyme induction” in marker_6_why (line 673), use specialist terms where the ER provides plain equivalents (“persistent unexplained physical symptoms”; making the body clear medications faster).

Fixes 27/09/2026 09:31

1. 2.7 — Unnecessary jargon replaced: Changed “somatoform symptoms” to “persistent unexplained physical symptoms” in benefits_high and time_2_label to “Unexplained physical symptoms”; changed marker_6_why from “Detects enzyme induction” to “Detects faster drug clearance”.

Issues 27/09/2026 09:27

1. 2.15 — Consumer-grade phrasing in lede: The at-a-glance (line 433) says the herb “can cause dangerous reactions” with other antidepressants, a lay “bad reaction” register rather than formal terminology such as “serious adverse reactions”.

Fixes 27/09/2026 09:27

1. 2.15 — Consumer-grade phrasing in lede: Changed the at-a-glance clause “combined with other antidepressants it can cause dangerous reactions” to “with other antidepressants it can cause serious adverse reactions”, keeping the lede at 70 words.

Issues 27/09/2026 09:24

1. 9.2 — Key Interaction duplicates Contraindication: The caution item “Light-based procedures (laser resurfacing, photodynamic therapy, ultraviolet phototherapy, bright-light therapy): caution” (line 570) repeats laser and photodynamic treatment, which are already listed as a Contraindication at line 549.

Fixes 27/09/2026 09:24

1. 9.2 — Removed duplicated light procedures: Trimmed the Key Interactions item from “Light-based procedures (laser resurfacing, photodynamic therapy, ultraviolet phototherapy, bright-light therapy)” to “Light-based procedures (ultraviolet phototherapy, bright-light therapy)”, since laser and photodynamic treatment are already covered by the Contraindications item.

Issues 27/09/2026 09:21

1. 1.3 — Hedge dropped in lede: At a Glance (line 433) states the herb ends up “undermining transplant, blood-thinning, contraceptive, antiviral and cancer medications” as a certainty, while the ER Conclusion says this “can undo the benefit of those drugs”.

Fixes 27/09/2026 09:21

1. 1.3 — Restored hedge in lede: Changed “undermining transplant, blood-thinning, contraceptive, antiviral and cancer medications” to “which can undermine transplant, …”, matching the ER Conclusion’s “can undo” (lede now 70 words).

Issues 27/09/2026 09:18

1. 4.2 / 4.3 — Serotonergic supplements label abbreviated: Key Interactions item at line 567 reads “Serotonergic supplements” instead of the ER bold label “Serotonergic supplements with additive effects”.
2. 9.5 — Parenthetical qualifiers dropped entirely: Line 565 omits the ER parenthetical “(cough suppressant)” after Dextromethorphan, and line 566 omits “(drugs moved out of cells by the P-glycoprotein pump)” after Fexofenadine and loperamide.

Fixes 27/09/2026 09:18

1. 4.2 / 4.3 — Serotonergic supplements label restored: Changed “Serotonergic supplements” to the ER bold label “Serotonergic supplements with additive effects” in Key Interactions.
2. 9.5 — Parenthetical qualifiers restored: Added “(cough suppressant)” after Dextromethorphan and “(drugs moved out of cells by the P-glycoprotein pump)” after Fexofenadine and loperamide, as in the ER.

Issues 27/09/2026 09:14

1. 2.7 — Drug-class jargon without glosses: Key Interactions items “Anticoagulants”, “Sulfonylureas” and “Proton pump inhibitors” (QRS lines 558, 563, 564) omit the ER’s plain-language descriptors “blood thinners”, “insulin-releasing diabetes drugs” and “stomach-acid reducers” (ER lines 305, 310, 314).
2. 8.4 — Trailing rationale in contraindication: “Pregnancy or breastfeeding (insufficient human safety data)” (QRS line 548) carries an explanatory parenthetical rather than a qualifier.

Fixes 27/09/2026 09:14

1. 2.7 — Drug-class glosses restored: Added the ER’s plain-language descriptors to Key Interactions: “blood thinners” for Anticoagulants, “insulin-releasing diabetes drugs” for Sulfonylureas and “stomach-acid reducers” for Proton pump inhibitors.
2. 8.4 — Trailing rationale removed: Changed “Pregnancy or breastfeeding (insufficient human safety data)” to “Pregnancy or breastfeeding”.