Audit: QRS - Mucuna pruriens for Health & Longevity
Audit conducted on 21/10/2026 05:00 using AI4L + evidence-mcp / GPT 6 Astra
Summary
| Items | Count |
|---|---|
| Total | 94 |
| Passed | 87 |
| Failed | 0 |
| N/A | 7 |
| 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. | 🟢 | Claims trace to ER conclusion, protocol, benefits, harms, interactions and monitoring; numeric dose and timing values match. |
| 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. | 🟢 | Research, theoretical, precautionary, unestablished-target and illustrative-practice qualifications retained; tier descriptors follow the required condensation rules. |
| 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 preventive efficacy, optimal dose or safety assurance asserted; assessment periods distinguished from onset. |
| 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. | 🟢 | Benefits, risks, contraindications and interactions retain their source decision categories. |
| 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. | 🟢 | Drug examples occur in ER interactions; no new study, expert or brand identifiers. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No new attribution. |
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 distinction between disease treatment and unproven healthy-longevity use. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Objective, accessible discussion preserves actionable research context without promotional claims. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Informational framing; specialist research is not prescribed to users. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Research dose is identified as research, not self-treatment advice. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Presents studied protocols and monitoring context. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No direct address in authored content; fixed template disclaimer retained. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain-language descriptions; necessary drug-class labels retained. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Compact cells and lists without trial narratives. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | No direct address in authored content. |
| 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. | 🟢 | Healthy-longevity applicability explicitly distinguished from Parkinson’s treatment. |
| 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. | 🟢 | Monitoring and individualized specialist adjustment retained without dismissing burden. |
| 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 framed around avoiding effort or inconvenience. |
| 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. | 🟢 | No healthy-adult efficacy inferred from disease-specific findings. |
| 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. | 🟢 | Uses longevity terminology. |
| 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 terminology; no colloquial administration language. |
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 card, gate, tier and table labels retained. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All template data-qrs-var anchors remain; monitoring has additional repeated rows. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Only checklist-addressed variables populated; website placeholders 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 applicable visible source-empty section; unused risk tiers follow 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 and qualitative labels match ER; interaction labels retain wording with permitted example trimming and dash-clause removal. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Source labels retained, including benefit and risk descriptors. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji in sheet content. |
| 4.5 | The QRS is designed to render on one A4 page: every section is condensed to the shortest form the other checklist items allow, not extended onto a second page. | 🟢 | Condensed descriptors and gate items; mandatory labels, qualifiers and markers retained. |
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. | 🟢 | Metadata comment immediately follows 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 and closing YAML delimiters present. |
| 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. | 🟢 | Metadata remains in an HTML comment; visible date/model are required header variables. |
| 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. | 🟢 | Values trimmed; duration contains a colon and is quoted. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Source filename matches the named ER in staging. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | 26.10.18 matches supplied QRS guideline. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | 2026-1021-0455 follows 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]” | 🟢 | GPT-Astra recorded. |
| 5.9 | The nickname of the AI is the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT) | 🟢 | GPT-Astra is GPT 6 Astra without version, hyphenated. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | GPT 6 Astra recorded. |
| 5.11 | The full name of the AI consists of the model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y) | 🟢 | Matches supplied model name and normalization. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Matches target basename. |
| 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. | 🟢 | 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., & for &) |
🟢 | Canonical topic entity-encoded and required suffix present. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | Canonical topic matches ER frontmatter. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 10/21/2026 matches creation date. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Header model matches creator fullname. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | Only template header content present. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence | 🟢 | Opens with plant identity, seed powders/extracts, and movement/reproductive use. |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses conclusion into applicability, regimen uncertainty and practical risks. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | 64 whitespace-delimited words. |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Identity/use: ER 36–38; benefits/applicability: 475; uncertainties and harms: 479; sourcing limits: 481. |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No specialist acronyms or technical classifications in lede. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial identifiers or sample statistics. |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes or statistical results. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from ER 359, 364 and 372–379. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All avoidance populations and avoid-class interactions represented. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each contraindication uses li tags. |
| 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. | 🟢 | Only gate facts and applicability qualifiers; no mechanisms or citations. |
| 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). | 🟢 | Under-18 boundary, preceding two weeks, narrow-angle, active/uncontrolled, severe/unstable and unsupervised qualifications 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. | 🟢 | No source ranking notation to normalize. |
| 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. |
🟢 | Nonempty because source names contraindications. |
| 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 | Section is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from ER 357–370. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All twelve remaining interaction categories represented; two avoid interactions appear under Contraindications. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Each interaction uses li tags. |
| 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. | 🟢 | Dash explanations removed; theoretical and dose-dependent applicability retained. |
| 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 names retained where applicable; B6 10–25 mg without carbidopa retained. |
| 9.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | 🟢 | No source ranking notation to normalize. |
| 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. |
🟢 | Nonempty because source names interactions. |
| 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 | Section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Derived from ER 400, 404 and 407. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Covers studied maintenance exposure, timing/division, and baseline response for adjustment. |
| 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 | ER has at least three actionable aspects. |
| 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 variables meaningful and source-supported. |
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 | 🟢 | Covers acute motor onset, longer-term function assessment, and reproductive assessment. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by high, medium and low 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 source timing aspects available. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | 34.6 minutes, twelve months and three months match ER; assessment periods expressly not portrayed as onset. |
| 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 | ER provides time-to-effect information. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All descriptors come from ER Expected Benefits tiers. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | Four required benefit variables 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. | 🟢 | Key descriptors only; multi-ingredient wording belongs to the source labels. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical study detail retained. |
| 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 source benefit tiers contain items. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Descriptors match ER Potential Risks & Side Effects tiers. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | Four required risk variables present. |
| 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. | 🟢 | Key risk descriptors only. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical frequency or study details. |
| 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. | 🟢 | Empty high and medium tiers hidden with display: none and no empty-state prose. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from ER 447–459. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | Five tabulated markers plus clinician-rated movement measures included. |
| 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. |
🟢 | One/four weeks, changes, every three months and laboratory three-month recheck accurately condensed with illustrative qualification. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from ER 459–461. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | Function diaries, sleep/behavior and tolerability outcomes all included. |
Issues 21/10/2026 05:00
Pass rate 100.00%. No issues found.
Issues 21/10/2026 04:57
- 4.5 / 9.4 — Removable interaction operational explanation: Key Interactions line 547 adds “specialist recalculation” rather than retaining only the interaction identity and applicable qualifiers.
- 9.5 — Missing parenthetical drug examples: Key Interactions line 547 drops diphenhydramine and glipizide from the examples in the corresponding ER bullets (lines 369–370).
- 11.1 — Missing daily function assessment: The third time cell is hidden at lines 503–511 despite the ER describing a 12-month daily-function assessment (lines 154 and 468), a Medium-tier benefit.
Fixes 21/10/2026 04:57
- 4.5 / 9.4 — Removed operational interaction explanation: Removed “specialist recalculation” from the carbidopa/benserazide interaction.
- 9.5 — Restored parenthetical drug examples: Added diphenhydramine and glipizide to their corresponding interaction entries while retaining theoretical qualifiers.
- 11.1 — Added daily function assessment: Added the 12-month Parkinson’s daily-function assessment as the second time cell, explicitly distinguished from onset. Moved the fertility assessment to the third cell to retain benefit-tier order.