Audit: QRS - Mucuna pruriens for Health & Longevity

Audit conducted on 20/08/2026 01:48 using AI4L / Opus 5

Iterations

Summary

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

1. General Rules

# Description Result Comments
1.1 Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. 🟢 Every populated span traces to ER text: protocol cells to ER lines 369/377/381, benefits to the ER Expected Benefits headings, risks to the Potential Risks & Side Effects headings, gates to lines 310-343, monitoring table to lines 454-463, cadence to line 452, qualitative items to lines 467-472.
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. 🟢 “without a placebo” (at_a_glance) and “with no placebo group” (time_3_sub) mirror ER lines 494 and 176; “Speculative” tiers carried over unchanged.
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 strength preserved, e.g. ER line 340 “unless the total dose is being managed by the prescribing neurologist” → “outside neurologist supervision”; selective MAO-B inhibitors remain a caution, non-selective MAOIs remain a contraindication.
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 drawn only from the ER Key Interactions & Contraindications section; no Benefit-Modifying Factors or Risk-Modifying Factors content appears in the gates.
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, NCT IDs or expert names anywhere in the QRS; the ER’s brand mentions (DopaBean, Nutricost, NOW Foods) are correctly absent. Generic drug names in the gates all appear in ER lines 310-332 for the same facts.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind in the QRS body.

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. 🟢 Flat, declarative, evidence-first register matching the ER throughout.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Quantified targets and dose ranges alongside plain-language framing; no alarmism, no hype.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Facts are stated, not directed; no imperatives in the document’s own voice.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No “recommend”, “should”, “must”, “advise” anywhere in the body; the only modal, “is best taken before 4 p.m.”, is verbatim ER line 377.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 All cells are descriptive statements of what the ER reports.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person or first-person-plural pronouns present.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Retained technical terms (dyskinesia, orthostatic, Child-Pugh Class C) are load-bearing decision-gate qualifiers required by items 8.5/9.5; “pyridoxine (vitamin B6)” is glossed as in the ER.
2.8 Information is presented in a concise and very compact manner 🟢 A 499-line ER reduced to roughly 5,500 characters of sheet text with all magnitudes, citations and rationale stripped.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by full-file scan for second-person address; none found.
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. 🟢 Sheet assumes lab access, batch-level product scrutiny and self-tracking.
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. 🟢 Split dosing, eight-marker panel and a staged cadence with batch-triggered resets all assume high compliance.
2.12 The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort. 🟢 Functional biomarker targets tighter than conventional lab ranges; not general-population framing.
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 label unreliability and the twelve-month evidence ceiling, the two facts that matter most to a self-directed user.
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. 🟢 No occurrence of “anti-aging” or “antiaging” in the file.
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. 🟢 “myocardial infarction”, “peptic ulcer disease”, “orthostatic”, “glycated haemoglobin” used in the body; the single consumer-register phrase “pharmacy tablet” is verbatim ER line 492 inside the plain-language At-A-Glance.

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” 🟢 All fifteen fixed strings byte-identical to the template.
3.2 All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variable names present; the repeatable marker_#_* and qualitative_item_# patterns are expanded to 8 marker rows and 6 qualitative items. No template span dropped.
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 unchanged; a structural diff against the template shows no edits outside variable regions.

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 feeding the QRS is empty; every tier, gate and monitoring row has source 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. 🟢 action_1_label “Whole roasted seed powder (the trial-validated form)”, action_2_label “Split versus single dose”, action_3_label “Best time of day” are verbatim ER bold labels from lines 369, 381, 377.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Marker names verbatim from the ER biomarker table (lines 456-463); time labels taken from the ER’s own wording at lines 424 and 176.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji in the file; the ER’s “⚠️ Conflicted” marker on the dyskinesia risk is 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. 🟢 Every section is condensed rather than carried over: benefit and risk tiers reduced to bare ER headings, gate items stripped of rationale and glosses, monitoring rows reduced to marker/target/why with the ER’s Context/Notes column dropped entirely.

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 and before the template comment at 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; the preamble text on line 2 sits before 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. 🟢 Enclosed in an HTML comment; none of its values appear in the rendered 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, 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: mucuna_pruriens_2026-0825-2346_Opus_ER.md, matching the ER’s own filename field.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 Line 5: qrs_prompt_version: 26.7.02, matching 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-0820-0132, correct format.
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” = nickname plus version, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9: qrs_filename: mucuna_pruriens_2026-0825-2346_Opus_QRS.html, matching 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 nine keys re-checked; no stray whitespace and no unnecessary quoting.

6. Page Title & Header

