Audit: QRS - Stephania tetrandra for Health & Longevity

Audit conducted on 15/08/2026 14:02 using AI4L / Opus 5

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.	🟢	Spot-checked every populated span against the ER: protocol doses (ER l.362-368), time-to-effect (ER l.418, l.272), benefit/risk headings (ER l.166-208, l.232-284), contraindications (ER l.330-336), interactions (ER l.306-326), all 13 biomarker rows and 6 qualitative markers (ER l.452-473).
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.	🟢	No cautious ER phrasing is hardened; conflicted/speculative material stays inside the Speculative tiers.
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 keep absolute wording (“at any dose”, “without specialist drug-level monitoring”); no claim is strengthened.
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.	🟢	Contraindications come from the ER’s “Populations who should avoid” list, interactions from the interaction bullets, benefits/risks from their own tiers; no cross-category relabelling.
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 identifiers, author names or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind 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.	🟢	Matches the ER’s measured, sceptical register (e.g. at-a-glance mirrors ER Conclusion l.499-501).
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert and data-driven while remaining readable; tiering and thresholds are stated without hedging.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents thresholds and protocols as evidence, not as instruction to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No directive clinical advice; the footer disclaimer is the unmodified template text.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Descriptive throughout (“Doses are taken with…” style); no “recommend”, “advise”, or “should” in document voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person address anywhere in the file (verified: no “you”/”your”).
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Terminology is plain where possible; retained clinical terms (Child-Pugh, glomerular filtration rate) are decision-gate thresholds carried verbatim from the ER.
2.8	Information is presented in a concise and very compact manner	🟢	Every item is a single compact line; explanations and mechanisms are stripped.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no direct reader address.
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 is pitched at proactive, risk-aware adults (species verification, cyclic dosing, biomarker panel).
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.	🟢	Assumes willingness to run certificates of analysis, cyclic protocols and quarterly lab panels.
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.	🟢	Not general-population framing; assumes effortful implementation.
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.	🟢	Benefit weighting foregrounds the dust-exposure indication and the substitution hazard, matching this audience’s decision needs.
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 occur.
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 terminology used throughout (“adverse”, “transaminases”, “orthostatic hypotension”).

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 headings present and unmodified: Protocol, Time to effect, Benefits, Risk & Side Effects, Monitoring, Qualitative Assessment, Contraindications, Key Interactions; tier labels High/Medium/Low/Speculative; Marker/Target/Why column headers.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	79 data-qrs-var spans present, covering every named template variable (header set, at_a_glance, action_1-3, time_1-3, stop/caution items, benefits_, risks_, marker_1-13, monitoring_cadence, qualitative_item_1-6).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Template-only spans (website=”evidence_review”, “audit”, “full_review”), CSS and structural comments are 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”	N/A	No source ER section relied on by the QRS is empty, so no empty-state phrasing applies.
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 are the ER’s bold labels verbatim: “Isolated alkaloid protocol”, “Whole-root decoction protocol”, “Best time of day” (ER l.362, l.364, l.368); interaction labels reproduce the ER bullet labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No label is paraphrased or invented; time labels are taken from the ER’s own wording (“Lung imaging and function”, “Joint symptom”, “blood pressure”).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters anywhere in the file; tiering is carried by bold labels and CSS.
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.	🟢	Each section is condensed to its minimum permitted by sections 8, 9, 12-15; no section is expanded beyond one-line items.

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 opens on line 2, immediately after <!doctype html>, before any other comment or head 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.	🟢	YAML opens at line 3 and closes at line 13 inside the 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.	🟢	Inside an HTML comment; not rendered and not repeated elsewhere 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.	🟢	All values trimmed; only duration is quoted, correctly, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: stephania_tetrandra_2026-0825-1205_Opus_ER.md (line 4) matches the actual source ER.
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.7.02 (line 5) 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-0815-1356 (line 6), correct YYYY-MMDD-HHMM form.
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 (line 7).
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 (line 8).
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)	🟢	Nickname plus version number, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: stephania_tetrandra_2026-0825-1205_Opus_QRS.html (line 9) 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.	🟢	Frontmatter values clean and consistently formatted.

