Audit: QRS - Common Hawthorn for Health & Longevity

Audit conducted on 07/07/2026 14:38 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 83
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 protocol, benefit, risk, monitoring, and at-a-glance content maps to the ER (dose 160–900 mg/day → ER line 327; benefits/risks tiers → ER §Expected Benefits/§Potential Risks; monitoring markers → ER table lines 402–409).
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. 🟢 At-a-glance “weak or unproven” mirrors the ER Conclusion’s hedged language; no cautious ER claim was hardened.
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 and interactions preserve ER severity; no strengthening or softening observed.
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 derive from the ER §Key Interactions & Contraindications; no modifying factors were promoted to gates.
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 brand names WS 1442 and LI 132 appear, both present in ER lines 220/327/331. No PMIDs, NCT IDs, or expert names introduced.
1.6 The QRS does not introduce new attributions. 🟢 No new attributions present.

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-graded tone matches the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Consistent throughout.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Information is presented, not prescribed.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Content presents data; footer carries the “Not medical advice” disclaimer.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Protocol/monitoring cells state facts, not recommendations.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address in any variable.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 At-a-glance uses plain language (“heart weakness”); technical terms confined to monitoring targets.
2.8 Information is presented in a concise and very compact manner 🟢 All cells are compact.
2.9 It DOES NOT address the reader directly 🟢 No direct 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 matches the health/longevity-oriented audience.
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 and monitoring detail assume a proactive 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 written for a general-population audience.
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/risk weighting reflects the target 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” phrasing present.
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. 🟢 Terminology is clinical/scientific; ER-derived headings retained verbatim.

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 labels/headings present and unmodified (lines 440, 477, 519, 565, 584, 692, 539, 548, tier labels, and 588–590).
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All expected named spans (header, at_a_glance, action/time sets, benefits, gates, risks, markers, cadence, qualitative) are present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No unaddressed span appears 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” N/A No source ER section relevant to the QRS is empty; every tier and section is populated.
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. 🟢 Benefit/risk tiers and monitoring markers preserve ER labels; protocol cells appropriately distill the ER Protocol bullets per §10.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Monitoring, benefit, and risk labels match the ER.
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 QRS; the ER’s tier emojis were 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 is condensed to a single-page budget.

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 the 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. 🟢 Enclosed in an 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; only “duration” is quoted (contains a colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 “er_filename: common_hawthorn_2026-0707-1257_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” (line 5).
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-0707-1425” (line 6).
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” (line 7).
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 4.8” (line 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: common_hawthorn_2026-0707-1257_Opus_QRS.html” (line 9).
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. 🟢 Confirmed trimmed and correctly quoted.

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 &) 🟢 “Common Hawthorn 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 &) 🟢 “Common Hawthorn for Health & Longevity” (line 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 qrs_creation_date 2026-0707-1425 → “07/07/2026” (line 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 4.8” (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 carries only date, source-ER reference, AI4L link, and model.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Summarizes the ER Conclusion (lines 432–434).
7.2 [at_a_glance] is no longer than 60 words 🟢 53 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each claim maps to a distinct Conclusion passage.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Uses “heart weakness”, “heart and blood-pressure medicines”; no NYHA/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 🟢 Derived from ER line 307 (populations to avoid).
8.2 [stop_items] represent the Contraindications from the ER 🟢 Pregnancy/breastfeeding, severe/decompensated HF (NYHA IV), symptomatic low BP, children — all from ER line 307.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each item is a <li> (lines 541–544).
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. 🟢 Items are bare facts with no trailing clauses.
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). 🟢 “(NYHA class IV)” preserved on the severe heart failure item.
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. 🟢 ER contraindications use no ranking notation; nothing to normalize.
8.7 If no [stop_items] are present the section is left empty N/A Contraindication items are present, so the empty-state condition does not apply.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER lines 293–306.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Seven interaction bullets carried; no overlap with the population-based contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each item is a <li> (lines 550–556).
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. 🟢 ER “— additive…” trailing clauses were stripped; only the drug classes remain.
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 preserved (digoxin/digitoxin, nitroglycerin/sildenafil, etc.); antihypertensive parenthetical retained as drug classes, trimmed but not 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. 🟢 ER interactions use no ranking notation; nothing to normalize.
9.7 If no [caution_items] are present the section is left empty N/A Key Interaction items are present, so the empty-state condition does not apply.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from ER §Therapeutic Protocol (lines 327–335).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard Dose, Form, and Frequency capture 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 The ER supplies three distinct actionable aspects, so the “less than three” condition does not apply.
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 carry ER-derived label/value/sub 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 🟢 Symptom Relief (several weeks), Judge Response (6–8 weeks), Trial Window (4–24 weeks) — all from ER line 374.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered from earliest symptomatic onset to trial measurement window, consistent with the high-tier symptom/exercise benefits.
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 used, so the “less than three” condition does not apply.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All three time sets carry ER-derived content.
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 (line 374), so the removal condition does not apply.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from ER §Expected Benefits (lines 157–213).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four tier spans populated to match ER tiers.
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. 🟢 Concise tier facts; ER magnitudes and mechanisms omitted.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried; ER “⚠️ Conflicted” marker dropped.
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 contain items, so the empty sub-section condition does not apply.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from ER §Potential Risks & Side Effects (lines 231–275).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four tier spans populated to match ER tiers.
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. 🟢 Concise tier facts; ER magnitudes/frequencies omitted.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried.
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 contain items, so the empty sub-section condition does not apply.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from ER §Monitoring Protocol & Defining Success (lines 394–409).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight biomarkers (BP, resting HR, exercise tolerance, NT-proBNP, LVEF, lipid panel, digoxin level, eGFR) are listed with matching targets.
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 matches ER line 398 (baseline, 6–12 weeks, then every 6–12 months).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from ER qualitative markers (lines 413–416).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All four qualitative markers listed verbatim.

DO NOT remove the <section> tags below. They are used for internal linking and must remain in place

Issues 07/07/2026 14:38

Pass rate 100.00%. No issues found.

Issues 07/07/2026 14:29

  1. 4.2 / 4.3 — Paraphrased interaction label: The 6th [caution_items] entry (QRS line 555) reads “Blood-pressure-lowering supplements (garlic, hibiscus, magnesium, CoQ10, L-arginine)”, but the ER’s verbatim bold label (ER line 303) is “Supplements with additive blood-pressure or blood-flow effects”; the label was paraphrased/reinvented from ER body text rather than carried through verbatim.

Fixes 07/07/2026 14:29

  1. 4.2 / 4.3 — Verbatim interaction label restored: Changed the 6th [caution_items] entry from “Blood-pressure-lowering supplements (garlic, hibiscus, magnesium, CoQ10, L-arginine)” to the ER’s verbatim bold label “Supplements with additive blood-pressure or blood-flow effects (garlic, hibiscus, magnesium, CoQ10, L-arginine)”, preserving the example drug list.