Audit: QRS - Salidroside for Health & Longevity

Audit conducted on 14/08/2026 01:47 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. 🟢 Every gate item, tier item, protocol cell, marker row and cadence string traces to a specific ER passage.
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. 🟢 “theoretical tumor concern”, “No established salidroside target”, “where they occur at all” all carried over.
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. 🟢 Gates draw only from Key Interactions & Contraindications; tiers only from Expected Benefits / Potential Risks & Side Effects.
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. 🟢 The QRS carries no PMIDs, NCT IDs, expert names or brand names at all.
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” 🟢 Cadence and protocol cells state what was done/observed rather than instructing.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronoun appears outside the fixed template disclaimer.
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. 🟢 Monitoring panel assumes routine self-tracking and lab work.
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. 🟢 At-a-glance frames the compound as a low-cost, short-horizon self-experiment.
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 appear.
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 effects”, “hepatic impairment”, “estimated filtration rate” used throughout.

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 heads, 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 resolved; marker_#_* expanded to rows 1–8 and qualitative_item_# to 1–5, giving 63 spans with no missing and no invented names.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 CSS block, structural markup, the website="evidence_review" / website="audit" / website="full_review" spans and the footer disclaimer are identical to the template.

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 into the QRS is empty; every gate, tier, protocol, monitoring and qualitative slot has source content.
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. 🟢 Protocol cells use “Standard isolated-compound dose”, “Standard extract-based dose”, “Best time of day” verbatim; marker names match the ER biomarker table verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Gate-item drug lists are trimmed only within the parentheses, as item 9.5 permits; the label stems are unchanged.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 The ER’s 🟩/🟥/🟨 tier markers and ⚠️ “Conflicted” flags are dropped; no emoji remains in the rendered body.
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. 🟢 Gate items, tier lines and marker rows are all single-fact and short enough to hold the one-page 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 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.
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. 🟢 Only duration: "00:03" is quoted, and it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: salidroside_2026-0814-0008_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]” 🟢 26.7.02, matching this prompt.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 2026-0814-0138
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 just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 Opus
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 [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
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 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. 🟢  

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”.
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”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0814-0138 → 08/14/2026.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “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. 🟢 The ER’s “Also known as” line is not carried into the header.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the Conclusion’s four load-bearing points: endurance/recovery, unsettled mood, animal-only organ claims, short safety record.
7.2 [at_a_glance] is no longer than 60 words 🟢 55 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a sentence in the ER Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain terms throughout (“whole-root extract”, “isolated compound”, “rest on animals”).
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢  
7.6 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 🟢 Drawn from the “Populations who should avoid Salidroside” list.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All 6 ER bullets present, in ER order.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six <li> elements inside the 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. 🟢 Every ER em-dash rationale (“— no reproductive toxicity data…”, “— 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.
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’s contraindication bullets use no ranking notation inside parentheses.
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 section is populated, and the ER does name such populations.
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 🟢  
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All 9 ER interaction bullets present; none overlaps the Contraindications list.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Nine <li> elements inside the 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 item is label-only; the ER’s mitigation prose and the NCT07458594 citation 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 kept in every item, trimmed only of connective prose (“some statins such as”, “sulfonylureas such as glipizide”).
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’s interaction bullets use no ranking notation inside parentheses.
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 section is populated, and the ER does name such 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 The section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Drawn from the 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 are the three decision-relevant bullets; the remaining bullets are contextual.
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 actionable aspects; 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. 🟢 Labels verbatim; values “60 mg daily”, “200–600 mg daily”, “Morning”; subs condensed from the same bullets.

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 🟢 All three clauses of the ER Practical Considerations “Time to effect” bullet are represented.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Perceived exertion (High-tier endurance) → performance and mood markers (High/Medium) → metabolic changes (Low).
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 distinct aspects; 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”, each with an ER-sourced sub-line.
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] 🟢 All four present and populated.
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. 🟢 Sub-heading titles only; all Magnitude: lines dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any tier line.
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 ER tiers carry items.

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] 🟢 All four present and populated.
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. 🟢 Sub-heading titles only; adverse-event percentages and IC50 figures dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any tier line.
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 ER tiers carry items.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Drawn from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 8 rows of the ER biomarker table appear, with targets and rationales matching the ER verbatim.
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, 12-week, 6–12-month schedule plus the 2-week daily self-check condition, all from the ER.

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 🟢 All 5 ER qualitative-marker bullets reproduced verbatim.

Issues 14/08/2026 01:47

Pass rate 100.00%. No issues found.

Issues 14/08/2026 01:42

  1. 9.4 — Trailing explanation in interaction item: The sixth [caution_items] entry (lines 599–602) reads “Over-the-counter analgesics and gastric agents (ibuprofen, omeprazole): no specific interaction identified for isolated salidroside”, appending an explanatory clause that section 9.4 requires be stripped; all other items in the list are label-only.

Fixes 14/08/2026 01:42

  1. 9.4 — Trailing explanation in interaction item: Stripped the explanatory clause from the sixth [caution_items] entry, reducing it from “Over-the-counter analgesics and gastric agents (ibuprofen, omeprazole): no specific interaction identified for isolated salidroside” to the label-only “Over-the-counter analgesics and gastric agents (ibuprofen, omeprazole)”.