Audit: QRS - Dang Shen for Health & Longevity

Audit conducted on 17/08/2026 21:13 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	85
Failed	0
N/A	8
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 protocol values, gate items, tier entries, biomarker rows and qualitative items trace to ER Therapeutic Protocol, Key Interactions & Contraindications, Expected Benefits, Potential Risks & Side Effects 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.	🟢	“Nothing in the literature reports an acute effect” (time_3_sub) is carried verbatim from ER line 387.
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”).	🟢	ER “Avoid” items (immunosuppressants, avoid-populations) sit in the Contraindications gate; ER “Caution” items sit in Key Interactions.
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.	🟢	No content from ER Benefit-Modifying Factors or Risk-Modifying Factors appears in the gates or the risk tiers.
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, citations, author names or NCT identifiers; drug names listed are generic and all appear in ER lines 287–305.
1.6	The QRS does not introduce new attributions.	🟢	No source, author or organisation is named anywhere in the QRS.

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.	🟢	Measured, non-promotional register matching the ER, including the “broad but shallow evidence base” framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Tier labels, biomarker targets and cadence give an actionable frame without hype.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Protocol cells report what practitioners use rather than instructing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Statements are descriptive/passive (“evening dosing is avoided”, “repeated at four weeks”).
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “should”, or “advise” in the QRS’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person address anywhere in the sheet.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms retained only where the ER itself uses them as biomarker names or drug classes.
2.8	Information is presented in a concise and very compact manner	🟢	Gate items and tier entries are stripped to key facts; no mechanistic rationale is carried through.
2.9	It DOES NOT address the reader directly	🟢	Confirmed across header, at-a-glance, protocol, gates, cards and cadence.
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.	🟢	Framing assumes a reader running biomarkers and weighing interactions.
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.	🟢	Decoction courses, split dosing and repeated blood panels are presented without softening.
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.	🟢	Eight-marker monitoring panel and 14-day pre-procedure window assume a committed reader.
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 states measured benefits come from multi-herb formulas in disease states, which is the audience-relevant caveat.
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.	🟢	“Longevity” appears only in the canonical topic; “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.	🟢	Formal terms used throughout (“gastrointestinal upset”, “hypersensitivity reactions”, “absolute neutrophil count”); the plainer wording in at-a-glance is required by item 7.4 and mirrors ER Conclusion.

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 strings match the template exactly (lines 446, 492, 540, 570, 585, 605, 631, 635–637, 761).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Span-name diff against the template shows every variable present; the marker_#_* and qualitative_item_# placeholders are expanded to 1–8 and 1–6 respectively.
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 the footer disclaimer are byte-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 feeding 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.	🟢	Protocol labels (“Standard practitioner protocol”, “Alternative approach, Western herbal practice”, “Best time of day”) and all interaction labels match ER bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Benefit, risk and biomarker labels reproduce ER headings and table rows; interaction labels reproduce ER bold labels.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji in the file; the ER’s tier emoji and the “⚠️ Conflicted” marker were correctly dropped.
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.	🟢	Gates run two columns of eight short items; tiers are single-line lists; monitoring is eight compact rows. Content volume is within 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 at line 1.
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.	🟢	Enclosed in an HTML comment; no metadata value is repeated in the rendered 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:02" is quoted, which is required by the embedded colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: dang_shen_2026-0825-1851_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]”	🟢	Line 5: qrs_prompt_version: 26.7.02, matching 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)	🟢	Line 6: qrs_creation_date: 2026-0817-2059.
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢	Line 7: 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)	🟢	“Opus” is a single word with no version or qualifier.
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢	Line 8: 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” is nickname plus version with no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s actual name.
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 unnecessary 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., & for &)	🟢	Line 22: “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., & for &)	🟢	Line 417: “Dang Shen for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 08/17/2026, matching qrs_creation_date 2026-0817-2059.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “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 header carries only the template subline; the ER’s “Also known as” line was not carried over.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses ER lines 455–459: evidence depth, absorption/gut-bacteria route, formula-derived benefits, harm profile and interaction priority.
7.2	[at_a_glance] is no longer than 60 words	🟢	58 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each of the five clauses maps to a distinct sentence in the ER Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Uses “gut bacteria”, “blood sugar”, “immune-suppressing medication”; no acronyms or clinical-register vocabulary.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No study, author, year or sample size appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No risk ratios, confidence intervals or numeric outcomes.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All eight items come from ER lines 293 and 309–315.
8.2	[stop_items] represent the Contraindications from the ER	🟢	The seven avoid-populations plus the one interaction the ER marks “Avoid” (immunosuppressants, ER line 293).
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Eight discrete <li> elements at lines 573–580.
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.	🟢	Rationales stripped (“because no reliable human safety data exist”, “given reported anaphylaxis to a related Codonopsis species”); no dash-trailing clauses remain.
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).	🟢	“indefinitely after transplantation”, “prednisone above 7.5 mg daily”, “within 14 days” and “below 100 × 10⁹/L” all 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.	N/A	The ER uses no ranking notation in this section.
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 identifies eight such items and the section is populated accordingly.
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 come from ER lines 287–305.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Ten ER interaction bullets minus immunosuppressants (ER “Avoid”) and abiraterone (already in the Contraindications gate) = the eight items shown.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eight discrete <li> elements at lines 588–595.
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.	🟢	Only the ER bold labels are carried; every mechanism and mitigation sentence is stripped, and no dash-trailing clause remains.
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 preserved verbatim; the “Other intervention interactions” item retains a trimmed list (chemotherapy, Veratrum nigrum, checkpoint immunotherapy).
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 this section.
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 identifies ten interactions and the section is 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 lines 337, 339 and 343.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Amount and form, alternative Western preparation, and timing — the three decision-bearing aspects of the ER protocol.
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.	🟢	Nine populated fields, each traceable to the corresponding ER protocol bullet.

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	🟢	Chemotherapy-support courses, lung-function/quality-of-life measurement window, and the overall onset statement, all from ER line 387.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Chemotherapy toxicity (ER Medium, first) precedes lung function (ER Medium, second), with the overall onset statement last.
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 aspects are present 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.	🟢	Nine populated fields; the sub-lines paraphrase ER line 387 without adding claims.
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 a Time to effect bullet, so the section is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All ten entries map one-to-one to the ER benefit headings at lines 153–205.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 542–563.
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.	🟢	Headings reduced to bare outcome names; no magnitude lines or study references carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s inline glosses and all risk-ratio/confidence-interval figures are absent.
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.	🟢	The ER has no High-tier benefit; line 542 sets style="display: none" with no empty-state text.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All eight entries map one-to-one to ER risk headings at lines 225–271.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 607–625.
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.	🟢	Headings reduced to bare risk names; no incidence figures or mechanism sentences carried over.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The 1.85-per-1,000 figure, the 30–60 g range and all monograph references are absent.
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.	🟢	The ER has no High-tier risk; line 607 sets style="display: none" with no empty-state text.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows reproduce the ER biomarker table at lines 413–422.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All eight ER biomarkers present with matching optimal ranges and “why” text.
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.	🟢	Line 752 condenses ER line 411, preserving baseline, four- and twelve-week repeats, six-to-twelve-month interval and the weekly first month on interacting medication.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Items reproduce the ER qualitative marker list at lines 426–431.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers present in ER order.

Issues 17/08/2026 21:13

Pass rate 100.00%. No issues found.

Issues 17/08/2026 21:06

1. 1.2 / 1.3 — Hedging dropped in At-A-Glance: The ER Conclusion (line 457) reads “Harms look modest at customary amounts” and “The plausible interactions with clotting, blood sugar and immune-suppressing medication matter more”; [at_a_glance] (QRS lines 436-437) states “Harms are modest at customary amounts; interactions with clotting, blood sugar and immune-suppressing medication matter more”, converting two hedged ER observations into flat assertions.

Fixes 17/08/2026 21:06

1. 1.2 / 1.3 — Restored At-A-Glance hedging: Changed “Harms are modest at customary amounts; interactions with clotting…” to “Harms look modest at customary amounts; plausible interactions with clotting…”, matching the ER Conclusion’s own hedged phrasing.