Audit: QRS - Pregnenolone for Health & Longevity

Audit conducted on 12/09/2026 04:09 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 84
Failed 0
N/A 9
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 protocol cell, gate item, tier item, marker row and cadence string traces to a named ER passage.
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. 🟢 “No independently validated target”, “unmeasured hormonal effects” and “the age-decline premise is contested” mirror the ER’s hedging.
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 stay absolute; interactions stay cautionary; no tier 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. 🟢 Stop items come only from “Populations who should avoid Pregnenolone”, caution items only from the interaction bullets, risk tiers only from Potential Risks & Side Effects.
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, author names, NCT numbers or brand names at all.
1.6 The QRS does not introduce new attributions. 🟢 No attribution appears anywhere in the sheet.

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, qualified register of the ER Conclusion is carried through verbatim in places.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Dose, timing, monitoring targets and stop thresholds give the reader actionable structure without overselling.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is stated as observed practice and measured findings, not as instruction.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperative addressed to a patient; gate and monitoring content is descriptive.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommended”, “advised” or “should” constructions in the QRS’s own voice.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronoun appears in the document.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Jargon is expanded or avoided; “prostate-specific antigen”, “sex hormone-binding globulin” and “thyroid-stimulating hormone” are spelled out rather than abbreviated.
2.8 Information is presented in a concise and very compact manner 🟢 Gate items, tier items and marker cells are trimmed to the key fact; the ER’s Context/Notes column is dropped entirely.
2.9 It DOES NOT address the reader directly 🟢 Confirmed across header, at-a-glance, protocol, gates, cards and footer.
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. 🟢 Framing assumes lab access, baseline panels and a numeric symptom score.
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. 🟢 A ten-marker hormone panel, weekly blood pressure and annual prostate-specific antigen are presented without hedging on effort.
2.12 The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort. 🟢 Demands of the monitoring and titration content exceed general-population expectations.
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 fact that no study tested undiagnosed adults — the decisive point 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. 🟢 “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)”; “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. 🟢 Route of administration is given as “Oral, once daily” (action_1_sub); no “pill”, “taken by mouth” or similar appears.

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, gate headings, tier labels and the three column headers match the template byte-for-byte.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 page_title, header_, at_a_glance, action_1–3_, time_1–3*, benefits, stop_items, caution_items, risks_, marker_#*, monitoring_cadence and qualitative_item# are all 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 carried over 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 is empty; the Risks High tier carries explanatory prose rather than an empty-state phrase, and is handled under 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. 🟢 Protocol labels (“Standard supplement protocol”, “Best time of day”, “Low dose may outperform high dose”) and all nine interaction labels are reproduced verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Marker names match the ER Biomarker column exactly, including “Prostate-specific antigen (men 40 and over)”.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 The ER’s 🟩/🟥/🟨/⚠️/⭕️ markers are all stripped; tiering is conveyed by bold labels and CSS.
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 rather than extended: the monitoring Context/Notes column is dropped, marker targets are trimmed, and tier items are reduced to bare headings.

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 value is echoed into 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: pregnenolone_2026-0912-0012_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 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-0912-0353.
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” 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]” 🟢 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” carries no trailing qualifier such as a context-window marker.
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 nine keys; 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 &) 🟢 “Pregnenolone for Health & Longevity - Quick Reference Sheet” with the ampersand correctly encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Pregnenolone for Health & Longevity”, matching the ER frontmatter canonical_topic.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0912-0353 renders as “09/12/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. 🟢 Header holds only the title and the template subline; 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 compress the Conclusion’s pathway framing, benefit list, evidence gaps and harms.
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 separate sentence of the ER Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronym or clinical-register term; “overstimulation”, “sleep disruption” and “supplement labels” are lay-transparent.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial name, year, n or p-value appears.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 “small trials” and “doses far above supplement labels” are qualitative, not statistical.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eight items come from the “Populations who should avoid Pregnenolone” list and the abiraterone bullet in that section.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All seven ER bullets are represented; the first is split into the cancer-history item and the prostate-specific antigen threshold item.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Eight <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. 🟢 No dashes or trailing clauses; the ER’s gloss “(extra beats arising in the heart’s lower chambers)” is dropped as explanatory.
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). 🟢 “(any stage)”, the 4 ng/mL and 0.75 ng/mL per year thresholds, “pending urological assessment”, “(any gestational age)” and “causing heavy bleeding” are 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 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 seven such populations, and the section is correctly populated rather than empty.
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 come from the interaction bullets of that section.
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 appear; the steroidogenesis-inhibitor bullet is correctly omitted because abiraterone is listed as a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Nine <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 corticosteroid bullet’s em-dash gloss “— steroid drugs given to damp inflammation…” is stripped; no mitigation text or citation is carried over.
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). 🟢 Every named drug list is retained, including “(diazepam, lorazepam, zolpidem)” and “(caffeine, Rhodiola rosea, tyrosine)” with the italics preserved as <em>.
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 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 correctly 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 derive from bullets in Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, timing and the dose-response caveat are the three decision-bearing bullets; the remaining bullets are background or modifiers.
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 well over three actionable aspects; 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. 🟢 “5–50 mg daily”, “Morning” and “30 mg over 200 mg” with their subs all trace to the ER bullets of the same names.

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 🟢 Craving/anxiety, chronic low back pain and psychiatric/cognitive change are the three windows named in the ER’s “Time to effect” bullet.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered High (craving), Medium (back pain), then the psychiatric/cognitive cluster, matching the ER benefit tiers.
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 names three distinct windows; 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. 🟢 “Within 2 weeks”, “4 weeks” and “8–12 weeks” with their subs are drawn from the ER’s Practical Considerations time-to-effect bullet.
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 🟢 All twelve items correspond one-to-one with the ER’s benefit headings.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans are 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 item is the bare ER heading; no Magnitude text, p-value or source is carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content remains in any benefit tier.
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 benefit tiers contain items in the ER.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All eight items correspond one-to-one with the ER’s risk headings.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans are present; risks_high is retained and hidden.
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 item is the bare ER heading; counts such as “5 versus 0” and the ⚠️ Conflicted marker are dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content remains in any risk tier.
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. 🟢 The ER states “No risk reaches High”, and risks_high carries style="display: none" with no empty-state text.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows and cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All ten rows of the ER biomarker table are present, in ER order, with Optimal Functional Range and Why Measure It mapped to Target and Why.
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. 🟢 Baseline, 8–12 weeks, 6-monthly, weekly/monthly vitals and annual prostate-specific antigen all match the ER’s ongoing-monitoring paragraph.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Taken from the ER’s “Qualitative markers worth tracking alongside the labs” list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All nine ER qualitative markers appear verbatim and in ER order.

Issues 12/09/2026 04:09

Pass rate 100.00%. No issues found.

Issues 12/09/2026 04:03

  1. 8.5 — PSA qualifier dropped: The contraindication “Men with prostate-specific antigen above 4 ng/mL or a rise over 0.75 ng/mL per year” (line 575) omits the ER’s qualifier “pending urological assessment” (ER line 333), which defines the contraindication as a deferral rather than a permanent bar.

Fixes 12/09/2026 04:03

  1. 8.5 — PSA qualifier restored: Appended the ER’s dropped qualifier to the prostate-specific antigen contraindication, changing it from “…or a rise over 0.75 ng/mL per year” to “…or a rise over 0.75 ng/mL per year, pending urological assessment”.

Issues 12/09/2026 03:58

  1. 7.2 — At-a-glance exceeds word cap: The [at_a_glance] span (lines 433–439) contains 62 words, two over the 60-word maximum.

Fixes 12/09/2026 03:58

  1. 7.2 — At-a-glance trimmed under word cap: Condensed [at_a_glance] from 62 to 59 words by dropping “Human” before “benefits” and replacing “adults without a diagnosis” with “undiagnosed adults”; all ER-supported facts retained.