Audit: QRS - Microdosing Psilocybin for Health & Longevity

Audit conducted on 30/09/2026 05:03 using AI4L + evidence-mcp / Opus 5.5

Iterations

Summary

Items Count
Total 94
Passed 87
Failed 0
N/A 7
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 sheet content traced to ER: lede to Conclusion; protocol to Therapeutic Protocol; time cells to Practical Considerations and Psychomotor Speed; tiers, gates and markers to the matching ER sections.
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 phrasing kept: “unreplicated”, “Observational reports; blinded trials over similar periods show no separation from placebo”, “gains largely disappear”.
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 claim strengthened or softened; lithium kept as “absolute contraindication”; evidence tiers match the ER.
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 avoid-list and interactions from the ER interaction bullets; no modifying factor relabelled.
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, study names or brand names; only ER terms (Fadiman protocol, Psilocybe cubensis) are used.
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 🟢 No second-person address found.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain wording; the technical terms that remain are ER labels, marker names or example drug names.
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. 🟢 Uses “healthier aging” and “Longevity”; no “anti-aging”.
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. 🟢 No lay route or consumer-grade terms (pill, by mouth, shot).

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 headers are unchanged.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All template spans are present; marker_# expanded to 1–6 and qualitative_item_# expanded to 1–8.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The website spans, footer and structural comments 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” 🟢 The only empty ER subsections are the Benefits High/Medium and Risk High tiers; per 12.5/13.5 these are hidden with display:none.
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 labels (Standard mushroom dose, Fadiman protocol, Time of day) and interaction labels match the ER bold labels verbatim.
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. 🟢 No emoji in the QRS body.
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 condensed from the ER (rationale stripped from the gates, labels only in the tiers); nothing is extended.

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 on line 2, directly 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. 🟢  
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. 🟢 The only quoted value is duration: “00:00”, which contains a colon.
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]” 🟢 26.9.29 matches the QRS.md version.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 2026-0930-0445
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) 🟢 Opus 5.5
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 &) 🟢 “Microdosing Psilocybin 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 &) 🟢  
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/30/2026
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Opus 5.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. 🟢  

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence 🟢 Starts with “Microdosing psilocybin is the practice of regularly taking imperceptible amounts of psilocybin, a hallucinogenic mushroom compound, for better mood, focus, and healthier aging.”
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the four ER Conclusion paragraphs: reported vs blinded benefits, longevity basis, main risks.
7.3 [at_a_glance] is no longer than 70 words 🟢 70 words (script count).
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢  
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms or specialist classifications.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢  
7.7 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 🟢 All 8 ER “Populations who should avoid” entries are present.
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. 🟢 Rationale stripped (e.g., the Oregon/Colorado minimum-age explanation); no trailing dash clauses.
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). 🟢 Thresholds kept: moderate or greater regurgitation, ≥160/100 mmHg, within the past 6 months, under 21.
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.
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. 🟢 Section is populated, as the ER names populations to avoid.
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 Section is not empty.

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 🟢 All 11 non-lithium ER interaction bullets are present; lithium sits only under 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. 🟢 Mechanisms and mitigations stripped; only labels with severity tags remain.
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). 🟢 Example drug lists and severity tags (avoid/caution/monitor) kept; supplement acronym expansions trimmed.
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.
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. 🟢 Section is populated, as the ER names 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 Section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells come from 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, schedule and timing are covered.
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 has more than three actionable aspects.
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 🟢 Mood (2–4 weeks), psychomotor speed (about 30 days) and acute effects (30–60 minutes) are all ER time points.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 The two benefit-linked cells are ordered by cohort effect (mood small-to-medium, then psychomotor d = 0.34); the acute-onset cell is last.
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 gives three or more time-to-effect aspects.
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 The 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. 🟢 Only ER benefit labels are used, with no effect sizes.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Parentheticals stripped (e.g., the ADHD expansion).
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 and benefits_medium spans carry style=”display: none”.

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. 🟢 Only ER risk labels are used, with no frequencies.
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. 🟢 risks_high span carries style=”display: none”.

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 6 ER table biomarkers are listed with their ER targets and reasons.
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 the ER baseline and ongoing schedule.

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 8 ER qualitative markers are listed verbatim.

