Audit: QRS - Dang Shen for Health & Longevity

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

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, values, labels, and statements trace directly to 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 and theoretical phrasings from the ER are preserved.
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”). 🟢 Evidence strength and contraindication/caution levels match the ER without strengthening or softening.
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 exact 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. 🟢 Only terms and formulations present in the source ER (such as Shenqi Fuzheng Injection) appear.
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. 🟢 Tone matches the source ER’s objective, evidence-graded framing.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Language is clear, data-driven, and accessible.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Reads as an objective reference rather than prescriptive clinical orders.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Presents clinical trial and monograph data without giving medical advice.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Describes protocols and evidence rather than advising or recommending.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Never addresses the reader directly.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Uses plain, accessible language.
2.8 Information is presented in a concise and very compact manner 🟢 Information is compactly distilled across all sections.
2.9 It DOES NOT address the reader directly 🟢 No second-person pronouns or direct commands to the reader.
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. 🟢 Tailored to proactive, risk-aware 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. 🟢 Includes practical decoction, cycling, and laboratory monitoring protocols.
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 water down multi-herb limitations or laboratory monitoring requirements.
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. 🟢 Highlights the absence of standalone oral human trials and specific contamination/prostate trade-offs.
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. 🟢 Frames usage in health and longevity terms, never ‘anti-aging’.
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 and scientific terminology 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 fixed card, section, gate, tier, and table headings are unchanged.
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 🟢 Unaddressed website spans are left 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” 🟢 All main sections have ER content; empty benefit/risk tiers use display: none 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, Key Interactions, and Qualitative Assessment.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No labels are 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. 🟢 No emoji indicators appear 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 sits 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 inside the HTML comment.
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. 🟢 Metadata is inside 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 and only duration is quoted due to its colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename is set to dang_shen_2026-1018-0613_Gemini-Argon_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.17.
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-1018-1052.
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-Argon.
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) 🟢 Gemini-Argon follows the nickname rule (Gemini 4 Argon without version number, joined by hyphen).
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 4 Argon.
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) 🟢 Gemini 4 Argon follows the fullname formatting rule.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename is set to dang_shen_2026-1018-0613_Gemini-Argon_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 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 ‘Dang Shen 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 ‘Dang Shen for Health & Longevity’.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 header_subline_date is ‘10/18/2026’.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 header_subline_model is ‘Gemini 4 Argon’.
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 content is 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 Dang Shen as an East Asian tonic root herb and its uses before summarizing evidence.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the ER Conclusion section into an execution-oriented summary.
7.3 [at_a_glance] is no longer than 70 words 🟢 Word count is 66 words (within the 70-word limit).
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Every statement is supported by passages in the ER.
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 trial names, years, sample sizes, or p-values are cited.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, relative risks, or statistical figures are cited.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from the ER Key Interactions & Contraindications section.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Lists all five population contraindications from the ER.
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 items with citations and trailing rationales 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). 🟢 Clinical trial thresholds (ALT/AST > 2.5× ULN, creatinine > 1.5× ULN, BP, NYHA class, platelets) are 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. 🟢 Inequality symbols are numerical thresholds rather than severity ranking notation.
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 because the ER identifies five contraindicated 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 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 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 🟢 Lists all seven key interactions from the ER.
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 items with citations and mechanistic explanations 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/supplements, theoretical status, and the 14-day surgical washout window are 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 severity ranking notation in parens is present in the ER.
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 because the ER identifies seven key 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 Section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from the 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 traditional root decoction/granules, standardized capsule/clinical regimens, and single 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 At least three actionable aspects are present in the ER.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three action cells have label, value, and sub 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 main time-to-effect aspects from the ER.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered matching the ER Expected Benefits order (Respiratory/COPD, Sarcopenia, Endothelial/Vascular).
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 in the ER.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All three time cells have label, value, and sub 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 The ER provides time-to-effect data.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from the 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 spans.
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. 🟢 Lists concise benefit headings separated by semicolons without effect sizes or study details.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content is 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 and benefits_medium spans have style=”display: none”.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from the 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 spans.
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. 🟢 Lists concise risk headings separated by semicolons without frequencies or study details.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content is 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 have style=”display: none”.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER Monitoring Protocol & Defining Success section.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 7 quantitative biomarkers 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 baseline, 4-week, 12-week, and 6-month schedule from the ER.

15. Qualitative Assessment

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

Issues 18/10/2026 11:12

Pass rate 100.00%. No issues found.

Issues 18/10/2026 11:02

  1. 2.7 — Unexpanded clinical acronyms: Line 461 (action_2_sub) uses the acronym “SFI” without defining “Shenqi Fuzheng Injection” anywhere on the sheet, and line 689 (qualitative_item_1) uses “6MWD” without spelling out “six-minute walk distance”.
  2. 4.2 / 10.4 — Mismatched Protocol cell label and subtext: Line 466 (action_3_label) uses the ER’s bold label “Single versus split dosing” (ER line 318), but line 472 (action_3_sub) populates the subtext from the ER’s “Best time of day” bullet (ER line 316) rather than the “Single versus split dosing” bullet.
  3. 8.5 — Omitted drug qualifier in Contraindications: Line 542 (stop_items first bullet, “Men with prostate cancer or prostatic intraepithelial neoplasia”) drops the qualifier from ER line 294 specifying co-treatment (“particularly those treated with abiraterone acetate or AR antagonists”).
  4. 9.4 — Trailing management instruction in Key Interactions: Line 560 (caution_items seventh bullet) includes the trailing management action “preoperative washout” from the body of ER line 290 rather than only the time-window and evidence qualifier (“at least 14 days before elective surgery; theoretical”).
  5. 14.1 / 14.3 — Monitoring cadence includes out-of-section frequency: Line 680 (monitoring_cadence) includes “(PT/INR checked within 7–14 days when starting or stopping alongside anticoagulants)”, which comes from ER Key Interactions & Contraindications (line 286) rather than the ER Monitoring Protocol & Defining Success section (line 359).

Fixes 18/10/2026 11:02

  1. 2.7 — Unexpanded clinical acronyms: Replaced “SFI” in action_2_sub with “Shenqi Fuzheng Injection” and expanded “6MWD” in qualitative_item_1 to “six-minute walk distance (6MWD)”.
  2. 4.2 / 10.4 — Mismatched Protocol cell label and subtext: Replaced action_3_sub with “Taken with meals to maintain steady small-molecule plasma levels and minimize gastrointestinal osmotic load” so it matches the ER’s “Single versus split dosing” bullet.
  3. 8.5 — Omitted drug qualifier in Contraindications: Restored the ER’s co-treatment qualifier “(particularly those treated with abiraterone acetate or androgen receptor antagonists)” to the first bullet of stop_items.
  4. 9.4 — Trailing management instruction in Key Interactions: Removed the management instruction “preoperative washout” from the seventh bullet of caution_items, retaining only the qualifier “(at least 14 days before elective surgery; theoretical)”.
  5. 14.1 / 14.3 — Monitoring cadence includes out-of-section frequency: Removed “(PT/INR checked within 7–14 days when starting or stopping alongside anticoagulants)” from monitoring_cadence so the cadence derives strictly from the ER Monitoring Protocol & Defining Success section.