Audit: QRS - Black Currant for Health & Longevity

Audit conducted on 17/10/2026 18:25 using AI4L + evidence-mcp / Gemini 4 Argon

Iterations

Summary

Items Count
Total 94
Passed 88
Failed 0
N/A 6
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. 🟢  
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. 🟢  
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”). 🟢  
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. 🟢  
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. 🟢  
1.6 The QRS does not introduce new attributions. 🟢  

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 🟢  
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 🟢  
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢  
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. 🟢  
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. 🟢  
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. 🟢  

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”
🟢  
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢  
3.3 Spans that are not addressed in a checklist item are left 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” 🟢  
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. 🟢  
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢  
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢  
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. 🟢  

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. 🟢  
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. 🟢  
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]” 🟢  
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢  
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 the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT) 🟢  
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 model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y) 🟢  
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., &amp; for &) 🟢  
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢  
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢  
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢  
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 🟢  
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 🟢 69 words.
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 🟢  
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). 🟢  
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. 🟢  
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. 🟢  
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 is 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 🟢  
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). 🟢  
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. 🟢  
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. 🟢  
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 is 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 🟢  
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 distinct actionable implementation aspects are present.
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 🟢  
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢  
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 time-to-effect aspects are present.
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 The 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 present in the ER.

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_high span is hidden via style="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 🟢  
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 🟢  

Issues 17/10/2026 18:25

Pass rate 100.00%. No issues found.

Issues 17/10/2026 18:13

  1. 1.2 / 1.3 — Cautious phrasing and acute scope: In [at_a_glance] (line 433), the QRS narrows the ER Conclusion’s high-certainty scope (“when taken at sufficient doses or loaded over multiple days”, ER line 373) to “Multi-day berry extracts” and collapses the ER’s distinction between “low and conflicted” human evidence and preclinical-only longevity evidence into “remain unproven”.
  2. 4.2 / 10.4 — Cross-bullet content merged in Protocol: In action_1_sub (line 450) and action_3_sub (line 472), content from separate ER protocol bullets (**Bone density and ocular protocols:** and **Pharmacokinetic half-life and split dosing:**) is merged under other bullets’ labels rather than matching each cell’s verbatim ER label.
  3. 4.3 / 11.4 — Mismatched Time to Effect labels: time_3_label (line 505, Vascular FMD, immunity, bone, and glaucoma) invents a composite label not present in the ER Time to effect bullet (ER line 335), while time_2_sub (line 500) includes 1.22-fold forearm blood flow and time_3_sub (line 511) includes -32.83 points joint pain (6 months) that do not match their cell labels.
  4. 7.2 / 7.3 — Incomplete and over-length At-A-Glance summary: [at_a_glance] (line 433) omits the second paragraph of the ER Conclusion (ER line 375) covering capsule tolerability, acidic juice enamel erosion, digestive upset, and drug interactions, and reaches 71–73 words when em-dash and hyphenated compounds (supplements—berry, Multi-day, after-meal) are split.
  5. 9.4 / 9.5 — Key Interactions parentheticals altered: [caution_items] (lines 553–558) injects trailing protocol instructions (14-day separation, line 553) and study details (1% phytic acid concentration, line 558) while dropping human pharmacodynamic data (line 553; ER line 280) and from human biomarker data (line 554; ER line 281) from the ER parenthetical qualifiers.
  6. 10.1 — Non-Protocol content in action cell: action_2_sub (line 461) includes "divided with meals", which comes from Risk Mitigation Strategies (ER line 300) rather than the ER Therapeutic Protocol section (ER lines 305–318).
  7. 11.2 — Time to Effect misordered: Time to Effect places a High-tier vascular benefit (+2.0 percentage points brachial FMD (6 weeks) in time_3, lines 505–511) after Medium- and Low-tier benefits (vision and MAO-B inhibition in time_2, lines 494–500) instead of ordering cells by the magnitude of the related benefit.