Issues 30/09/2026 05:03

Pass rate 100.00%. No issues found.

Issues 30/09/2026 04:58

  1. 1.2 — Lede drops cautious qualifier: At a Glance (line 433) states “Longevity claims rest on cell and animal studies at far larger doses”, omitting the ER Conclusion’s cautious phrasing “limited, unreplicated cell and animal work”.

Fixes 30/09/2026 04:58

  1. 1.2 — Lede drops cautious qualifier: Changed At a Glance to “Longevity claims rest on limited, unreplicated cell and animal studies at far larger doses”; trimmed “tiny,” and “Key” to keep the lede at 70 words.

Issues 30/09/2026 04:55

  1. 1.1 — Cumulative-use qualifier dropped: Line 676 [monitoring_cadence] says “planned use beyond 6 months”, while the ER (lines 335, 394) sets the echocardiogram trigger at “more than 6 months of cumulative use”.
  2. 2.15 — Colloquial wording in lede: Line 433 [at_a_glance] uses “who got the real compound” instead of the formal “received” used in the ER Conclusion (line 436).

Fixes 30/09/2026 04:55

  1. 1.1 — Cumulative-use qualifier restored: Changed [monitoring_cadence] “planned use beyond 6 months” to “planned cumulative use beyond 6 months” to match the ER echocardiogram trigger.
  2. 2.15 — Formal wording in lede: Replaced “who got the real compound” with “who received the real compound” in [at_a_glance]; word count stays at 70.

Issues 30/09/2026 04:54

  1. 1.1 — Unconditional baseline echocardiogram implied: monitoring_cadence (line 676) starts “Baseline before the first dose” for all six markers, whereas the ER Monitoring Protocol limits a baseline echocardiogram to “anyone with a heart murmur or planning more than 6 months of cumulative use”.

Fixes 30/09/2026 04:54

  1. 1.1 — Conditional baseline echocardiogram: Changed monitoring_cadence from “Baseline before the first dose” to “Baseline before the first dose (echocardiogram only with a heart murmur or planned use beyond 6 months)” to match the ER Monitoring Protocol.

Issues 30/09/2026 04:51

  1. 2.15 — Colloquial “magic-mushroom” phrasing: The At a Glance lede (line 433) describes psilocybin as “the magic-mushroom compound” in the document’s own voice, a colloquial term the ER only uses as “so-called magic mushrooms”; formal terminology is required on every surface.

Fixes 30/09/2026 04:51

  1. 2.15 — Colloquial “magic-mushroom” phrasing: Replaced “the magic-mushroom compound” with “a hallucinogenic mushroom compound” in the At a Glance lede, and shortened “Users report feeling better” to “Users report benefits” to stay within 70 words.

Issues 30/09/2026 04:48

  1. 1.3 — Risk severity softened in lede: At-a-glance (line 433) reads “danger with psychotic or bipolar illness or lithium”, dropping the ER Conclusion’s “serious danger” qualifier.
  2. 12.4 — Parenthetical kept in benefits: benefits_low (line 528) retains the parenthetical “creative thinking (originality)” instead of stripping parenthetical content.

Fixes 30/09/2026 04:48

  1. 1.3 — Restored serious-danger qualifier: Changed at-a-glance “danger with psychotic or bipolar illness or lithium” to “serious danger with psychotic or bipolar illness or lithium”, matching the ER Conclusion (70 words).
  2. 12.4 — Removed benefits parenthetical: Changed benefits_low “creative thinking (originality)” to “originality in creative thinking”, preserving the narrow scope without parenthetical content.