#	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 `&`)	🟢	Stephania tetrandra for Health & Longevity - Quick Reference Sheet (line 22), canonical_topic entity-encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER `frontmatter`, with HTML entities encoded as needed (e.g., `&` for `&`)	🟢	header_topic = “Stephania tetrandra for Health & Longevity” (line 417).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	header_subline_date = 08/15/2026 (line 421), matching qrs_creation_date 2026-0815.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	header_subline_model = 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 carries only the template subline; no badge, AKA line, version stamp or audit date.

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 ER Conclusion (l.499-501): drug-like character, strongest indication, weaker joint evidence, dominant substitution hazard.
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 clause maps to a distinct ER Conclusion passage (ER l.499 for the first three claims, l.501 for the hazard).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms or specialist classifications; “scarring lung disease caused by inhaled stone dust” replaces silicosis, “near-identically named plant” replaces Aristolochia fangchi.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, sample sizes or p-values.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect sizes, odds ratios or confidence intervals.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	Derived from the ER’s “Populations who should avoid Stephania tetrandra” list inside Key Interactions & Contraindications (ER l.328-336).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoid-population bullets are represented, plus the P-glycoprotein-substrate bullet the ER marks an absolute contraindication (ER l.314) carried as the digoxin/tacrolimus/cyclosporine/DOAC item.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <li> elements inside the stop_items span (lines 566-586).
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.	🟢	Trailing rationales stripped (“given absent reproductive toxicology…”, “for whom no dosing or safety data exist”); no dashes or citations 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).	🟢	Thresholds and staging preserved: eGFR below 30 mL/min/1.73 m2, Child-Pugh Class B or C, transaminases above three times the upper reference limit, systolic below 100 mmHg, age under 18.
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 inside parentheses 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.	🟢	Section is populated, as required, since the ER names multiple avoid 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	🟢	Derived from the ER Key Interactions & Contraindications bullets (ER l.306-326).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All ten remaining interaction bullets present, in ER order; the narrow-margin P-glycoprotein substrate bullet is correctly excluded because it is carried as a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Ten <li> elements inside the caution_items span (lines 594-609).
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 mechanistic explanation and mitigation clause after the em-dash is stripped; only the labelled category 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).	🟢	All example drug lists preserved verbatim, including the CYP3A4 inhibitor and inducer lists and the supplement list.
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 inside parentheses 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.	🟢	Section is populated, as required, since the ER names eleven 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	🟢	Derived from the ER Therapeutic Protocol section (ER l.360-382).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	The two competing dosing routes and the dosing-time bullet are the three most actionable items in the ER protocol list.
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 names more than three actionable implementation aspects.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER `Protocol` section.	🟢	All nine action spans carry ER-derived content (60 mg three times daily, 6-on/1-off in 3-month cycles, 5-10 g decocted root within the astragalus pairing, dosing with meals).

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	🟢	Lung imaging/function, joint symptoms and blood pressure are the three time-to-effect aspects the ER supplies (ER l.418, l.272).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered High (lung fibrosis) then Medium (rheumatoid arthritis) then Low (blood pressure), matching the benefit tiers.
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 exist in the ER.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine time spans populated with ER-derived content; values 3-12 months, 4-8 weeks and within hours all trace to ER text.
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 does provide time-to-effect information.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	Derived from the ER Expected Benefits section (ER l.162-208).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four benefit tier spans present and populated (lines 540-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 headline claims only; magnitudes, mechanisms and trial counts omitted.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content carried over.
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 contain items in the ER.

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 (ER l.228-284).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four risk tier spans present and populated (lines 621-638).
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 headline risks only; magnitudes, incidence figures and mechanisms omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content carried over; the ER’s conflicted markers are dropped in line with the no-emoji rule.
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 risk tiers contain items in the ER.

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 (ER l.444-464).
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All 13 ER biomarker rows reproduced with optimal ranges and rationale verbatim, from alanine aminotransferase through urine cytology.
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 reproduces the ER’s ongoing schedule (ER l.448): liver panel and blood pressure at 4 weeks then quarterly, kidney measures every 6 months, lung function and imaging at 6 and 12 months.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Derived from the ER’s qualitative marker list in the same Monitoring section (ER l.466-473).
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All six qualitative markers reproduced verbatim in qualitative_item_1-6.

Issues 15/08/2026 14:02

Pass rate 100.00%. No issues found.