Audit: QRS - Tribulus terrestris for Health & Longevity

Audit conducted on 12/08/2026 05:23 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. 🟢 Protocol cells trace to ER lines 362/368/374; time cells to ER lines 417 and 157; benefits/risks to ER benefit and risk headings; gates to ER lines 307–340; monitoring table and cadence to ER lines 447–462.
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. 🟢 marker_12_target carries the ER’s “No established functional target; track change from the individual’s own baseline” verbatim.
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 retain absolute framing; “Higher total testosterone in low-androgen groups” keeps the population restriction rather than generalising.
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. 🟢 Both gates draw only from ER Key Interactions & Contraindications; no Benefit- or Risk-Modifying Factor content appears.
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 (Tribestan, Sopharma, Herbarium) appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind are present.

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. 🟢 Sober, sceptical register of the ER Conclusion is carried through, including the manufacturer-funding caveat.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Quantified targets and thresholds throughout, with plain-language framing in At-A-Glance.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is stated as observed trial practice, not as instruction to the reader.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No “recommend”, “advise”, “consult”, “should” or “must” appears in the QRS.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Cadence and protocol cells describe trial regimens rather than prescribing them.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns occur anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Abbreviations are expanded on first use in the Monitoring table (SHBG, LH, ALT/AST, eGFR, PSA, HbA1c, CK); remaining technical terms are ER-verbatim gate labels.
2.8 Information is presented in a concise and very compact manner 🟢 Gate and tier items are reduced to a key fact plus qualifier; no prose paragraphs outside At-A-Glance and Cadence.
2.9 It DOES NOT address the reader directly 🟢 Confirmed — no direct address anywhere in the document.
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. 🟢 Twelve-marker panel, functional ranges and interaction list assume a proactive, risk-aware reader.
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. 🟢 Thrice-daily dosing for 12 weeks and repeated lab panels are presented without hedging on inconvenience.
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. 🟢 Functional (not conventional) reference ranges and a full baseline panel place it beyond general-population content.
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 leads with the failure of the testosterone claim, the signal most relevant to this audience’s likely reason for interest.
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. 🟢 The string “anti-aging” does not occur; the title uses “Health & Longevity”.
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. 🟢 “tablets”, “extract”, “gastrointestinal intolerance”, “rhabdomyolysis”, “priapism” — clinical register maintained outside the deliberately plain At-A-Glance.

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 verified verbatim at lines 446, 492, 541, 571, 595, 625, 653, 657–659, 849 and in the four tier <strong> labels of Benefits and Risks.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variables present; the repeatable marker_#_* and qualitative_item_# spans are instantiated as marker_1–12 and qualitative_item_1–7.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 A structural diff against [qrs_template] shows no change outside the variable spans — CSS, wrapper markup, website= spans, footer disclaimer and the template’s own comments are byte-identical in content.

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.
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. 🟢 “Standardized-extract protocol”, “Women’s protocol”, “Split versus single dose” and all twelve interaction labels reproduce the ER bold labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Time-to-effect cell labels are the only derived labels, and no ER bold label exists for those sub-facts.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji characters occur in the file; the ER’s “⚠️ Conflicted” markers are 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. 🟢 Template page geometry is untouched; every section is condensed to key facts with rationale, citations and parentheticals stripped, subject to the completeness mandates of 8.2, 9.2, 14.2 and 15.2.

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; it is the first element 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. 🟢 Enclosed in an HTML comment; no metadata value is repeated in the 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:03" is quoted, and it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: tribulus_terrestris_2026-0812-0206_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 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) 🟢 Line 6: qrs_creation_date: 2026-0812-0459.
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” — 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]” 🟢 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” — nickname plus version, 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 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. 🟢 Re-verified across all eight fields; 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., &amp; for &) 🟢 Line 22: “Tribulus terrestris 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 &) 🟢 Line 417: “Tribulus terrestris for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “08/12/2026”, matching qrs_creation_date 2026-0812-0459.
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. 🟢 Header contains only the title and the template subline; the ER’s “Also known as” list is 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 🟢 Covers the failed hormone claim, what does hold up, the timeframe, the trial-quality caveat and the product-quality caveat — all from ER lines 492–496.
7.2 [at_a_glance] is no longer than 60 words 🟢 59 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct Conclusion sentence at ER lines 492, 494 and 496.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “hormone levels”, “blood flow”, “sperm quality” used in place of clinical terms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, sample sizes or p-values appear.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numeric outcome data appear; only the qualitative “modest improvement”.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eight items trace to the “Populations who should avoid Tribulus terrestris” list at ER lines 333–340.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All eight ER avoid-populations are present, none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Lines 574–590: eight discrete <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. 🟢 Rationales stripped, e.g. ER “(no human safety data…)” and “, given documented product contamination” do not appear; no trailing dash clauses.
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). 🟢 “at any stage”, “above 4 ng/mL”, “Child-Pugh Class B or C”, “above twice the upper reference limit”, “below 30 mL/min/1.73 m²” and “under 18” 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 inside parentheses in this section; thresholds are written out as “above”/”below”.
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 names eight such populations and the section is correspondingly populated.
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 twelve items trace to the bulleted interaction list at ER lines 307–329.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All twelve ER interaction bullets present; tacrolimus and cyclosporine are correctly withheld from item 2 because transplant immunosuppressants are already a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Lines 598–615: twelve discrete <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. 🟢 Each item is label plus example-drug parenthetical only; the ER’s “Caution.”/”Monitor.” verdicts and mitigation sentences are all 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). 🟢 Ten of twelve items carry their ER drug list verbatim; the PDE5 and CYP3A4-substrate lists are trimmed but retain named examples.
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 parentheticals are plain comma-separated drug lists with no 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. 🟢 The ER names twelve interactions and the section is correspondingly 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 trace to the ER Therapeutic Protocol bullets at lines 362, 368 and 374.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The trial-validated dosing regimen, the female regimen, and dose splitting — the three bullets that determine what is actually taken and how.
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 Therapeutic Protocol section contains twelve bullets; 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 of nine cells populated; labels are ER bold labels and values/subs restate ER dose, standardization, duration and timing.

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 🟢 Erectile function, desire in women and semen parameters — the three benefit domains for which the ER states a timeframe.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Erectile function (High tier) first, then the two Medium-tier benefits in the ER’s own order.
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 at least three distinct time-to-effect 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. 🟢 Nine of nine cells populated from ER lines 417 (30/90 days, 12 weeks, nothing inside 2 weeks) and 157 (one to three months in women).
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, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All ten benefit entries correspond one-to-one with the ER Expected Benefits sub-headings at lines 147–207.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated at lines 543–564, tier-matched to the ER.
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. 🟢 Each entry is the ER sub-heading only; no Magnitude figures, mechanisms or trial references carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any benefits entry; the ER’s “⚠️ Conflicted” markers are also dropped.
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 The ER populates all four benefit tiers, so no span needs hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All nine risk entries correspond one-to-one with the ER risk sub-headings at lines 233–287.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated at lines 627–647, tier-matched to the ER.
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. 🟢 Each entry is the ER sub-heading only; no bilirubin/creatinine peaks, case ages or incidence notes carried over.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 ER “Priapism (Prolonged Painful Erection)” reduced to “priapism”; no parentheses remain in any risks entry.
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 The ER populates all four risk tiers, so no span needs hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 The table reproduces the ER Monitoring Protocol & Defining Success biomarker table at lines 449–462.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All twelve ER biomarkers present in ER order, with Optimal Functional Range and Why Measure It? carried across 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. 🟢 Lines 838–843 reproduce the ER cadence of line 447: baseline, 4 weeks, 12 weeks, every 6 months, plus the immediate re-test trigger.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All seven items trace to the “Qualitative markers worth tracking alongside the labs” list at ER lines 466–472.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Seven of seven ER qualitative markers present in ER order, none added.

