Audit: QRS - Bulbine natalensis to Improve Testosterone
Audit conducted on 14/09/2026 06:12 using AI4L / Opus 5
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. | 🟢 | Protocol cells, gate items, benefit/risk headings, all 12 biomarker rows and the cadence 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. | 🟢 | “Unknown in humans” (time_1_value) matches ER line 353 verbatim; “no human onset interval can be quoted” carried through in time_1_sub. |
| 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 remain absolute; speculative tiers remain speculative; no hedge added or removed. |
| 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. | 🟢 | Gate items come only from Key Interactions & Contraindications; no modifying-factor content appears in any card. |
| 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, expert names, NCT identifiers or brand names at all. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions present; ER attributions (Center for Applied Health Sciences, Examine’s Kamal Patel) were dropped rather than replaced. |
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 restrained, evidence-first register. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Presents the evidence gap and the monitoring path without alarm or exhortation. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Declarative throughout; no imperatives. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Cadence and gates are stated as facts about the evidence, not as instructions. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “should”, “recommend” or “advise” in the document’s own voice. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Jargon is limited to marker names in the Monitoring table, which are the ER’s own laboratory order names. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate items and tier lists are stripped to the key fact; subs are one to two clauses. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed — no direct 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. | 🟢 | Dose regimens, 12-marker panel and cycling-relevant cadence assume an engaged self-experimenter. |
| 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. | 🟢 | Fasted morning draws and a four-timepoint laboratory schedule are presented without apology. |
| 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. | 🟢 | Tighter-than-conventional targets (ALT under 25 U/L, eGFR above 90) are optimisation-grade, not population-grade. |
| 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 foregrounds the untested human effect and the product-composition problem — the two facts that decide use 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. | 🟢 | The string “anti-aging” does not occur in the QRS. |
| 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. | 🟢 | At-a-glance uses “oral supplement” (ER wording); no “pill”, “shot” or “taken by mouth” anywhere. |
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 headings match the template byte-for-byte (lines 445, 491, 541, 559, 575, 596, 619, 623–625, 792); populated tier labels “Medium”, “Low”, “Speculative” unchanged. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | Diff of the data-qrs-var name sets shows only the template’s repeatable marker_#_* and qualitative_item_# placeholders expanded to marker_1..12_* and qualitative_item_1..7; every other named span is present. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The three non-variable spans (website="evidence_review", website="audit", website="full_review") 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 carries empty-state phrasing; the only empty ER subsection (Expected Benefits → Low, line 144) is blank, and the tiered spans are handled under 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. | 🟢 | action_1/2/3 labels reproduce ER lines 301, 303, 311 verbatim; all 12 marker names reproduce the ER biomarker column verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Where the ER supplies a bold label it is carried through unchanged; the time-cell labels name the endpoint per section 11, which the ER’s single “Time to effect” bullet does not itself label. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji codepoints in the file; the ER’s ⭕️ and tier squares were 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. | 🟢 | Gate items, benefit and risk tiers are compressed to bare facts; the biomarker and qualitative lists are the full ER sets required by 14.2/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, immediately after the doctype on line 1 and before the template comment on line 16. |
| 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 header or footer. |
| 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 — bulbine_natalensis_testosterone_2026-0914-0400_Opus_ER.md, matching the ER frontmatter filename. |
| 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 — 26.9.11, matching 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) | 🟢 | Line 6 — 2026-0914-0607. |
| 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 — 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 — 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 on disk exactly. |
| 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 eleven keys; no stray whitespace or 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 — “Bulbine natalensis to Improve Testosterone - Quick Reference Sheet”; no characters requiring entity encoding. |
| 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 — matches ER canonical_topic exactly. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421 — 09/14/2026, from qrs_creation_date 2026-0914-0607. |
| 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 holds only the title and 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 |
🟢 | Lines 434–437 condense ER lines 424–428: what it is, what the claim rests on, the human gap, the organ signal, the product problem. |
| 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 sentence in the ER Conclusion (lines 424, 426). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “marker compounds”, “hormone levels”, “liver and kidney chemistry” are lay-legible. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | “one university group” is a generic referent; no study, year or sample size named. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numbers of any kind appear. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All nine items trace to ER lines 270–281. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | The eight “Populations who should avoid” bullets plus the TRT/hCG absolute contraindication (ER line 270) = nine items. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Lines 562–570 — nine discrete <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. | 🟢 | Rationale clauses stripped: “given the reproductive findings at higher rodent doses” and “in whom no benefit has been proposed” both removed; 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). | 🟢 | “above 3× the upper limit of normal”, “Child-Pugh Class B or C”, “below 60 mL/min/1.73 m²”, “above 4 ng/mL”, “within 14 days of scheduled surgery” all retained. |
| 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 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. |
🟢 | The ER names nine such populations/scenarios 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 nine items trace to ER lines 252–268. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Nine of the ER’s ten interaction bullets carried; the tenth (TRT/hCG, ER line 270) is correctly routed to Contraindications only. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Lines 578–586 — nine discrete <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. | 🟢 | Every “Caution.” sentence, mechanism and “Mitigation:” clause removed; only the bold label and its drug list remain. |
| 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 five named-drug parentheticals preserved in full; only the nested DHEA gloss was trimmed, with “DHEA” retained. |
| 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 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. |
🟢 | The ER names ten 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 ER Therapeutic Protocol lines 301, 303, 311. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | The two dose regimens (trial-anchored, allometric) plus the dosing schedule are the only directly executable bullets; the remainder are “no data exist” statements. |
| 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 three or more actionable aspects and 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. |
🟢 | All nine fields populated; values “650 mg daily, 28 days”, “~8 mg/kg” and “Split, morning and early afternoon” all trace to 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 | 🟢 | Human onset (ER line 353), rodent onset (ER line 353) and the 12-week durability point (ER line 379). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered from the headline human endpoint, through the rodent surrogate, to the durability horizon. |
| 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 three distinct aspects 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. | 🟢 | All nine fields populated; “Unknown in humans”, “1–7 days” and “12 weeks” all appear in 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 information (lines 353, 379), so the section is retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | The five listed items are the five ER speculative benefit headings (lines 148–166). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present at lines 543–552. |
| 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 only, semicolon-separated; doses, species, PMIDs and the ER’s “Basis is animal work only” qualifiers all dropped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheticals remain in the Benefits card. |
| 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, benefits_medium and benefits_low carry style="display: none" with empty content, matching the ER’s empty High/Medium/Low tiers. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Medium, Low and all eight Speculative items match ER headings at lines 190, 198 and 206–236. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present at lines 598–613. |
| 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 only; the ER’s Magnitude: paragraphs, percentages, P values and citations are all absent. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheticals remain in the Risks card. |
| 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 carries style="display: none" with empty content, matching the ER’s empty High tier (line 186). |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows reproduce the ER biomarker table at lines 381–394. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All 12 ER rows present, with names, optimal ranges and “Why Measure It?” text carried 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 784–785 combine the ER’s baseline requirement and the 4-week / 12-week / 6-month cadence with the fasted 8–10 a.m. draw window (ER lines 377, 379). |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Items reproduce the ER’s qualitative-marker list at lines 398–404. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All seven ER items present and verbatim. |
Issues 14/09/2026 06:12
Pass rate 100.00%. No issues found.