Audit: QRS - Fadogia agrestis to Improve Testosterone

Audit conducted on 14/09/2026 06:06 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 85
Failed 0
N/A 8
Pass Rate 100.00%
  • Total = Passed + Failed + N/A
  • Pass Rate = Passed / (Passed + Failed) × 100
  • N/A items are excluded from the pass rate calculation

1. General Rules

# Description Result Comments
1.1 Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. 🟢 Spot-checked every populated span against the ER: protocol doses (ER 286-292), time-to-effect (ER 149, 341), benefit and risk headings (ER 143-165, 197-219), gates (ER 237-262), all 12 biomarkers and cadence (ER 365-380), qualitative markers (ER 384-388). All literally supported.
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. 🟢 Cautious ER phrasing carried through verbatim: “no human timeline exists”, “no human sexual-function trial exists”, “No human data on dose timing exist”, “The benefit remains a hypothesis”.
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”). 🟢 No strengthening or softening detected; the speculative tier and rodent-only framing are preserved on every surface.
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 “Populations who should avoid” list, Key Interactions from the ER interaction bullets, benefits and risks from their own ER sections. 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. 🟢 The QRS contains no PMIDs, study citations, expert names, NCT identifiers or brand names.
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 sober, evidence-limited register.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert, objective and data-driven; the negative weighting is the ER’s own and is stated without alarm.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents thresholds and panels as information, not as orders.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperative or prescriptive constructions; the footer disclaimer is template text.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommend”, “advise” or “you should” constructions anywhere in the file.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns present (verified across the whole file).
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language throughout; technical marker names carry their ER expansions (LH, FSH, SHBG, GGT, PSA, MDA).
2.8 Information is presented in a concise and very compact manner 🟢 Every cell is a compressed phrase; no narrative prose outside the 56-word lede.
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. 🟢 Content assumes a reader running baseline panels, cycling and sourcing by certificate of analysis.
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. 🟢 The 12-marker panel and fixed cadence presume willingness to follow an effortful protocol.
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 pitched at the general population.
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. 🟢 Risk-benefit weighting mirrors the ER: unproven benefit set against rodent organ signals and product variability.
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 appear.
2.15 The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “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. 🟢 Formal register throughout; “dose” is used where the ER said “capsule” in the cadence line.

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” 🟢 Verified against the template: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, tier labels and “Marker”/”Target”/”Why” headers are all byte-identical.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 38 template variable names are present; marker_#* is expanded to marker_1..marker_12 and qualitative_item# to items 1-5, as intended.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Every span in the file is addressed by a checklist item. The non-variable template elements (website=”evidence_review”, website=”audit”, website=”full_review”, footer disclaimer) and the entire inline stylesheet are unchanged from 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 mapped to a QRS variable is empty while carrying an ER empty-state phrasing. The empty benefit and risk tiers are governed by the more specific items 12.5 and 13.5, which mandate display:none rather than empty-state text.
4.2 Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. 🟢 Protocol labels “Standard dose”, “Conservative dose anchored to the animal data” and “Time of day” are the ER’s bold labels verbatim; gate items reuse the ER’s bold interaction labels verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Biomarker names, protocol labels and tier labels are all verbatim; no invented labels.
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 (verified by codepoint scan); the ER’s tier and conflict emoji were correctly stripped.
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. 🟢 Every section is condensed to phrase-level content - drug lists trimmed to three examples, benefit and risk tiers collapsed to single comma-separated lines, marker rationales kept to one clause.

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: the metadata comment is the first element after <!doctype html>.
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; the preceding “QRS - Metadata” text sits outside the block.
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; not echoed by any visible element.
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: “00:04” is quoted, correctly, because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: fadogia_agrestis_testosterone_2026-0914-0450_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.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: qrs_creation_date: 2026-0914-0600, 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]” 🟢 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) 🟢 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) 🟢 Nickname plus version number, 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. 🟢 Confirmed - see 5.4.

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: “Fadogia agrestis to Improve Testosterone - Quick Reference Sheet”; the canonical_topic contains no characters needing entity encoding.
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 matches the 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, the correct MM/DD/YYYY rendering of 2026-0914-0600.
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 carries only the title and the template subline; no badge, AKA line or variant marker, despite the ER listing three alternate names.

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 (lines 408-414) into identity, evidence state, safety signal, product variability and verdict.
7.2 [at_a_glance] is no longer than 60 words 🟢 56 words, under the 60-word cap.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each of the five statements maps to a distinct Conclusion passage: ER 408 (shrub, animal-only), 408 (no human trial), 410 (organ strain), 412 (product variability), 414 (hypothesis).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; plain terms used throughout (“animal work”, “cellular strain”, “published trial”).
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years or sample sizes.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from the ER “Populations who should avoid Fadogia agrestis” list inside Key Interactions & Contraindications (ER 253-262).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All eight ER avoid-population bullets are present, in ER order.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Eight <li> elements inside the stop_items span, lines 567-574.
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 stripped where the ER carried it, e.g. “Men actively pursuing conception, given the rodent testicular findings” reduced to “Men actively pursuing conception”.
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 preserved: 1.5x upper reference limit, eGFR below 60 mL/min/1.73 m2, PSA above 4 ng/mL, haematocrit above 52%, 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. 🟢 The section is populated, and the ER does identify avoid-populations, so the constraint holds.
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 🟢 Drawn from the ER Key Interactions & Contraindications bullets (ER 237-251).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All eight ER interaction bullets are present, in ER order; none duplicates a contraindication entry.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eight <li> elements inside the caution_items span, lines 582-589.
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. 🟢 All mechanistic rationale and mitigation text stripped; each item is the ER bold label plus its example list.
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). 🟢 Example drug lists preserved and trimmed to three names each per the one-page budget; none 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 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. 🟢 The section is populated, and the ER does identify interactions, so the constraint holds.
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 🟢 Drawn from the ER Therapeutic Protocol section (ER 284-306).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard dose, conservative dose anchored to the animal data, and time of day are the three actionable bullets in that section; the remainder (half-life unknown, no female protocol, no pharmacogenetic guidance) are non-actionable.
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 at least three distinct actionable aspects, so 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 action fields carry ER-derived content; values 300-600 mg daily, ~200 mg and Morning all trace to ER 286, 288 and 292.

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 🟢 Serum testosterone rise (ER 341), sexual motivation and performance (ER 149) and the eight-week follow-up panel (ER 341) are the only time-to-effect statements in the ER.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered to match the ER’s own benefit ranking within the Speculative tier: elevated serum testosterone first, sexual motivation second, with the monitoring milestone last.
11.3 If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A The ER supplies three distinct time-to-effect aspects, so 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 time fields carry ER-derived content with the rodent-only caveat attached to each.
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, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Drawn from the ER Expected Benefits section (ER 127-165).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present at lines 539-557.
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. 🟢 The six items are the ER’s H4 benefit headings reduced to bare noun phrases, with no bases, magnitudes or citations.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 The ER headings carry no parentheses; the conflict and not-central markers were correctly 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. 🟢 benefits_high, benefits_medium and benefits_low all carry style=”display: none” with an HTML comment recording the ER basis; no empty-state text is rendered.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Drawn from the ER Potential Risks & Side Effects section (ER 181-219).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present at lines 601-619.
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. 🟢 The six items are the ER’s H4 risk headings reduced to bare noun phrases, with no net statements or study detail.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 The parenthetical in the ER heading “Erythrocytosis (Thickened Blood)” is stripped, leaving “erythrocytosis”.
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, risks_medium and risks_low all carry style=”display: none” with an HTML comment recording the ER basis.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Drawn from the ER Monitoring Protocol & Defining Success section (ER 363-380).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 12 rows of the ER biomarker table are present with names, targets and rationales matching the ER 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. 🟢 Populated at lines 798-802 from ER 365: baseline fasting early morning, week 4, each cycle end, then every three to six months beyond three cycles, with hormones redrawn at the same hour.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Drawn from the ER qualitative markers list (ER 382-388).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers are present verbatim as qualitative_item_1 through qualitative_item_5.

Issues 14/09/2026 06:06

Pass rate 100.00%. No issues found.