Fixes 17/10/2026 18:13

  1. 1.2 / 1.3 — Cautious phrasing and acute scope: Updated [at_a_glance] to state “Sufficient or multi-day extracts” and preserve the ER Conclusion’s distinction between “low and conflicted” human evidence (gut, blood pressure, cholesterol, memory) and longevity evidence “confined to yeast and mice”.
  2. 4.2 / 10.4 — Cross-bullet content merged in Protocol: Restricted action_1_sub and action_3_sub to the content of their respective ER protocol bullets (Standard cardiometabolic and exercise protocol and Optimal time of day), removing merged bone/ocular and split-dosing details from other bullets.
  3. 4.3 / 11.4 — Mismatched Time to Effect labels: Changed time_3_label to Immunity, bone, and glaucoma to match the ER Time to effect bullet and removed 1.22-fold forearm blood flow from time_2_sub and -32.83 points joint pain (6 months) from time_3_sub.
  4. 7.2 / 7.3 — Incomplete and over-length At-A-Glance summary: Added capsule tolerability versus juice tooth erosion from the second paragraph of the ER Conclusion and condensed [at_a_glance] to 66 words (67 when hyphen-split).
  5. 9.4 / 9.5 — Key Interactions parentheticals altered: Restored human pharmacodynamic data (line 553) and from human biomarker data (line 554) in [caution_items] while removing the trailing protocol instruction 14-day separation and study detail ; 1%.
  6. 10.1 — Non-Protocol content in action cell: Replaced "divided with meals" in action_2_sub with "for anti-inflammatory support" from the ER Therapeutic Protocol section.
  7. 11.2 — Time to Effect misordered: Removed the High-tier Vascular FMD item from time_3 so that the three Time to Effect cells are strictly ordered from High-tier (time_1) to mixed High/Medium/Low acute (time_2) to Medium-tier (time_3) benefits.

Issues 17/10/2026 18:03

  1. 1.1 / 7.4 — Conflated berry extract and seed oil benefits: In at_a_glance (line 433), "Multi-day berry extracts strongly improve exercise fat burning, artery flexibility, and after-meal blood sugar, with moderate evidence for bone, eye, joint, and immune health..." attributes joint and immune health to berry extracts, whereas the source ER (Expected Benefits line 172; Conclusion line 373) attributes bone and eye health to berry pigments and joint tenderness and older-adult immunity to seed oil.
  2. 9.5 — Truncated parenthetical qualifiers in interactions: In caution_items (lines 557–558), L-theanine is omitted from the ER’s parenthetical supplement example list (fish oil, Ginkgo, berberine, L-theanine) (ER line 285), and the phytic acid/irinotecan qualifier (human pharmacokinetic data for phytic acid; theoretical for irinotecan) (ER line 286) is truncated to (irinotecan; theoretical) while modifying (inositol hexaphosphate) to (inositol hexaphosphate, 1%).
  3. 11.2 — Time to effect ordered chronologically: In Time to effect (lines 480–514), the three sets are ordered chronologically (1–2 hours, 7–8 days, 4–8 weeks to 24 months) rather than by the magnitude of the related benefit, placing time_1 (Glycemic blunting, vision, and MAO-B inhibition, which includes Medium-tier vision and Low-tier MAO-B inhibition) before time_2 (Fat oxidation and insulin sensitivity, 7–8 days, which covers exclusively High-tier benefits with +22% insulin sensitivity and +0.042 g/min / +27% fat oxidation).

Fixes 17/10/2026 18:03

  1. 1.1 / 7.4 — Conflated berry extract and seed oil benefits: Updated at_a_glance to explicitly state that berry extracts moderately support bone and eye health while seed oil moderately supports joint and immune health.
  2. 9.5 — Truncated parenthetical qualifiers in interactions: Restored L-theanine to (fish oil, Ginkgo, berberine, L-theanine; theoretical additive effect) and restored (human pharmacokinetic data for phytic acid; theoretical for irinotecan) in caution_items.
  3. 11.2 — Time to effect ordered chronologically: Reordered time_1 and time_2 so the High-tier Fat oxidation and insulin sensitivity (7–8 days) set precedes Glycemic blunting, vision, and MAO-B inhibition (1–2 hours).