Audit: QRS - Common Hawthorn for Health & Longevity

Audit conducted on 16/08/2026 12:03 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.	🟢	Protocol, time-to-effect, benefits, risks, gates, all 11 monitoring rows and all 5 qualitative items trace verbatim or near-verbatim to ER lines 305–337, 361–383, 418, 446–474.
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 keeps “less certain”, “missed their main goals”, “raised a signal”; marker_11 keeps “No established target”.
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 remain contraindications; interactions remain interactions; no directional shift found.
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.	🟢	Benefits from Expected Benefits, Risks from Potential Risks & Side Effects, gates from Key Interactions & Contraindications; no cross-category migration.
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.	🟢	No PMIDs, NCT IDs, author names or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind 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.	🟢	Restrained, two-sided framing matching the ER’s Conclusion.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Actionable protocol and monitoring targets presented without hedging or alarm.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Descriptive throughout (“Judging the response before 6 weeks is premature”).
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives directed at a patient outside the fixed template disclaimer.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “advised”, or “should” constructions in populated spans.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns in any populated span.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Acronyms are confined to the biomarker names the ER itself uses (NT-proBNP, hs-CRP, eGFR, QTc).
2.8	Information is presented in a concise and very compact manner	🟢	All list items are single clauses; no prose paragraphs outside At-A-Glance.
2.9	It DOES NOT address the reader directly	🟢	Uses “someone”, not “you” (marker_4_why, qualitative items).
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.	🟢	Dose, split-dosing, monitoring cadence and biomarker targets assume a self-directed implementer.
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.	🟢	11-marker monitoring panel, echocardiogram and trough digoxin level assume high willingness.
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 simplification toward a general-population reader.
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 ejection-fraction benefit/harm split is surfaced in both the gates and marker_4.
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 appear; title 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	“adverse events”, “gastrointestinal complaints”, “orthostatic hypotension”; the plainer terms carried into At-A-Glance are ER-verbatim and required by 7.4.

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 present unmodified at lines 446, 492, 534, 567, 584, 609, 638, 642–644, 814 and in the tier <strong> labels.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 66 named spans present: header (4), at_a_glance, action_1–3 (9), time_1–3 (9), benefits (4), stop/caution (2), risks (4), marker_1–11 (33), monitoring_cadence, qualitative_item_1–5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	website="evidence_review", website="audit" and website="full_review" spans, the CSS block and the footer disclaimer are untouched.

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 mapped to 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 European protocol”, “Best time of day”, “Higher-dose protocol” and all 11 biomarker names are verbatim ER labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect labels are lifted from the ER’s own wording at line 418 (“Symptom and exercise-capacity changes”, “blood-pressure and lipid changes”).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji anywhere; the ER’s 🟩/🟥/🟨 and ⚠️ 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 section is condensed at item level; no section carries prose, citations or effect sizes beyond its 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.	🟢	Lines 2–14, immediately after <!doctype html> at 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 --- at line 3, closing --- at line 13; the descriptive text at line 2 precedes the block.
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.	🟢	Fully enclosed in an HTML comment; no duplicate rendering elsewhere.
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:03" is quoted, correctly, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: common_hawthorn_2026-0816-1000_Opus_ER.md, matching the ER’s own filename field.
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md version badge.
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	Line 6: qrs_creation_date: 2026-0816-1200.
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢	Line 7: 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” — single word, 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]”	🟢	Line 8: 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 qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual 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; consistent and clean.

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 &)	🟢	Line 22: “Common Hawthorn 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 &)	🟢	Line 417: “Common Hawthorn for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 08/16/2026, correctly derived from 2026-0816-1200.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 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.	🟢	Header contains only the title and the standard subline; the ER’s long “Also known as” list was correctly omitted.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses ER line 496 into the decision-relevant core: who benefits, how much, and where the harm signal sits.
7.2	[at_a_glance] is no longer than 60 words	🟢	58 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each of the four claims maps to a distinct clause of the ER Conclusion’s first paragraph.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; uses “heart pump function”, “blood fats”, “pumping function” rather than LVEF/lipids/NYHA.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Refers only to “the two largest trials” and “one re-analysis”.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Uses qualitative magnitudes only (“a small drop”, “modest, less certain gains”).

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Sourced from the “Populations who should avoid Common Hawthorn” list, ER lines 325–337.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER bullets represented; the combined heart-failure/ejection-fraction bullet is correctly split into two items.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <li> elements inside the span, lines 570–579.
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.	🟢	The ER’s trailing rationale clauses (“where the progression signal is strongest”, “where any vasodilator can precipitate collapse”) are all stripped.
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, EF below 25%, systolic below 100 mmHg, 20/10 mmHg on standing and the 90-day window are all retained.
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 identifies six such populations and the section is correctly populated.
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	🟢	Sourced from the ten interaction bullets at ER lines 305–323.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All ten ER interaction bullets present; no overlap with the contraindication gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Ten <li> elements inside the span, lines 587–599.
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.	🟢	Every “Caution — additive hypotension … Mitigation: …” tail and the linked meta-analysis reference are 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).	🟢	Named example drugs retained for beta-blockers, ACE inhibitors/ARBs, nitrates, diuretics, anticoagulants, NSAIDs and the supplement stack.
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 identifies ten and the section is correctly 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	The section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	Sourced from the ER Therapeutic Protocol bullets at lines 361–371.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard 900 mg regimen, dose timing, and the 1800 mg higher-dose option — the three bullets that determine what is actually taken and when.
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 more than three; 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 carry ER-derived content; none is a placeholder.

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	🟢	Symptoms/exercise capacity, blood pressure and blood lipids — the only three onset windows the ER names (line 418).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Symptoms/exercise capacity is the ER’s sole High-tier benefit and comes first; blood pressure then lipids follow the ER’s Medium-tier order.
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; 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.	🟢	Values 6–8 weeks and 10–16 weeks from ER line 418; subs from ER lines 383 and 418.
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 a dedicated “Time to effect” bullet.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All nine benefit headings from ER lines 145–199 are represented.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 536, 542, 548, 555.
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; the ER’s Magnitude lines (5.35 watts, HR 0.59, elastase values) are all omitted.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefits 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	🟢	All ten risk headings from ER lines 223–283 are represented.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 611, 614, 620, 626.
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 event counts, odds ratios and confidence intervals are all omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risks item.
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	🟢	Sourced from the ER Monitoring Protocol & Defining Success table, lines 450–462.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 11 ER table rows present: home blood pressure, resting heart rate, NT-proBNP, LVEF, LDL, triglycerides, hs-CRP, serum digoxin, QTc, eGFR, 6-minute walk distance.
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.	🟢	Lines 804–808 reproduce the ER’s cadence paragraph at line 448, including the 4-week digoxin recheck.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Sourced from the “Qualitative markers worth tracking” list, ER lines 464–474.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER items present verbatim: breathlessness on a familiar task, late-afternoon fatigue, ankle swelling, light-headedness on standing, palpitation awareness.

Issues 16/08/2026 12:03

Pass rate 100.00%. No issues found.