Audit: QRS - Butcher’s Broom for Health & Longevity

Audit conducted on 14/10/2026 22:34 using AI4L + evidence-mcp / Gemini 3.1

Iterations

Summary

Items Count
Total 94
Passed 89
Failed 0
N/A 5
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 claims, magnitudes, labels, and statements match the source ER.
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 phrasing (“No established target”, “rare”, “mostly in formulas”) is preserved from the ER.
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”). 🟢 No claims are strengthened or softened relative to the ER.
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. 🟢 All items remain in their proper ER decision categories.
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. 🟢 Named products (Cyclo 3 Fort) and Commission E appear in the source ER for the same facts.
1.6 The QRS does not introduce new attributions. 🟢 No new attributions are 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. 🟢 Matches the objective, evidence-graded tone of the source ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Accessible and data-driven throughout.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence descriptively without prescriptive language.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No medical advice phrasing; footer disclaimer intact.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Descriptive phrasing used throughout all sections.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns or imperative commands directed at the reader.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms (e.g., HMC, cytolytic hepatitis, ketoacidosis) are explained or replaced with plain language.
2.8 Information is presented in a concise and very compact manner 🟢 Compact, single-page density.
2.9 It DOES NOT address the reader directly 🟢 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. 🟢 Framed for proactive health- and longevity-oriented adults.
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 details reflect a proactive audience.
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. 🟢 Does not dilute protocol or biomarker tracking for general-population convenience.
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. 🟢 Takeaways distinguish standalone vs. combination evidence and industry sponsorship.
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. 🟢 Uses “longevity” framing; no “anti-aging” terminology.
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. 🟢 Uses formal clinical terminology (“oral extracts”, “oral use”).

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 table column headers are unmodified.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All data-qrs-var spans from QRS.html are present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 All website=”…” spans and static template elements are unchanged.

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” 🟢 No full ER sections mapped to the QRS are empty; empty benefit/risk tiers are hidden per 12.5/13.5.
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. 🟢 Bold labels from the ER are used verbatim in Protocol, Contraindications, Key Interactions, and Qualitative Assessment.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels are verbatim from 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 indicators are present in the QRS.
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. 🟢 Condensed to fit a single A4 page.

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 immediately 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. 🟢 YAML block is delimited by — lines.
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 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. 🟢 All frontmatter values are properly trimmed; only duration (“00:05”) is quoted due to the colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename is set to butchers_broom_2026-1014-2111_Gemini_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]” 🟢 qrs_prompt_version is set to 26.10.14.
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 is set to 2026-1014-2220.
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 is set to Gemini.
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 nickname “Gemini”.
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 is set to Gemini 3.1.
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) 🟢 Full name “Gemini 3.1” consists of nickname and version number only.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches butchers_broom_2026-1014-2111_Gemini_QRS.html.
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. 🟢 All frontmatter values are clean and properly trimmed.

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 &) 🟢 page_title is “Butcher’s Broom 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., &amp; for &) 🟢 header_topic is “Butcher’s Broom for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 header_subline_date is 10/14/2026.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 header_subline_model is Gemini 3.1.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 No extra header elements added.

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 by defining Butcher’s Broom as a Mediterranean shrub whose root extract is used for leg vein tone and swelling.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Dense summary of the ER Conclusion covering evidence tier, sponsorship, standalone vs. combination formulas, and safety.
7.3 [at_a_glance] is no longer than 70 words 🟢 65 words (under the 70-word maximum).
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Every statement maps directly to the ER Conclusion.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Uses plain language without unexplained acronyms or specialist jargon.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No specific trial citations, years, sample sizes, or p-values.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, relative risks, or statistical figures.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All 5 populations who should avoid Butcher’s Broom from the ER are listed.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Formatted as <li> elements.
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. 🟢 Concise labels only; trailing explanations and citations 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). 🟢 Parenthetical age threshold (<18 years) 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. 🟢 No ranking notation symbols requiring normalization.
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 is populated with the 5 ER contraindications.
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 Contraindications section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER Key Interactions & Contraindications.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All 7 key interactions from the ER are listed without duplicating contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Formatted as <li> elements.
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. 🟢 Concise labels and example lists only; trailing explanations and citations 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). 🟢 Parenthetical drug and supplement example lists preserved.
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. 🟢 No ranking notation symbols requiring normalization.
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 is populated with the 7 ER interactions.
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 Key Interactions section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from ER Therapeutic Protocol section.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Covers the three key actionable protocols: single-herb regimen, European combination regimen, and once-daily morning vs. split dosing.
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 All three action sets are populated.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All action_1..3 label, value, and sub spans are populated from the ER.

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 🟢 Covers the three time-to-effect aspects documented in the ER.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered by benefit tier/magnitude: CVI (Medium), Secondary Lymphedema (Low RCT), Hemorrhoidal Relief (Low observational).
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 All three time sets are populated.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All time_1..3 label, value, and sub spans are populated 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 Time-to-effect information is present in the ER.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from ER Expected Benefits section.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 Uses benefits_high, benefits_medium, benefits_low, and 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. 🟢 Concise outcome names only; emoji flags and elaborations stripped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content included.
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 span is hidden with style=”display: none”.

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 section.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 Uses risks_high, risks_medium, risks_low, and 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. 🟢 Concise risk names only; emoji flags and elaborations stripped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content included.
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 and risks_medium spans are hidden with style=”display: none”.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from ER Monitoring Protocol & Defining Success section.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 4 measurable biomarker rows from the ER table are included.
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. 🟢 monitoring_cadence is populated with the ER baseline and follow-up schedule.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from ER Monitoring Protocol & Defining Success section.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 3 qualitative assessment items from the ER are included.

Issues 14/10/2026 22:34

Pass rate 100.00%. No issues found.

Issues 14/10/2026 22:28

  1. 2.7 — Unexpanded acronym and specialist jargon: Line 461 (action_2_sub) uses the unexpanded acronym “HMC”, line 489 (time_1_sub) uses specialist terms “Capillaroscopic and plethysmographic improvements” without plain-language explanation, and lines 629 and 640 (marker_3_why, marker_4_why) use “cytolytic hepatitis” and “glycemic decompensation” without plain-language terms.

Fixes 14/10/2026 22:28

  1. 2.7 — Unexpanded acronym and specialist jargon: Expanded “HMC” to “hesperidin methyl chalcone [HMC, citrus flavonoid]” in action_2_sub, replaced “Capillaroscopic and plethysmographic improvements” with “Microscopic capillary imaging and limb blood-volume improvements” in time_1_sub, and added plain-language explanations in marker_3_why and marker_4_why.