Audit: QRS - Salidroside for Health & Longevity

Audit conducted on 22/09/2026 19:30 using AI4L + evidence-mcp / Opus 5

Iterations

Summary

Items Count
Total 94
Passed 84
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 doses, time-to-effect values, tier items, gates, biomarker targets and cadence all trace to ER Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications and Monitoring Protocol & Defining Success.
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. 🟢 E.g. marker_7_target keeps “No established salidroside target; track change from the individual’s own 7-day baseline”; speculative risk keeps “theoretical tumor concern”.
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; interactions remain cautions; “plausible but unsettled” mood framing preserved in at_a_glance.
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. 🟢 stop_items come only from “Populations who should avoid Salidroside”; caution_items only from the interaction bullets; no modifying factor is promoted into a gate.
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 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. 🟢 Phrasing is largely lifted from ER sentences (“Better endurance and faster recovery from hard training are the best-established effects”).
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Targets, cadence and tiers are concrete; framing is neutral and actionable.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is stated as observed evidence and tested regimens, not orders.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Monitoring cadence and gates are descriptive; footer disclaimer retained from template.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “should”, “recommend” or “advise” in the document’s own voice.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the sheet.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Jargon is limited to drug/enzyme names required for the interaction gate; at_a_glance is jargon-free.
2.8 Information is presented in a concise and very compact manner 🟢 Tier lines are semicolon-joined headings; gate items carry no rationale.
2.9 It DOES NOT address the reader directly 🟢 Confirmed: no “you” / “your” in any span.
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. 🟢 Content assumes self-tracking (baseline panel, HRV, time-trial-style qualitative markers).
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. 🟢 12-week lab panel, daily self-checks and pre-training dosing timing are presented without hedging on 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. 🟢 Optimal functional ranges (e.g. hs-CRP < 0.5 mg/L) rather than conventional lab cut-offs are used.
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 closes on the low-cost, low-risk short-term experiment framing drawn from the ER Conclusion.
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 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. 🟢 Uses “dietary supplement”, “adverse effects”, “extract”; no lay route-of-administration phrasing.

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, gate headings, tier labels and column headers match the template byte-for-byte.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 38 template variables present; marker_#* expanded to marker_1..8 and qualitative_item# to items 1–5.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The website="evidence_review", website="audit" and website="full_review" spans and all surrounding markup 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” N/A No source ER section used by 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 isolated-compound dose”, “Standard extract-based dose”, “Best time of day” are verbatim ER bold labels; monitoring row labels are verbatim ER biomarker names.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No label is shortened or reworded.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji anywhere in the file; the ER’s ⚠️ “Conflicted” markers were dropped, not carried over.
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 at its condensed form: tier lines are bare headings, gate items carry no rationale, marker “why” cells are single clauses.

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 “—” line 3, closing “—” line 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; no metadata value is repeated in the header or body.
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, which the colon requires.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: salidroside_2026-0814-0008_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.9.22 matches 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) 🟢 qrs_creation_date: 2026-0922-1919.
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.
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]” 🟢 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” carries no additional qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: salidroside_2026-0814-0008_Opus_QRS.html 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. 🟢 Re-verified across all nine keys; no stray whitespace or 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 &) 🟢 “Salidroside 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 &) 🟢 “Salidroside for Health & Longevity” (line 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0922 → “09/22/2026” (line 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5” (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 block is structurally identical to the template; the ER’s “Also known as” line was not carried over.

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 “Salidroside is the main active compound of golden root, a plant sold as a dietary supplement for fatigue, stress and endurance”.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Mirrors the ER Conclusion: best-established endurance/recovery effect, unsettled mood claim, animal-only organ claims, low-cost short experiment.
7.3 [at_a_glance] is no longer than 70 words 🟢 64 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to Motivation, Practical Considerations (supplement status) or Conclusion.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; uses “golden root” rather than the binomial and “made by fermentation” rather than “bioengineered”.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial reference of any kind.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numbers appear in the lede.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All six items come from “Populations who should avoid Salidroside” in that ER section.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoid-populations are present, in ER order.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six <li> elements inside the span (lines 566–574).
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. 🟢 Every ER em-dash rationale (“— no reproductive toxicity data in humans…”, “— no trial has enrolled them”) is 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). 🟢 “(estimated filtration rate below 30 mL/min/1.73 m², or dialysis)” and “(Child-Pugh Class C)” retained; “current or historical” and “under 18” 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 these bullets.
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 six such populations and the section is correspondingly 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 eight items map to interaction bullets in that ER section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All ER interaction bullets are represented except the explicit no-interaction bullet (OTC analgesics and gastric agents); no contraindication is duplicated.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eight <li> elements inside the span (lines 582–603).
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. 🟢 Mechanistic text (“Pump inhibition raises absorption…”) and the NCT citation in the stimulant bullet 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). 🟢 Every ER drug list is carried (tacrolimus/cyclosporine/ivabradine/simvastatin; digoxin/dabigatran/apixaban; metformin/sulfonylureas/insulin/SGLT2 inhibitors; etc.), plus the “two-week pre-surgical stop” window and the “whole-root extract” applicability qualifier.
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 these bullets.
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 several interactions and the section is correspondingly 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 derive from ER Therapeutic Protocol bullets.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Isolated-compound dose, extract-based dose and timing — the only directly executable bullets; the remaining bullets are background (half-life, popularizers, competing approaches).
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 aspects exist 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. 🟢 “60 mg daily”, “200–600 mg daily”, “Morning” with ER-sourced subs (8–12 weeks, 3% rosavins / 1% salidroside ≈ 2–6 mg, 30–60 min pre-training).

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 🟢 Perceived exertion, performance & mood markers, metabolic changes — the three clauses of the ER “Time to effect” bullet.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered high (endurance/fatigue) → medium (performance and mood) → low (metabolic).
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. 🟢 “Within hours”, “2–4 weeks”, “Longer” with ER-sourced subs.
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 in Practical Considerations.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Each tier line lists the ER subsection headings for that tier.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (lines 536–556).
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. 🟢 Bare headings joined by semicolons; no “Magnitude” text carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in any benefit 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 have ER content.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Each tier line lists the ER subsection headings for that tier.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (lines 615–632).
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. 🟢 Bare headings joined by semicolons; adverse-event percentages and inhibitory concentrations are not carried over.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in any risk 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 have ER content.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows and cadence come from ER Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight rows of the ER biomarker table are present with matching names, optimal functional ranges and rationales.
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, 4-week glucose/insulin recheck, 12-week full panel, 6–12 month interval and the 2-week daily self-check caveat, matching the ER.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Items are the ER’s qualitative-marker bullet list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER bullets present, verbatim and in ER order.

Issues 22/09/2026 19:30

Pass rate 100.00%. No issues found.

Issues 22/09/2026 19:25

  1. 2.5 / 9.4 — Imperative surgery-stop instruction: The Key Interactions item at line 603 ends “(discontinue two weeks before elective surgery)”, an imperative mitigation instruction rather than the interaction fact; the ER states it descriptively at line 317 (“discontinuing two weeks before elective surgery is the conventional mitigation”) and the QRS bullet has no such parenthetical in its ER source label.

Fixes 22/09/2026 19:25

  1. 2.5 / 9.4 — Imperative surgery-stop instruction: Rewrote the anticoagulant Key Interactions item from “Anticoagulant therapy and surgery (discontinue two weeks before elective surgery)” to “Anticoagulant therapy and elective surgery (two-week pre-surgical stop)”, removing the imperative mitigation instruction while keeping the time window as a descriptive qualifier.