Audit: QRS - Tribulus terrestris for Health & Longevity

Audit conducted on 12/08/2026 11:54 using AI4L / Grok 4

Iterations

Summary

Items	Count
Total	93
Passed	86
Failed	0
N/A	7
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.	🟢
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.	🟢
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.	🟢
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.	🟢
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”	🟢
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢
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.	🟢
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.	🟢
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.	🟢
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.	🟢

---

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”	🟢
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢
3.3	Spans that are not addressed in a checklist item are left 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 sections used by the QRS are 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.	🟢
4.3	Labels are not 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.	🟢
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.	🟢

---

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.	🟢
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.	🟢
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.	🟢
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of 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)	🟢
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)	🟢
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)	🟢
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢
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., & for &)	🟢
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢

---

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢
7.2	[at_a_glance] is no longer than 60 words	🟢
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢
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	🟢
8.2	[stop_items] represent the Contraindications from the ER	🟢
8.3	Individual [stop_items] are formatted as <li></li>	🟢
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.	🟢
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).	🟢
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	ER contraindications do not use 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.	🟢
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	🟢
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢
9.3	Individual [caution_items] are formatted as <li></li>	🟢
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.	🟢
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).	🟢
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	ER interactions do not use ranking notation
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.	🟢
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	🟢
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢
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 protocol aspects are present
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢

---

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	🟢
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢
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.	🟢
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived 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	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]	🟢
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.	🟢
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢
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.	🟢

---

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]	🟢
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.	🟢
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢
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.	🟢

---

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢
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.	🟢

---

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	🟢

Issues 12/08/2026 11:54

Pass rate 100.00%. No issues found.

Issues 12/08/2026 11:48

1. 2.15 — Colloquial medicine checks: At-a-glance uses consumer-grade “medicine checks” instead of formal clinical terminology (e.g., “review of concurrent medications”).

Fixes 12/08/2026 11:49

1. 2.15 — Formal concurrent-medication wording: Replaced colloquial at-a-glance “medicine checks” with “review of concurrent medications.”

Issues 12/08/2026 11:39

1. 7.4 — Clinical-register at-a-glance phrasing: At-a-glance uses “interaction screening”, a clinical-register phrase rather than plain language (e.g., “checking for drug interactions”).

Fixes 12/08/2026 11:41

1. 7.4 — Plain-language at-a-glance: Replaced clinical-register “interaction screening” (and tightened the surrounding clause) with plain wording: “interactions with some cholesterol medications make extract quality, medicine checks, and monitoring relevant.”

Issues 12/08/2026 11:30

1. 2.4 / 2.5 — Guidance language in at-a-glance: Closing phrase “warrant screening, quality extracts, and monitoring” implies clinical advice/guidance rather than presenting information about extract quality, interaction screening, and monitoring.

2. 9.4 — Interaction study-detail elaboration: Key Interactions item “Antiplatelet/anticoagulant context (clopidogrel in herbal-formula case context)” retains study-context wording; should keep the example drug only.

Fixes 12/08/2026 11:30

1. 2.4 / 2.5 — At-a-glance guidance language: Rewrote the closing clause from “warrant screening, quality extracts, and monitoring” to “make extract quality, interaction screening, and monitoring relevant” so the summary presents information rather than advice.

2. 9.4 — Antiplatelet interaction detail: Shortened the Key Interactions item from “Antiplatelet/anticoagulant context (clopidogrel in herbal-formula case context)” to “Antiplatelet/anticoagulant context (clopidogrel)”, dropping study-context elaboration.

Issues 12/08/2026 11:22

1. 4.2 — Interaction labels not verbatim: Key Interactions use ER **Label:** form, but the QRS paraphrases several bold labels (e.g., “Statins via CYP3A4” → “CYP3A4-metabolized statins”; “Supplements with additive metabolic effects” → “Glucose-lowering supplements”; “Other libido / PDE5-pathway agents” → “PDE5-pathway agents”).

2. 4.3 — Labels paraphrased/abbreviated: Same caution items abbreviate or invent wording vs ER labels (“Over-the-counter (OTC)” → “OTC”; antiplatelet parenthetical reworded from “clopidogrel noted in herbal-formula case context”).

Fixes 12/08/2026 11:24

1. 4.2 — Interaction labels restored: Replaced paraphrased Key Interactions labels with ER bold-label wording (e.g., “Statins via CYP3A4”, “Other libido / PDE5-pathway agents”, “Supplements with additive metabolic effects”, “Over-the-counter (OTC)…”).

2. 4.3 — Label paraphrases removed: Restored antiplatelet parenthetical to ER phrasing (“clopidogrel in herbal-formula case context”) and dropped abbreviated/invented label forms in the caution list.

Issues 12/08/2026 11:15

1. 1.1 — Unsupported metabolic onset: time_3 states metabolic markers take “About 3 months”; the ER only reports a 3-month type 2 diabetes trial duration, not an onset window for metabolic effects.

2. 2.15 — Colloquial stomach upset: At-a-glance uses consumer-grade “stomach upset” instead of formal clinical terminology such as “gastrointestinal upset”.

3. 4.2 / 4.3 — Protocol label wording: Protocol action labels “Dose” and “Form” are invented/paraphrased; ER bold labels are “Common studied range” and “Standardized extract example” (“Timing” already matches).

4. 11.1 / 11.3 / 11.4 — Extra time-to-effect slot: Only two distinct ER time-to-effect aspects are clear (sexual-function 4–12 weeks; uncommon before 2 weeks), but time_3 is filled with unsupported metabolic “About 3 months” content instead of being left empty and invisible.

Fixes 12/08/2026 11:15

1. 1.1 / 11.1 / 11.3 / 11.4 — Hide unsupported time_3: Cleared time_3 label/value/sub and set the third Time-to-effect cell to display:none, removing the unsupported “Metabolic markers / About 3 months” claim.

2. 2.15 — Formal GI phrasing: Replaced at-a-glance “stomach upset” with “gastrointestinal upset”.

3. 4.2 / 4.3 — Protocol ER labels: Changed action_1_label from “Dose” to “Common studied range” and action_3_label from “Form” to “Standardized extract example”.

Issues 12/08/2026 11:10

1. 1.3 — Strengthened onset phrasing: time_2_value uses “Rare before 2 weeks” while the ER Practical Considerations states benefits before 2 weeks are “uncommon” in controlled data.

2. 10.2 / 10.4 — Protocol duration source: action_3 (“Duration & form” / “8–12 week trial” / third-party single-ingredient wording) pulls duration and product-quality content from Risk Mitigation and Sourcing rather than the Therapeutic Protocol section required by 10.2/10.4.

Fixes 12/08/2026 11:11

1. 1.3 — Strengthened onset phrasing: Changed time_2_value from “Rare before 2 weeks” to “Uncommon before 2 weeks” to match the ER Practical Considerations wording.

2. 10.2 / 10.4 — Protocol duration source: Replaced action_3 Duration & form / 8–12 week trial / third-party wording with Form / Standardized fruit extract / Furostanol saponins multi-dose regimen content drawn from the Therapeutic Protocol section.