Audit: QRS - Baikal Skullcap for Health & Longevity

Audit conducted on 15/08/2026 17:38 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. 🟢 At-a-glance, protocol cells, time-to-effect, benefit/risk tiers, gates, all 8 markers, cadence, and all 8 qualitative items trace to ER text.
1.2 Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing. 🟢 No ER hedge is dropped or rewritten; “The signal is real but narrow” carried verbatim from the ER Conclusion.
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”). 🟢 The absolute contraindication for transplant recipients on calcineurin inhibitors stays in Contraindications, not Key Interactions.
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. 🟢 Benefit- and Risk-Modifying Factors are not surfaced at all; gates draw only from Key Interactions & Contraindications.
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, NCT IDs, author names, or brand names (Limbrel, flavocoxid, Univestin, UP446) anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind 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.
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 paired with plain-language framing.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is presented as observed practice (“Standard practitioner protocol”), not as instruction.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Cadence and qualitative items are noun-phrase statements, not imperatives.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No occurrence of “should”, “must”, “recommend”, “advise”, “ensure”, or “consider” in body content.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the document.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained only where they are the decision handle (OATP1B1, CYP3A4), each paired with named example drugs.
2.8 Information is presented in a concise and very compact manner 🟢 Benefit and risk tiers reduced to bare headings; gate items stripped to category plus example list.
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. 🟢 Framing assumes a reader who will run liver panels and track symptom scores.
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, weekly fasting glucose, and 12-week course reassessment are presented without hedging on 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. 🟢 Monitoring targets use optimal functional ranges, not conventional lab flags.
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 closes on the narrow-but-real signal, matching the ER’s conditional endorsement.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. 🟢 “anti-aging” does not appear; the title uses “Health & Longevity”.
2.15 The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. 🟢 Formal terms used throughout (“alanine aminotransferase”, “hypersensitivity pneumonitis”); plain-language substitutes appear only inside At-A-Glance, where item 7.4 requires them.

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 headings, gate headings, tier labels, and table column headers present verbatim.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All 66 template variable spans present (page_title through qualitative_item_8).
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The website="evidence_review", website="audit", and website="full_review" placeholder spans are untouched.

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 that feeds 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 practitioner protocol”, “Best time of day”, “Single versus split dosing” match the ER Therapeutic Protocol bold labels verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 All eight marker names match the ER biomarker table verbatim.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji present; the ER’s ⚠️ Conflicted markers were correctly stripped.
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 against the ER: tiers reduced to headings, gate items to category plus example list, marker targets trimmed.

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 <!doctype html> on line 1.
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML. 🟢 Opening --- at line 3, closing --- at line 13.
5.3 The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. 🟢 Enclosed in an HTML comment; no value is echoed elsewhere 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. 🟢 Only duration: "00:02" is quoted, and it contains a colon requiring it.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: baikal_skullcap_2026-0825-1434_Opus_ER.md.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 Line 5: qrs_prompt_version: 26.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-0815-1726.
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” — 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]” 🟢 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 matches the actual filename 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. 🟢 Confirmed for all eight keys.

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 &) 🟢 “Baikal Skullcap 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 &) 🟢 “Baikal Skullcap for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0815-1726 → 08/15/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 carries only title and the standard subline; the ER’s seven alternate names are not reproduced.

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 four Conclusion threads: mechanism, tiered benefit, the two safety signals, and the narrow verdict.
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. 🟢 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 🟢 “yellow pigments”, “blood fats”, “knee and hip arthritis”, “gum inflammation” used in place of flavones, lipids, osteoarthritis, gingival inflammation.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial identifiers of any kind.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numeric results present.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Sourced from the “Populations who should avoid Baikal skullcap” list plus the absolute-contraindication bullet.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoidance populations present, one-to-one.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Six <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 rationale “on absent safety data and traditional uterine claims” correctly stripped from the pregnancy item; 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 B or C”, “above twice the upper limit of normal”, “(cyclosporine, tacrolimus)”, and “Within 14 days” 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 inside parentheses in this section.
8.7 The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision. 🟢 The ER names six such populations and the section is correctly non-empty.
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All nine items map to ER bullets in that section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Nine of the ER’s ten interaction bullets carried; the calcineurin-inhibitor bullet is correctly excluded as it appears in Contraindications.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Nine <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. 🟢 Every item reduced to category plus example list; the ER’s mechanism sentences and Caution/Monitor severity words are 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). 🟢 Named drug lists retained throughout, including the “acetaminophen above 2 g/day” threshold.
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 names ten such interactions and the section is correctly non-empty.
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 drawn 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, timing, and dose-splitting — the three bullets that determine how the intervention is actually taken.
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 fields populated; the 1.6-fold food effect and 85–90% baicalin standardisation both trace to the ER.

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 🟢 Joint pain, gum inflammation, and mood — the three named in the ER Practical Considerations time-to-effect bullet.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Joint pain (High tier) first, then gum inflammation and mood (both Medium tier), in ER order.
11.3 If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A The ER names exactly three time-to-effect aspects.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All nine time fields populated; “Continued through 90 days” and “14–21 days” match the ER wording.
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel N/A The ER does provide time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All thirteen items map to ER benefit sub-headings across the four 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. 🟢 Reduced to bare sub-headings; the ⚠️ Conflicted qualifier, magnitude figures, and funding caveats all stripped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried into any tier.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four tiers carry items in the ER.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All six items map to ER risk sub-headings across the four 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. 🟢 Reduced to bare sub-headings; the registry figures, incidence rates, and ⚠️ Conflicted qualifier all stripped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried into any tier.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four tiers carry items in the ER.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Drawn from the ER Monitoring Protocol & Defining Success biomarker table.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight ER table rows present, with names, targets, and rationale preserved.
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. 🟢 Carries the liver panel, lipid panel, and fasting glucose schedules from the ER’s ongoing-monitoring paragraph.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Drawn from the ER’s “Qualitative markers tracked alongside the labs” list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All eight ER qualitative markers present verbatim.

Issues 15/08/2026 17:38

Pass rate 100.00%. No issues found.

Issues 15/08/2026 17:31

  1. 1.3 — Split-dose tolerability overstated: [action_3_sub] at line 472 asserts “split dosing gave the cleanest tolerability” as established fact, whereas ER line 373 attributes it to what the split-dose joint trials reported.

Fixes 15/08/2026 17:31

  1. 1.3 — Split-dose tolerability overstated: Reworded [action_3_sub] from “split dosing gave the cleanest tolerability” to “split-dose joint trials reported the cleanest tolerability”, restoring the ER’s attribution to what the trials reported.