evipedia.aidev
← Back to Review

Audit: QRS - Vinpocetine for Health & Longevity

Audit conducted on 07/08/2026 05:09 using AI4L / Grok 4

Iterations

Summary

Items Count
Total 91
Passed 85
Failed 0
N/A 6
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. 🟢  
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. 🟢  
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”). 🟢  
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. 🟢  
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. 🟢  
1.6 The QRS does not introduce new attributions. 🟢  

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. 🟢  
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢  
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢  
2.4 The QRS avoids language that implies medical or clinical advice 🟢  
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢  
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢  
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢  
2.8 Information is presented in a concise and very compact manner 🟢  
2.9 It DOES NOT address the reader directly 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  

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” 🟢  
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢  
3.3 Spans that are not addressed in a checklist item are left 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 fully empty ER source section maps to a QRS section requiring empty-state phrasing.
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. 🟢  
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢  
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢  
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. 🟢  

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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢  
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version 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) 🟢  
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢  
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢  
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢  
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) 🟢  
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢  
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. 🟢  

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 &) 🟢  
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢  
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢  
6.4 [header_subline_model] is set to [qrs_creator_ai_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. 🟢  

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢  
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. 🟢  
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢  
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢  
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢  

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢  
8.2 [stop_items] represent the Contraindications from the ER 🟢  
8.3 Individual [stop_items] are formatted as <li></li> 🟢  
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. 🟢  
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). 🟢  
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 ranking notation in ER contraindications.
8.7 If no [stop_items] are present the section is left empty N/A stop_items are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢  
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢  
9.3 Individual [caution_items] are formatted as <li></li> 🟢  
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. 🟢  
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). 🟢  
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 ranking notation in ER interactions.
9.7 If no [caution_items] are present the section is left empty N/A caution_items are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢  
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢  
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 or more distinct actionable aspects are present in the ER.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢  

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 🟢 ER Practical Considerations states two time-to-effect aspects; both are covered.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Brain blood flow (Medium benefit) before cognitive scales (Low benefit).
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. 🟢 Only two aspects in ER; time_3 pcell is empty with display:none.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢  
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 🟢  
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢  
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. 🟢  
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢  
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 benefits_high has display:none; no High tier in ER.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢  
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢  
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. 🟢  
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢  
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 risk tiers have items in the ER and QRS.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢  
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All five table biomarkers present.
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. 🟢  

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢  
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six qualitative markers present.

Issues 07/08/2026 05:09

Pass rate 100.00%. No issues found.

Issues 07/08/2026 05:03

  1. 1.1 — Leftover benefits_high placeholder: The hidden benefits_high span still contains template placeholder text [benefits_high], which is not ER-supported content.
  2. 2.8 — Redundant action_2_sub opener: action_2_sub begins with “Low maintenance dose;” which only restates action_2_label before listing mid-range and high-end regimens.

Fixes 07/08/2026 05:04

  1. 1.1 — Leftover benefits_high placeholder: Cleared template placeholder [benefits_high] from the hidden high-benefits span; span remains display: none with empty High tier content.
  2. 2.8 — Redundant action_2_sub opener: Replaced action_2_sub leading “Low maintenance dose;” with “15 mg/day total; mid-range often 10 mg three times daily; up to 20 mg three times daily in older dementia trials” so the sub no longer restates the label.

Issues 07/08/2026 04:50

  1. 1.2 — Cautious phrasing dropped: action_3_sub uses “move evening dose earlier if insomnia” instead of the ER’s cautious “Evening dose may be moved earlier if insomnia appears” (Therapeutic Protocol / Practical Considerations).
  2. 1.3 — Claim strengthened to imperative: Same action_3_sub turns a permissive ER statement into an instruction, strengthening the claim.
  3. 2.4 — Clinical advice language: action_3_sub imperative wording implies clinical advice rather than neutral presentation of evidence.
  4. 2.5 — Guidance instead of information: action_3_sub provides dosing guidance (“move…”) instead of presenting information about possible evening-dose timing adjustment.

Fixes 07/08/2026 04:51

  1. 1.2 / 1.3 / 2.4 / 2.5 — Evening-dose wording: Replaced imperative action_3_sub “move evening dose earlier if insomnia” with ER-aligned “evening dose may be moved earlier if insomnia appears” (restores cautious phrasing; presents information rather than guidance).

Issues 07/08/2026 04:38

  1. 1.2 / 1.3 — At-a-glance cognitive phrasing: At-a-glance says “Older trials show modest cognitive gains mainly with circulatory brain impairment,” while the ER Conclusion uses cautious “modest older trial signals” and the Expected Benefits section notes Cochrane evidence was inconclusive.

  2. 9.5 — BP interaction examples dropped: Key Interactions lists “Blood-pressure–lowering agents (ACE inhibitors, ARBs, calcium-channel blockers, beta-blockers, diuretics)” without any of the ER example drugs (lisinopril, ramipril, losartan, valsartan, amlodipine, metoprolol, hydrochlorothiazide).

Fixes 07/08/2026 04:38

  1. 1.2 / 1.3 — At-a-glance cognitive phrasing: Changed “Older trials show modest cognitive gains mainly with circulatory brain impairment” to “Older trials report modest cognitive signals mainly with circulatory brain impairment” to match ER cautious wording.

  2. 9.5 — BP interaction examples restored: Expanded the blood-pressure–lowering agents Key Interaction line to include ER example drugs (lisinopril, ramipril, losartan, valsartan, amlodipine, metoprolol, hydrochlorothiazide) under each class.

