Audit: QRS - Schisandra for Health & Longevity
Audit conducted on 26/06/2026 04:48 using AI4L / Opus 4.8
Summary
| Items | Count |
|---|---|
| Total | 91 |
| Passed | 86 |
| Failed | 0 |
| N/A | 5 |
| 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. | 🟢 | All QRS content traces to ER passages (e.g., at-a-glance to Conclusion lines 398–402; gates to ER lines 256–268; protocol to ER lines 290–298). |
| 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. | 🟢 | Cautious framing preserved (at-a-glance “Evidence is uneven… human research sparse”). |
| 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 strengthening or softening; pregnancy listed as a contraindication consistent with ER line 268. |
| 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. | 🟢 | Categories map cleanly to their ER source sections. |
| 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, citations, or brand names introduced in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No new attributions 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. | 🟢 | Matches the ER’s measured, evidence-graded tone. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert yet accessible throughout. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents evidence, not prescriptions. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No directive medical advice; footer disclaimer present. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Information-presenting register maintained. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person address. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms glossed or avoided in the at-a-glance. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Compact cells and bullets throughout. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | 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 fits the optimizing-adult audience. |
| 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. | 🟢 | Protocol/monitoring detail assumes a willing audience. |
| 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 pitched to a general audience. |
| 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. | 🟢 | Risk/benefit weighting consistent with the 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. | 🟢 | No “anti-aging” voice usage. |
| 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. | 🟢 | Uses “medications”, “gastrointestinal upset”, etc. |
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/labels present and unmodified (lines 440, 477, 519, 539, 551, 569, 588, 592–594, 674). |
| 3.2 | All “…” from the [qrs_template] are present in the QRS. | 🟢 | All expected data-qrs-var spans present. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | No unauthorized span modifications detected. |
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”. | 🟢 | High tiers (no ER content) use display:none rather than invented text; no empty-state mismatch. |
| 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/gate labels match ER bold labels (e.g., “Standard dosing (whole berry / extract)”, line 290). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Labels preserved from the ER. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji indicators in the rendered content. |
| 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. | 🟢 | Content condensed to one-page budget. |
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 is first element (lines 2–14). |
| 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. | 🟢 | YAML delimited by — at lines 3 and 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; not rendered. |
| 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; only “duration” quoted (contains colon). |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]”. | 🟢 | er_filename: schisandra_2026-0626-0348_Opus_ER.md (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.5.18 (line 5), matches QRS.md. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]”. | 🟢 | qrs_creation_date: 2026-0626-0435 (line 6). |
| 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 (line 7). |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. | 🟢 | “Opus” is a single word. |
| 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 4.8 (line 8). |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier. | 🟢 | “Opus 4.8” — nickname plus version, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]”. | 🟢 | qrs_filename: schisandra_2026-0626-0348_Opus_QRS.html (line 9). |
| 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 trimmed and correctly quoted. |
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”. The [canonical_topic] is HTML-entity-encoded as needed. | 🟢 | “Schisandra for Health & Longevity - Quick Reference Sheet” (line 22). |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed. | 🟢 | “Schisandra for Health & Longevity” (line 417). |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]. | 🟢 | “06/26/2026” (line 421), from 2026-0626. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname]. | 🟢 | “Opus 4.8” (line 425). |
| 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 the permitted elements. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section. |
🟢 | Distills ER Conclusion (lines 398–402). |
| 7.2 | [at_a_glance] is no longer than 60 words. | 🟢 | 58 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a Conclusion passage. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead. | 🟢 | “Adaptogen” is self-glossed (“stamina- and stress-supporting”); “lignans” glossed as antioxidants; no specialist acronyms. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values). | 🟢 | No trials cited. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results. | 🟢 | No statistics cited. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section. |
🟢 | Derived from ER line 268 (“Populations who should avoid Schisandra”). |
| 8.2 | [stop_items] represent the Contraindications from the ER. | 🟢 | All five avoid-populations represented (lines 542–546). |
| 8.3 | Individual [stop_items] are formatted as <li></li>. | 🟢 | Each item is an <li>. |
| 8.4 | Items are as concise as possible. No trailing explanations, elaborations, mechanistic rationale, attributions, citations, study details. No content after an em-dash, en-dash, or hyphen-dash. Just the key fact. | 🟢 | No trailing dash content; items are terse facts. |
| 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. | 🟢 | “(decompensated cirrhosis, Child-Pugh Class C)” and “(unless supervised)” preserved. |
| 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. | 🟢 | ER uses no such ranking notation here; nothing to normalize. |
| 8.7 | If no [stop_items] are present the section is left empty. | N/A | Contraindications are present, so this empty-state condition does not apply. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section. |
🟢 | Derived from ER interaction bullets (lines 256–266). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications. | 🟢 | Six interaction classes listed; the immunosuppressant drug class is distinct from the transplant-recipient population contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li>. | 🟢 | Each item is an <li>. |
| 9.4 | Items are as concise as possible. No trailing explanations, elaborations, mechanistic rationale, attributions, citations, study details. No content after an em-dash, en-dash, or hyphen-dash. Just the key fact. | 🟢 | Severity/explanatory clauses stripped; no trailing dash content. |
| 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. | 🟢 | Example-drug parentheticals preserved (e.g., “(tacrolimus, sirolimus, cyclosporine)”). |
| 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 the ER bullets; lists are already comma-separated. |
| 9.7 | If no [caution_items] are present the section is left empty. | N/A | Key Interactions are present, so this empty-state condition does not apply. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section. |
🟢 | Derived from ER Therapeutic Protocol (lines 286–308). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section. |
🟢 | Standard dosing, best time of day, single-vs-split dosing. |
| 10.3 | If less than three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible. | N/A | Three distinct actionable aspects exist, so the under-three condition does not apply. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All three cells fully populated from 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. | 🟢 | Liver-enzyme/metabolic, menopausal, subjective stress/energy (ER line 337). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit. | 🟢 | Ordered Medium-tier benefits first (hepato/metabolic, menopausal), Low-tier subjective last. |
| 11.3 | If less than three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible. | N/A | Three distinct aspects exist, so the under-three condition does not apply. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All three cells populated from ER line 337. |
| 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 data, so removal does not apply. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section. |
🟢 | Derived from ER Expected Benefits (lines 140–184). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]. | 🟢 | All four tiers present. |
| 12.3 | Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations. Just the key fact. | 🟢 | Terse benefit labels only. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheticals carried into benefit items. |
| 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 empty-state phrasing. | 🟢 | High tier (no ER content) set to display:none (line 521). |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section. |
🟢 | Derived from ER Risks (lines 200–238). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]. | 🟢 | All four tiers present. |
| 13.3 | Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations. Just the key fact. | 🟢 | Terse risk labels only. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheticals carried into risk items. |
| 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 empty-state phrasing. | 🟢 | High tier (no ER content) set to display:none (line 571). |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section. |
🟢 | Derived from ER Monitoring Protocol (lines 357–371). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed. |
🟢 | All six ER table biomarkers present (markers 1–6). |
| 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. |
🟢 | Cadence matches ER line 361 (line 668). |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section. |
🟢 | Derived from ER qualitative markers (lines 374–378). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed. |
🟢 | All five qualitative markers present (items 1–5). |
Issues 26/06/2026 04:48
Pass rate 100.00%. No issues found.
Issues 26/06/2026 04:43
- 12.4 — Parentheticals not stripped from benefits: benefits_medium, benefits_low, and benefits_speculative retain plain-language parentheticals “(liver enzyme support)”, “(blood sugar)”, “(stress resilience)”, and “(anti-sarcopenia)” at QRS lines 525–531; item 12.4 requires all parenthetical content to be stripped, not preserved.
Fixes 26/06/2026 04:43
- 12.4 — Stripped parentheticals from benefits: Removed the plain-language parentheticals from the benefit items — “Hepatoprotection (liver enzyme support)” → “Hepatoprotection”, “Glycemic control (blood sugar)” → “Glycemic control”, “physical endurance & anti-fatigue (stress resilience)” → “physical endurance & anti-fatigue”, and “muscle preservation (anti-sarcopenia)” → “muscle preservation”.
Issues 26/06/2026 04:39
- 14.2 — Kupperman Index marker omitted: The ER Monitoring table (line 370) includes the quantifiable “Kupperman Index / menopause symptom score” as a sixth biomarker, but the QRS Monitoring table (markers 1–5, lines 600–650) lists only ALT, AST, fasting glucose, HbA1c, and LDL, dropping the Kupperman Index.
Fixes 26/06/2026 04:39
- 14.2 — Added Kupperman Index marker: Added a sixth Monitoring row for the quantifiable “Kupperman Index / menopause symptom score” (target “Lower score = fewer symptoms”; why “Quantifies menopausal-symptom benefit”), matching the ER Monitoring table that the QRS had previously omitted.