Audit: QRS - Enclomiphene to Improve Testosterone

Audit conducted on 08/08/2026 18:56 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 91
Passed 81
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. 🟢 Every gate item, protocol cell, tier item, marker row, and qualitative item traces to a named ER passage (ER Key Interactions & Contraindications, Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks & Side Effects, Monitoring Protocol & Defining Success, Conclusion).
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. 🟢 “Whether better numbers make men feel better is unsettled” mirrors ER line 548; “Symptomatic change, where it occurs” retains the ER hedge from line 472.
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”). 🟢 Contraindication thresholds (LH above 12 IU/L, haematocrit above 54%, AHI of 30 or more, Child-Pugh Class C, within 90 days) are carried at ER strength; no caution is upgraded or downgraded.
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 and Key Interactions both come from ER Key Interactions & Contraindications; benefits from Expected Benefits; risks from Potential Risks & Side Effects; nothing is drawn from the modifying-factor sections.
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, citations, expert names, NCT identifiers, or brand names (Androxal, EnCyzix, Empower, Strive) appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 The only attributive phrase, “Standard regimen used by leading practitioners”, is the ER’s own bold label at line 419.

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. 🟢 Neutral, evidence-first register throughout, matching the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Quantified targets and thresholds paired with plain-language framing in At-A-Glance.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Descriptive constructions (“Escalated to 25 mg daily if…”, “The only regimen tested in the controlled trials”) rather than instructions.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives; monitoring targets are presented as the ER’s functional ranges, not as orders.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No occurrence of recommend/advise/should in the QRS body.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the document.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Hormones and enzymes are written out in full (luteinizing hormone, follicle-stimulating hormone, sex hormone-binding globulin); no unexpanded acronyms.
2.8 Information is presented in a concise and very compact manner 🟢 Tier rows are single semicolon-separated lines; gate items are single clauses; marker rows are short phrases.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by full-text scan for “you”/”your”.
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. 🟢 Functional target ranges, self-monitoring cadence, and qualitative tracking items address a proactive optimizer.
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. 🟢 Twelve-marker panel, paired morning draws 2–10 days apart, and semen analysis assume a high-effort audience.
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. 🟢 Nothing is simplified toward a general-population reader; assay-level detail is retained.
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. 🟢 Unapproved status and unverified supply quality are surfaced as a High risk, which is the audience-specific signal.
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 term “anti-aging” does not appear 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. 🟢 “oral medication”, “venous blood clots”, “gynecomastia”, “haematocrit” are used; the plainer terms in At-A-Glance are the ER’s own Conclusion wording and are required by item 7.4.

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” 🟢 All fixed headings, gate headings, tier labels, and column headers match the template byte-for-byte.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All 22 distinct template variable names are present; the repeatable marker_#_* and qualitative_item_# spans are instantiated as marker_1marker_12 and qualitative_item_1qualitative_item_6.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 A normalized diff against the template shows the head, CSS block, footer disclaimer, and the non-variable spans (website="evidence_review", website="audit", website="full_review") are 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 section that feeds the QRS is empty; every tier, gate, and table has content.
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. 🟢 “Standard regimen used by leading practitioners”, “Best time of day”, “Single versus split dosing” are verbatim ER bold labels (ER lines 419, 425, 429); marker names are verbatim ER table row labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Protocol and marker labels are copied unchanged; the Time-to-Effect labels are the ER’s own subject terms from the Time to effect bullet (testosterone, semen parameters, symptomatic change).
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji present; the ER’s “⚠️ Conflicted” markers on two headings were 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. 🟢 Content is at the compressed limit permitted by the mandatory items: single-line tier rows, parentheticals stripped from monitoring targets, CYP3A4 example lists trimmed, and At-A-Glance at 54 words.

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. 🟢 The comment opens at line 2, immediately after the doctype, and closes at line 14 before the template comment and <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 and closing --- at line 13; the descriptive text on line 2 precedes the opening delimiter.
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. 🟢 It sits inside an HTML comment and no element echoes its values.
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:02" is quoted, which is required because the value contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: enclomiphene_testosterone_2026-0808-1531_Opus_ER.md at line 4.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 qrs_prompt_version: 26.7.02, matching the version badge 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) 🟢 qrs_creation_date: 2026-0808-1834 in the required format.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 qrs_creator_ai_nickname: Opus at line 7.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 “Opus” is a single word with no version or qualifier.
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 qrs_creator_ai_fullname: Opus 5 at line 8.
5.11 The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) 🟢 “Opus 5” is nickname plus version with no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: enclomiphene_testosterone_2026-0808-1531_Opus_QRS.html matches the file on disk.
5.13 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 All eight remaining values are unquoted and untrimmed of any stray whitespace.

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 &) 🟢 “Enclomiphene to Improve Testosterone - Quick Reference Sheet”; no characters require 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 &) 🟢 “Enclomiphene to Improve Testosterone”, matching ER frontmatter line 8.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0808-1834 renders as 08/08/2026.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5”, matching the frontmatter value.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 The subline carries only the creation date, the AI4L link, and the model name; the ER’s “Also known as” line 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 🟢 Four sentences mapping to the four paragraphs of the ER Conclusion (mechanism and fertility, stability, unsettled symptom benefit, supply quality).
7.2 [at_a_glance] is no longer than 60 words 🟢 54 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Traceable to ER lines 546 (mechanism, sperm production, steadier levels), 548 (unsettled symptom benefit), and 550 (no approved product, variable quality).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Uses “estrogen’s brake on the brain’s hormone signals” and “testosterone gels”; no acronyms, no drug-class names, no register-heavy clinical words.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, sample sizes, or p-values.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numbers of any kind appear in the At-A-Glance text.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All nine items come from that section: the “Exogenous testosterone” bullet (ER line 377) and the “Populations who should avoid this intervention” bullet (ER line 395).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All eight populations from ER line 395 plus the absolute exogenous-testosterone antagonism are represented; nothing is omitted.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Nine discrete <li> elements inside the stop_items 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. 🟢 Each item is a single noun phrase; the ER’s rationale clauses (“in whom the drug cannot work”, “given hepatic metabolism and biliary excretion”, “for whom there is no evidence base”) are all stripped, and no dash-led trailing clause remains.
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). 🟢 Preserved: “above 12 IU/L with low testosterone”, “especially within 90 days”, “Child-Pugh Class C”, “above 54%”, “apnoea-hypopnoea index of 30 or more”, and the dosage-form list for exogenous testosterone.
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 in words (“above 12 IU/L”, “above 54%”).
8.7 If no [stop_items] are present the section is left empty N/A Nine stop_items are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eight items map one-to-one to ER bullets at lines 379–393.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All eight caution-grade ER bullets are carried; the two absolute bullets (exogenous testosterone, populations who should avoid) are correctly routed to Contraindications instead.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eight discrete <li> elements inside the caution_items 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. 🟢 The ER’s “caution —”, “avoid in routine use —”, “monitor —” prefixes and all mitigation clauses are stripped; only the agent or agent class remains.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). 🟢 Drug lists are preserved for CYP2D6 inhibitors (complete), aromatase inhibitors (complete), and the additive supplements (complete); the CYP3A4 lists are trimmed to representative members rather than dropped, as the one-page budget permits.
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; all parenthetical content is plain comma-separated drug lists.
9.7 If no [caution_items] are present the section is left empty N/A Eight caution_items are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells come from ER Therapeutic Protocol lines 419, 425, and 429.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose and titration, time of day, and single-versus-split dosing are the three executable decisions; the remaining bullets are comparative, contextual, or population-modifying rather than 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 Three distinct actionable aspects exist 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 are populated: “12.5 mg once daily” with the escalation rule, “Morning” with the food and trough-placement note, and “Single daily dose” with the tested-regimen note.

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 🟢 Testosterone, sperm production, and symptoms are the three distinct clocks given in the ER Time to effect bullet at line 472.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Testosterone (High-tier benefit) first, sperm production (High-tier benefit) second, symptoms (Low-tier, conflicted benefit) 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 Three distinct time-to-effect aspects exist 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. 🟢 “2 weeks” with the four-week steady state above 400 ng/dL, “3 months” with the 72–90 day spermatogenic cycle, and “Several weeks later” with the ER’s “where it occurs” hedge.
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 an explicit “Time to effect” bullet, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All eleven items correspond one-to-one to the eleven ER benefit headings across the four tiers.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated.
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 tier is a semicolon-separated list of the ER headings alone; none of the ER’s Magnitude: lines, confidence intervals, or caveats are carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear anywhere in the four benefit rows.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four tiers have items in the ER, 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 fourteen items correspond one-to-one to the fourteen ER risk headings across the four tiers.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated.
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 tier is a semicolon-separated list of the ER headings alone; the ER’s incidence figures (7.1%, 4.5%, 2.2%, 0.4%) and mechanistic commentary are omitted.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear anywhere in the four risk rows.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four tiers have items in the ER, 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 (ER lines 500–511).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All twelve ER rows are present in ER order, with marker names, optimal functional ranges, and “Why Measure It?” text carried over.
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. 🟢 Carries the paired baseline draws 2–10 days apart, the 4–6 week recheck and post-dose-change recheck, 3 and 6 months, every 6–12 months thereafter, and semen analysis at 3–6 months (ER lines 494 and 496).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All six items come from the qualitative-marker list at ER lines 515–520.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six are present in ER order, with the ER’s trailing rationale clauses trimmed.

