Audit: QRS - Elderberry for Health & Longevity

Audit conducted on 12/09/2026 10:39 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	85
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.	🟢	Protocol values, time-to-effect values, tiered benefit/risk labels, gate items, biomarker rows and qualitative items all trace to ER lines 337–347, 396–398, 157–195, 223–269, 285–315 and 428–445.
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 documented interaction” (NSAIDs) and “vaccination is unaffected” carried through verbatim from ER lines 299 and 305.
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 absolute; the NSAID entry retains its null-finding status rather than implying an interaction.
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 only from the ER “Populations who should avoid Elderberry” list; Key Interactions only from the ER interaction bullets; no modifying factors were promoted.
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 identifiers, expert names or brand names (e.g., Sambucol, BerryPharma) appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind in the QRS body.

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, sceptical register of the ER Conclusion is preserved in the At-A-Glance and tier lists.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified protocol and monitoring cells paired with plain-language framing.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents regimens and targets as what was studied, not as instructions.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Clinical-sounding phrases (e.g., the upper-abdominal-pain qualitative item) are ER-verbatim descriptions of what is worth tracking.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “should”, or “advised” in the QRS body.
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 retained are drug-class names and biomarker names that have no plain equivalent.
2.8	Information is presented in a concise and very compact manner	🟢	Gate items, tier lists and monitoring rows are reduced to key facts; ER glosses and mitigations stripped.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: 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.	🟢	Functional-range biomarker targets and episode logging assume a proactive self-quantifying 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.	🟢	Four-times-daily dosing and multi-marker laboratory panels are presented without hedging on burden.
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 casual consumer use.
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 foregrounds funding bias and product adulteration, which matter to this audience more than the headline symptom claim.
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.	🟢	“anti-aging” does not occur; the 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)”; “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.	🟢	“syrup”, “extract capsules”, “fat oxidation”, “cyanide-type poisoning” are the ER’s own formal terms; no consumer-grade substitutions.

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 headings match the template byte-for-byte; the “High” tier labels are absent only because their spans are hidden under 12.5 / 13.5.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Diff of the variable-name sets shows only the expected expansion of marker_#* into marker_1..8* and qualitative_item_# into 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 footer disclaimer and all structural comments 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 source ER section that feeds 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.	🟢	“Acute-illness regimen”, “Travel and prevention regimen”, “Best time of day”, “Time to effect — acute use”, “Time to effect — metabolic use” and “Other interventions” are carried over verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	The only non-bold-label cell title, time_3_label “Cognitive and inflammation signals”, is lifted from the ER’s own wording at line 398.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji present; the ER’s ⚠️ Conflicted markers were stripped.
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 reduced to its minimum: mitigations, glosses and trailing clauses stripped from gate items; magnitudes and mechanisms stripped from tier lists.

---

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 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.	🟢	Opening “—” at line 3, closing at line 13; the caption text precedes it.
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 and not duplicated in the header or footer.
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: elderberry_2026-0912-0838_Opus_ER.md
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: 26.9.11, 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: 2026-0912-1036.
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: 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)	🟢	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: 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 only, no context-window or other qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches 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.	🟢	Confirmed across all nine template keys plus the appended git_user / git_issue keys.

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: “Elderberry 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: “Elderberry for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 09/12/2026, from qrs_creation_date 2026-0912-1036.
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 template subline.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Compresses ER lines 467–469: what it is, when it is used, the strength and funding of the evidence, and the two real hazards.
7.2	[at_a_glance] is no longer than 60 words	🟢	57 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each of the six clauses maps to a distinct sentence in the ER Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “deeply pigmented”, “cyanide-type poisoning” and “extract makers” are lay-readable.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Refers to “small studies” and “the one independent trial” without identifying either.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items come from the “Populations who should avoid Elderberry” list at ER lines 307–315.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoid-populations are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <li> elements inside the stop_items span.
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.	🟢	“— safety data are absent rather than reassuring” and “, the age band below which no elderberry trial has enrolled participants” were both 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).	🟢	“at any stage”, “on maintenance immunosuppression”, “requiring drug control (Hashimoto thyroiditis, lupus, rheumatoid arthritis)”, “of unexplained cause” and “under 5 years” 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 names seven 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	🟢	All ten items come from the interaction bullets at ER lines 287–305.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All ten ER interaction bullets are present; the contraindication entries are population-based and name no drug class, so nothing is duplicated.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Ten <li> elements inside the caution_items span.
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/Monitor” verdict, mechanism sentence and “Mitigation:” clause was removed; the two retained tails (“no documented interaction”, “vaccination is unaffected”) are required null findings under 1.2 / 1.3.
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).	🟢	All example-drug lists retained, with the ER’s inline definitions trimmed (e.g., diuretics reduced to “furosemide, hydrochlorothiazide, spironolactone”).
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 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	🟢	All three cells come from the ER Therapeutic Protocol bullets at lines 337, 339 and 347.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Acute-illness regimen, travel/prevention regimen and dose timing are the only directly executable bullets; the remainder are competing-approach, pharmacokinetic or “no difference established” entries.
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 or more 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 carry ER-derived content; doses (15 mL 4×/day for 5 days, 175–300 mg, 600 mg → 900 mg) match ER lines 337 and 339 exactly.

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	🟢	Acute respiratory (2–4 days), metabolic (7 days) and cognitive/inflammation (3–6 months), from ER lines 396 and 398 — the only time-to-effect statements in the ER.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Respiratory and metabolic are the two Medium-tier benefits and lead; the cognitive/inflammation signals are Low and Speculative and come last.
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 distinct aspects exist 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; values and subs track ER lines 396–398 verbatim or near-verbatim.
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, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Each entry corresponds to an ER benefit heading at lines 157–195.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present.
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.	🟢	Only the benefit names are carried; every Magnitude figure and “Net reading” sentence was dropped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content remains in any tier.
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.	🟢	benefits_high carries style=”display: none” and no empty-state text, matching the ER’s “No benefit reaches High” at line 153.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Each entry corresponds to an ER risk heading at lines 223–269.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present.
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.	🟢	Only the risk names are carried; the outbreak figures, case counts and adulteration numbers were dropped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content remains in any tier.
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_high carries style=”display: none” and no empty-state text, matching the ER’s “No risk reaches High” at line 219.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows and cadence come from the ER Monitoring Protocol & Defining Success section at lines 424–437.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All eight ER table rows — fasting glucose, HbA1c, fasting insulin, TSH, free T4, hs-CRP, ALT and the respiratory episode log — are present with matching targets and “Why” text.
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.	🟢	Baseline, 8–12 weeks, 6–12 months, end-of-season and the 12-week thyroid recheck all carried from ER lines 424–426.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All five items come from the qualitative-marker list at ER lines 441–445.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER bullets are present, verbatim.

Issues 12/09/2026 10:39

Pass rate 100.00%. No issues found.