Audit: QRS - Chaste Tree for Health & Longevity
Audit conducted on 16/08/2026 12:04 using AI4L / Opus 5
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. | 🟢 | All protocol, time, benefit, risk, gate, marker and qualitative content traces to the ER (Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications, Monitoring Protocol & Defining Success, Conclusion). |
| 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. | 🟢 | Speculative tiers are carried as “Speculative”; no cautious ER wording is upgraded. |
| 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”). | 🟢 | Absolute contraindications stay in the stop gate; caution-level interactions stay in the caution gate. |
| 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. | 🟢 | Modifying-factor bullets are not used anywhere; each gate/tier item comes from the matching ER section. |
| 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. | 🟢 | Only Ze 440 and BNO 1095 appear (line 457), both from the ER Therapeutic Protocol bullet for the same dose fact; no PMIDs, NCT IDs or author names. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind in the QRS. |
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. | 🟢 | Wording is largely ER-verbatim, including the Conclusion’s own register in At-A-Glance. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Objective and specific throughout, with actionable protocol and monitoring targets. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated as evidence and targets, not as instructions to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No prescriptive second-person constructions; 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 in the QRS body. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the file; the ER’s imperatives (“Rate”, “Record”, “Log”) were converted to nominal forms in the Qualitative Assessment card. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms carry the ER’s own glosses (“Ferritin (the stored form of iron)”, “thyroid-stimulating hormone”). |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every item is reduced to its key fact; magnitudes, citations and mechanistic rationale are stripped. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by full-text scan for you/your/we/our — no hits. |
| 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. | 🟢 | Baseline biomarker panel, functional target ranges and a defined three-cycle trial address an active self-optimizing 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. | 🟢 | Seven-marker baseline panel and daily symptom tracking assume high willingness to act. |
| 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. | 🟢 | Content depth (extract identity, mid-luteal timing, LH-to-FSH ratio) is beyond general-population framing. |
| 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 retains the sponsor-bias and overstated-effect caveat rather than a promotional summary. |
| 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. | 🟢 | “Longevity” is used in the title; “anti-aging” does not appear. |
| 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. | 🟢 | Clinical register throughout (“intermenstrual bleeding”, “hypersensitivity skin reactions”, “mid-luteal progesterone”); no consumer-grade substitutions. |
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 present verbatim (lines 446, 493, 542, 573, 590, 621, 649, 653–655, 774) and all four tier labels appear in both Benefits and Risks. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | 61 named spans present with unbroken numbering (action 1–3, time 1–3, marker 1–7, qualitative 1–6) plus the three website= template spans at lines 423, 426, 440. |
| 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 are untouched; every named span is covered by a checklist item. |
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 European protocol”, “Best time of day”, “Baseline biomarkers”, and all six Qualitative Assessment labels match the ER bold labels verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Marker names match the ER biomarker table verbatim; Time-to-Effect labels are drawn from the ER’s own benefit headings and cycle-regulation wording. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Full-text scan returns no emoji code points; the ER’s ⚠️ Conflicted markers were correctly dropped. |
| 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 permitted by the completeness requirements of 8.2, 9.2, 12.2, 13.2, 14.2 and 15.2; no residual explanations, magnitudes or citations remain to condense. |
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 duplicate of these values appears in head or 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:03" is quoted, correctly, because it contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: chaste_tree_2026-0825-1111_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 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) | 🟢 | Line 6: qrs_creation_date: 2026-0816-1156. |
| 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” is a single word with no version or qualifier. |
| 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” is nickname plus version with no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9 matches the file on disk: chaste_tree_2026-0825-1111_Opus_QRS.html. |
| 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 across all eleven keys; no stray whitespace or 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 &) |
🟢 | Line 22: “Chaste Tree for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | Line 417: “Chaste Tree for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/16/2026”, matching qrs_creation_date: 2026-0816-1156. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “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 holds only the title and the template subline (lines 415–428); the ER’s “Also known as” line was not carried over. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Lines 434–438 compress all three Conclusion paragraphs: mechanism, evidence tiering, safety, and sponsor bias. |
| 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 distinct Conclusion sentence (ER lines 471, 473, 475). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “prolactin” is glossed as “the milk-producing hormone” and “second-half hormone patterns” replaces “luteal phase”. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years or sample sizes. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numeric results; the effect is described qualitatively as “probably overstated”. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All seven items map to the ER’s “Populations who should avoid Chaste tree” list (ER lines 314–320). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All seven ER avoid-populations are present; none is omitted or added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Seven <li> elements inside the span (lines 576–585). |
| 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 post-em-dash rationale (“theoretical uterine-stimulant… no human safety data”, “prolactin suppression may reduce milk supply”) is stripped; only applicability qualifiers survive. |
| 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). | 🟢 | “larger than 10 mm”, “active or in remission”, “at least four weeks beforehand” and “under 18 outside specialist supervision” 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 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 seven such populations and the section is populated accordingly. |
| 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 seven items map to the ER’s interaction bullets (ER lines 296–310). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Seven of the ER’s eight interaction bullets appear; “Ovulation-induction and assisted reproduction drugs” is correctly excluded because it is an absolute contraindication carried in [stop_items]. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Seven <li> elements inside the span (lines 593–611). |
| 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. | 🟢 | All “Caution.” sentences and mechanism text are stripped, including the ER’s “which supplies L-DOPA” gloss and “where sold without prescription” qualifier. |
| 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 agents are retained for every item (haloperidol/risperidone/amisulpride/metoclopramide, bromocriptine/cabergoline, cimetidine/promethazine, Mucuna pruriens/vitamin B6/zinc, Hypericum perforatum). |
| 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 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 eight interactions and the section is populated accordingly. |
| 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 (ER lines 344, 352, 364). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose/extract identity, dose timing, and baseline biomarkers are the three load-bearing implementation decisions in that 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 | The ER supplies at least three distinct actionable aspects and 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 spans carry ER-derived content (lines 450–488); the sub-cells reproduce the ER’s extract names, timing rationale and baseline panel. |
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 | 🟢 | Premenstrual symptoms, cyclical breast pain and cycle regulation, drawn from ER Practical Considerations and the breast-pain magnitude data. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Order follows the ER benefit tiers: two High-tier benefits first, then the Low-tier cycle-irregularity 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 exist and 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. | 🟢 | All nine spans populated (lines 499–534); “3 cycles”, “3 cycles” and “Up to 6 months” all trace to ER statements. |
| 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 (ER line 399), so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All eight benefit headings from the ER are represented in the matching tier. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated (lines 544–566). |
| 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. | 🟢 | Items are the ER benefit headings only; the Magnitude paragraphs (responder rates, SMD 0.67, RR 2.57) are all excluded. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses in any benefit item; the ER’s “⚠️ Conflicted” markers are also dropped. |
| 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 | The ER populates all four benefit tiers, so no sub-section is empty. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All nine risk headings from the ER are represented in the matching tier. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated (lines 623–643). |
| 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. | 🟢 | Items are the ER risk headings only; the Magnitude paragraphs and Daniele/Schellenberg citations are excluded. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses in any risk item; the ER’s “⚠️ Conflicted” marker on Acne is dropped. |
| 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 | The ER populates all four risk tiers, so no sub-section is empty. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows reproduce the ER Monitoring Protocol & Defining Success biomarker table, including its “Why Measure It?” text. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All seven ER biomarkers present: prolactin, mid-luteal progesterone, TSH, estradiol, LH/FSH, ALT and ferritin, with their optimal functional ranges unchanged. |
| 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. |
🟢 | Lines 764–768 carry baseline, three-cycle, six-month, six-to-twelve-month intervals plus the earlier-retesting triggers from ER line 425. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All six items come from the ER’s “Qualitative markers worth tracking” list (ER lines 439–449). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | Premenstrual symptom diary, breast comfort, cycle regularity, sleep quality, energy and cognitive clarity, and skin — six of six, with the ER’s bold labels intact. |
Issues 16/08/2026 12:04
Pass rate 100.00%. No issues found.