Issues 08/08/2026 18:56

Pass rate 100.00%. No issues found.

Issues 08/08/2026 18:50

  1. 2.15 — Consumer-grade term for dosage form: at_a_glance (line 433) says levels are “steadier than with skin gels”, while the QRS’s own benefits_medium span (line 525) uses the formal “topical testosterone” for the same comparator.

Fixes 08/08/2026 18:50

  1. 2.15 — Consumer-grade term for dosage form: In at_a_glance (line 433) replaced “skin gels” with “testosterone gels”, aligning the At-A-Glance comparator with the formal register used by the QRS’s own benefits_medium span while keeping the span at 54 words.

Issues 08/08/2026 18:42

  1. 1.3 — Hedge dropped from time-to-effect: [time_1_sub] (line 489) states “steady state above 400 ng/dL by four weeks”, while ER line 472 hedges it as “a steady state above 400 ng/dL is typically reached by four weeks”; removing “typically” strengthens the claim.
  2. 4.5 — Content exceeds one A4 page: The sheet renders to roughly twice the ~1030px usable A4 height; the two gate lists (~15 and ~17 wrapped lines), the three-line protocol and time-to-effect sub-lines, and the three-line monitoring cadence are the condensable surfaces.

Fixes 08/08/2026 18:42

  1. 1.3 — Hedge restored in time-to-effect: [time_1_sub] changed from “steady state above 400 ng/dL by four weeks” to “steady state typically above 400 ng/dL by four weeks”, matching the ER’s own hedged wording.
  2. 4.5 — Protocol and time-to-effect sub-lines condensed: [action_1_sub] shortened to “Escalated to 25 mg daily if four-week morning testosterone is inadequate”, [action_2_sub] to “…in the evening, not the working day”, and [time_2_sub] to “One spermatogenic cycle is roughly 72–90 days”.
  3. 4.5 — Monitoring cadence condensed: Cadence rewritten from 240 to 184 characters, retaining the baseline two-draw rule, the 4–6 week, 3-month, 6-month, and 6–12 month recheck points, and the 3–6 month semen analysis.
  4. 4.5 — Key Interactions items trimmed: CYP3A4 and supplement-interaction example lists reduced to representative agents per the “shortened or trimmed where needed to fit the one-page budget” allowance, collapsing each item from three wrapped lines to two.