Issues 07/08/2026 04:30

  1. 2.15 — Colloquial “thinking gains”: At-a-glance uses consumer-grade “thinking gains” instead of formal clinical phrasing such as “cognitive gains” aligned with the ER Conclusion.

  2. 4.3 — Invented protocol label: action_2_label is “Starting Dose”, which is not an ER bold label or ER phrase; the content is drawn from the Standard oral range low-maintenance / dose-ladder wording.

  3. 7.4 — Specialist “inflammatory signaling”: At-a-glance uses technical “inflammatory signaling”; At-A-Glance requires plain-language wording instead.

Fixes 07/08/2026 04:31

  1. 2.15 — Colloquial thinking gains: Replaced “thinking gains” with formal “cognitive gains” in at-a-glance.

  2. 4.3 — Invented protocol label: Changed action_2_label from invented “Starting Dose” to ER phrase “Low maintenance dose”; aligned action_2_sub wording.

  3. 7.4 — Specialist inflammatory signaling: Replaced “inflammatory signaling in vessels” with plain-language “vessel inflammation” in at-a-glance.

Issues 07/08/2026 04:22

  1. 1.1 — Unsupported stroke TTE claim: Time-to-effect cell presents ‘Stroke Disability / 1–3 months’ as if it were protocol time-to-effect; ER Practical Considerations only supports days–weeks (perfusion/clear-headedness) and weeks–months (cognitive scales).
  2. 1.4 — Benefit endpoint as TTE: Acute-stroke death/disability outcome timing from Expected Benefits is relabeled into the Protocol Time to effect category.
  3. 11.1 — Invalid third TTE set: QRS fills three time sets though the ER only states two distinct time-to-effect aspects; ‘Stroke Disability’ is not a TTE aspect from the ER.
  4. 11.3 — Unused TTE set not hidden: With only two ER TTE aspects, the third time set must be empty and invisible; it is populated instead.
  5. 11.4 — time_2 not ER-derived TTE: time_2_label/value/sub recycle acute-stroke pooled-analysis outcome windows rather than ER time-to-effect content.

Fixes 07/08/2026 04:22

  1. 1.1 — Unsupported stroke TTE claim: Removed the invented Stroke Disability time-to-effect cell; Time to effect now only uses ER Practical Considerations content (perfusion days–weeks; cognitive scales weeks–months).
  2. 1.4 — Benefit endpoint as TTE: Stopped surfacing acute-stroke disability outcome timing under Protocol Time to effect; that benefit-endpoint fact is no longer relabeled as TTE.
  3. 11.1 / 11.3 / 11.4 — Third TTE set cleanup: Kept two ER-derived TTE sets (Brain Blood Flow; Cognitive Scales), emptied time_3 spans, and hid the third pcell with display: none.

Issues 07/08/2026 04:17

  1. 4.2 / 4.3 — Protocol labels paraphrased: action_1_label uses “Standard Dose” instead of the ER bold label “Standard oral range”; action_3_label uses “With Food” instead of “Food”.
  2. 8.4 — FDA attribution in stop item: Pregnancy contraindication retains “per FDA warning”, which is an attribution and should be stripped; keep severity as “(absolute avoidance)” only.
  3. 12.3 / 12.4 — early-treated qualifier retained: Medium benefits include “early-treated” derived from the ER parenthetical “(Early Treatment)”, which benefits rules require stripping.

Fixes 07/08/2026 04:18

  1. 4.2 / 4.3 — Protocol labels paraphrased: Changed action_1_label from “Standard Dose” to “Standard oral range” and action_3_label from “With Food” to “Food” to match ER bold labels.
  2. 8.4 — FDA attribution in stop item: Removed “per FDA warning” from the pregnancy contraindication; item is now “Pregnant women and those trying to conceive (absolute avoidance)”.
  3. 12.3 / 12.4 — early-treated qualifier retained: Stripped “early-treated” from medium benefits; now “reduced disability after acute ischemic stroke”.

Issues 07/08/2026 04:09

  1. 2.4 — Medical-advice phrasing: At-a-glance uses imperative “Avoid in pregnancy”, which implies clinical advice rather than neutral presentation of evidence.
  2. 2.5 — Guidance not information: Same at-a-glance clause provides guidance (“Avoid…”) instead of presenting the pregnancy-exclusion fact in descriptive form.
  3. 2.6 / 2.9 — Reader addressed: Imperative “Avoid in pregnancy” addresses the reader directly rather than presenting evidence only.
  4. 2.7 — TID medical jargon: Protocol action_2_sub uses unexplained abbreviation “TID”; the ER uses “three times daily”.
  5. 13.3 / 13.4 — Speculative risk parenthetical: risks_speculative keeps “(e.g., lowered white-cell count)”, which must be stripped as parenthetical/example elaboration.

Fixes 07/08/2026 04:11

  1. 2.4 / 2.5 / 2.6 / 2.9 — Pregnancy phrasing: Replaced imperative at-a-glance “Avoid in pregnancy” with descriptive “Pregnancy is a firm exclusion”.
  2. 2.7 — TID jargon removed: Replaced “TID” in action_2_sub with “three times daily” to match ER plain language.
  3. 13.3 / 13.4 — Speculative risk parenthetical: Stripped “(e.g., lowered white-cell count)” from risks_speculative, leaving “Hematologic effects; long-term unknowns at supplement doses”.