Audit: QRS - Ginkgo biloba for Health & Longevity

Audit conducted on 10/09/2026 04:31 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 benefit, risk, contraindication, interaction, marker, target and cadence traces to an 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. 🟢 The ER’s “⚠️ Conflicted” markers are carried as “(conflicted)” on the same six items.
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”). 🟢 Pregnancy/breastfeeding remains a Contraindication; hedges on dosing pattern and time of day are preserved.
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 come from the ER’s avoid-populations list, Key Interactions from the ER’s interaction bullets.
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, author names, NCT IDs or brand names appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind are present.

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, evidence-weighted register matching the ER’s “well-tested, unusually mixed record” framing.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Presents where the extract works and where it does not, giving the reader a basis for decision.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Protocol and Monitoring cells state what trials used, not what should be done.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives; cadence and gates are stated descriptively.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommended”, “advised” or “should” constructions.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the rendered text.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms appear only where they are the decision gate itself (e.g. Child-Pugh Class, P-glycoprotein).
2.8 Information is presented in a concise and very compact manner 🟢 Benefits, risks and interactions are reduced to bare item labels.
2.9 It DOES NOT address the reader directly 🟢 Confirmed — no direct address.
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. 🟢 Content is pitched at a reader weighing whether to use the extract.
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. 🟢 Nine-marker monitoring panel and a 14-day pre-procedure window are presented without softening.
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. 🟢 Assumes access to laboratory testing and medication review.
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 states plainly that there is no cognitive gain where thinking is intact — the case most relevant to 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. 🟢 The string “anti-aging” does not occur.
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 register throughout; no consumer-grade substitutes for route or adverse events.

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 column headers match the template byte-for-byte.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variables present; marker_#* and qualitative_item# correctly instantiated as 9 and 7 numbered sets.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The website=”evidence_review”, website=”audit” and website=”full_review” spans, CSS and page skeleton are unchanged from the template.

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 relied on by the QRS is empty.
4.2 Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. 🟢 “Standard dose”, “Single versus split dosing”, “Time of day” and all twelve interaction labels are the ER’s bold labels verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Marker names and Protocol labels match the ER exactly.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji characters occur in the file.
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. 🟢 Each section is reduced to the minimum the remaining checklist items permit — benefits and risks to bare headings, interactions to labels only.

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. 🟢 Comment opens at line 2, immediately 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 metadata value is repeated in 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:04" is quoted, correctly, because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: ginkgo_biloba_2026-0910-0004_Opus_ER.md at line 4.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 qrs_prompt_version: 26.7.02 matches the guideline version.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 qrs_creation_date: 2026-0910-0414.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 qrs_creator_ai_nickname: Opus.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 Single word, no version.
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 qrs_creator_ai_fullname: Opus 5.
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]” 🟢 qrs_filename: ginkgo_biloba_2026-0910-0004_Opus_QRS.html matches the file on disk.
5.13 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. 🟢 All values trimmed; quoting used only where YAML requires it.

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 &) 🟢 “Ginkgo biloba for Health & Longevity - Quick Reference Sheet”.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Ginkgo biloba for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0910-0414 → 09/10/2026.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5”.
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 is the template’s title and subline only.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses all three Conclusion paragraphs into where it works, where it does not, and what the hazard is.
7.2 [at_a_glance] is no longer than 60 words 🟢 56 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct Conclusion sentence.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 “sudden hearing loss” replaces the ER’s “sudden sensorineural hearing loss”; no acronyms used.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial is named.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numbers appear.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Taken from the “Populations who should avoid Ginkgo biloba” list.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All eight ER avoid-populations are present, in ER order.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Eight <li> elements inside the 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. 🟢 The ER’s trailing rationales (“given ginkgolic acid liver toxicity in cell work”, “shared alkylphenol chemistry”) are stripped; no dash-trailed 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). 🟢 “below 100 × 10⁹/L”, “Within 14 days”, “Child-Pugh Class B or C” and the named clotting-factor deficiencies 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 the contraindication bullets.
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 section is populated, matching an ER that names eight such populations.
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 🟢 Taken from the twelve interaction bullets of that section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All twelve ER interaction bullets appear; none duplicates a contraindication item.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Twelve <li> elements inside the 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. 🟢 Only the ER’s bold label survives; caution/monitor verdicts, mechanisms, consequences, mitigations and citations are all stripped.
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 is carried over intact, including the six-supplement antiplatelet list.
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 the interaction bullets.
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 section is populated, matching an ER that names twelve 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 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 the ER Therapeutic Protocol bullets.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, dosing split and time of day — the only three bullets that state an executable action.
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 more than 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. 🟢 All nine fields populated from the ER’s dose, split-dosing and time-of-day bullets.

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 🟢 Dementia symptoms, depressive symptoms and anxiety symptoms — the only three endpoints for which the ER states a time course.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Two High-tier benefits first, Medium-tier anxiety last; dementia progression is the ER’s first-listed High 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. N/A Three distinct time-to-effect aspects are present; 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. 🟢 “About 6 months”, “4–8 weeks” and “4 weeks” with subs drawn from the ER’s benefit and practical-considerations text.
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, so the section is retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All seventeen ER benefit headings are represented in their ER tiers.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated.
12.3 Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. 🟢 Each item is the ER heading reduced to a lowercase phrase; no magnitudes or mechanisms carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No ER parenthetical survives; the only parentheses are the ER’s own conflicted markers.
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 nine ER risk headings are represented in their ER tiers.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated.
13.3 Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. 🟢 Each item is the ER heading reduced to a lowercase phrase.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No hazard ratios, risk ratios or study details carried over.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four risk tiers contain items in the ER.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows correspond one-to-one with the ER Monitoring Protocol & Defining Success biomarker table.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All nine ER biomarkers present with their optimal ranges and reasons verbatim.
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, 6-week and 6-month rechecks, annual thereafter, 24-week cognitive repeat and the warfarin INR checks are all carried over.

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 laboratory values” list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All seven ER qualitative markers present, verbatim and in ER order.

Issues 10/09/2026 04:31

Pass rate 100.00%. No issues found.

Issues 10/09/2026 04:23

  1. 11.2 — Time sets not ordered by benefit magnitude: The three Time to Effect cells (lines 496–536) run chronologically — “Time to effect / 4–6 weeks”, “Dementia symptoms / About 6 months”, “Stopping rules / 24 weeks” — rather than ordered by the magnitude of the related benefit, and only the second cell is tied to a benefit at all.

Fixes 10/09/2026 04:23

  1. 11.2 — Time sets reordered by benefit magnitude: Replaced the chronological Time to Effect row with three benefit-tied sets ordered by tier — “Dementia symptoms / About 6 months” (High), “Depressive symptoms / 4–8 weeks” (High), “Anxiety symptoms / 4 weeks” (Medium) — dropping the untied “Time to effect” and “Stopping rules” cells and folding the four-to-six-week onset window into the first cell’s sub-text.