Issues 12/08/2026 05:23

Pass rate 100.00%. No issues found.

Issues 12/08/2026 05:15

  1. 2.15 — Colloquial term for gut irritation: [action_3_sub] (QRS line 486) says the split dose “spreads the saponin load that irritates the gut”, replacing the ER’s formal “causes gastrointestinal irritation” (ER line 374) with consumer-grade wording in the document’s own voice.

Fixes 12/08/2026 05:15

  1. 2.15 — Colloquial term for gut irritation: Changed [action_3_sub] from “spreads the saponin load that irritates the gut” to “spreads the saponin load that causes gastrointestinal irritation”, matching the ER’s formal wording.

Issues 12/08/2026 05:07

  1. 1.1 / 1.3 — Unqualified testosterone claim: [at_a_glance] (line 434) states the extract “does not raise hormone levels” without the ER’s population scope (“across controlled studies in healthy and athletic men, hormone levels … are unchanged”), which strengthens the ER claim and contradicts the QRS’s own Benefits line “Higher total testosterone in low-androgen groups” (line 554).

Fixes 12/08/2026 05:07

  1. 1.1 / 1.3 — Unqualified testosterone claim: In [at_a_glance], “does not raise hormone levels” was changed to “does not raise already-normal hormone levels”, restoring the ER’s population scope and removing the contradiction with the Benefits line “Higher total testosterone in low-androgen groups”. The section remains within the 60-word limit at 59 words.