# Description Result Comments
6.1 [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., &amp; for &) 🟢 Line 22: “Mucuna pruriens for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic with the ampersand 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 &) 🟢 Line 417: “Mucuna pruriens for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “08/20/2026”, the correct reformat of 2026-0820-0132.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: “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” list is not carried over.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Compresses all five Conclusion paragraphs (ER lines 492-498) into evidence strength, evidence provenance, leading harms and the evidence ceiling.
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. 🟢 Seven claims map to ER lines 492, 494, 494, 496, 496, 496 and 498 respectively.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “active substance”, “movement disorders”, “roasted seed powder”, “labels are unreliable” are all non-specialist wording.
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 numbers other than “twelve months”, a follow-up horizon rather than an effect size.

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 310-343.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All eight bullets of the ER’s “Populations who should avoid Mucuna pruriens” list are present, plus the two absolute contraindications from lines 310 and 312 (levodopa products, non-selective MAOIs).
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Nine <li> elements inside the stop_items span, lines 569-588.
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. 🟢 Every ER “because…” / “where…” / “carried over from…” clause stripped (e.g. ER line 339 “Narrow-angle glaucoma, where dopaminergic agents can raise intraocular pressure” → “Narrow-angle glaucoma”); 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). 🟢 “Child-Pugh Class C”, “below 30 mL/min/1.73 m²” and “within 90 days” all preserved; only the ER’s explanatory glosses inside those parens were trimmed.
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’s Key Interactions & Contraindications section uses no ranking notation inside parentheses.
8.7 The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision. 🟢 The ER names eight avoidance populations plus two absolute contraindications, 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. <!– empty: ER names no population that should avoid the intervention –> 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 eleven items trace to ER lines 312-332.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All ten ER caution bullets plus the selective MAO-B carve-out from line 312 are present; the two absolute contraindications correctly appear only in the Contraindications gate.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Eleven <li> elements inside the caution_items span, lines 596-616.
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 mechanism and mitigation sentences dropped (e.g. ER line 320’s “Iron chelates levodopa… A two-hour separation resolves it” → the bare item); the ER’s “Other interventions —” dash prefix on line 332 is correctly removed.
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 ER example-drug list preserved verbatim (selegiline/rasagiline, haloperidol/risperidone/metoclopramide/prochlorperazine, metformin/glipizide/insulin, and the rest).
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 ER lists twelve interaction bullets 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. <!– empty: ER names no interaction that changes how the intervention is used –> 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 action sets come from the ER Therapeutic Protocol bullets at lines 369, 381 and 377.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Form and dose, dose splitting, and timing — the three bullets that determine what is actually taken, in what fractions, and when; the remaining nine bullets are modifiers rather than implementation steps.
10.3 If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A The ER Therapeutic Protocol section carries twelve bullets, well above three.
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 spans populated; no placeholder text remains.

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 🟢 Motor/alertness onset and hormonal/semen timing from ER line 424, plus cortisol and state anxiety at three months from ER line 176.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered High (motor control), Medium (semen and hormones), Low (cortisol), matching the ER’s 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 Three distinct time-to-effect aspects are present in the ER.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All nine time spans populated; time_3_sub correctly carries the ER’s “no placebo group” caveat.
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 at line 424, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All ten benefit items map one-to-one onto the ER’s H4 benefit headings, lines 158-208.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated, lines 539-559.
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. 🟢 Every ER Magnitude: line dropped (688% concentration rise, 25-81% cortisol fall, SMD −18.36); items reduced to the ER heading text alone.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any benefits span.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> 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 carry items in the ER, so no span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All ten risk items map one-to-one onto the ER’s H4 risk headings, lines 232-292.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated, lines 628-652.
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. 🟢 Every ER Magnitude: line dropped (4 of 14 discontinuations, 56% vs 37.5% adverse events, 0-241 mg per serving, SMD 0.97); items reduced to the ER heading text alone.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses remain in any risks span.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four risk tiers carry items in the ER, so no span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Table rows drawn from the ER Monitoring Protocol & Defining Success biomarker table, lines 454-463.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight ER biomarkers present with matching targets and “Why Measure It?” text: prolactin, total and free testosterone, semen analysis, morning cortisol, fasting glucose and glycated haemoglobin, seated and standing blood pressure, metabolic panel and complete blood count, homocysteine.
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 786-791 carry the full ER cadence from line 452, including the batch-change reset of the two-week check.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Items taken from the ER’s qualitative-marker list at lines 467-472.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER qualitative markers present and in ER order: morning drive, afternoon slump, sleep onset and awakenings, nausea and appetite, libido and refractory period, involuntary movement and compulsive behaviour.

Issues 20/08/2026 01:48

Pass rate 100.00%. No issues found.

Issues 20/08/2026 01:40

  1. 2.15 — Colloquial verb in at-a-glance: [at_a_glance] (line 436) reads “matched or beat standard preparations”, using the colloquial “beat” where the ER’s own conclusion (line 494) uses the formal “matched or outperformed”.

Fixes 20/08/2026 01:40

  1. 2.15 — Colloquial verb in at-a-glance: Replaced “matched or beat standard preparations” with “matched or outperformed standard preparations” in [at_a_glance], restoring the ER’s formal wording; the section remains at 59 words.