Audit: QRS - Microdosing LSD for Health & Longevity
Audit conducted on 04/08/2026 15:44 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 91 |
| Passed | 82 |
| Failed | 0 |
| N/A | 9 |
| 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. | 🟢 | Spot-checked every populated span against the ER: protocol values (ER 376-382), time-to-effect (ER 171,177,425), benefit/risk tier headings, all 10 contraindications (ER 341-350), all 8 caution items (ER 319-337), all 8 markers and cadence (ER 449-460), all 6 qualitative items (ER 464-469). All literally supported. |
| 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: “None demonstrated” for cumulative benefit, “Speculative” tier for valvular disease and HPPD, mirroring the ER’s open-question language. |
| 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 detected; e.g. contraindication list keeps “Known or suspected valvular heart disease of any grade” (ER 344) unweakened. |
| 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 preserved: CYP2D6 genotype stays a monitoring marker (ER 459), not a contraindication; sex/expectancy modifiers are not surfaced as risks. |
| 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 identifiers or brand names in the QRS. All generic drug names in [caution_items] appear in the ER for the same interaction. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind introduced. |
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, sceptical register (e.g. “None demonstrated”, “no lasting gains”). |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert and data-driven (24.3 minutes, 140/90 mmHg, Child-Pugh B/C) while remaining readable. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents thresholds and stopping signals as evidence, not as instructions from a clinician. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperative or prescriptive constructions; grep for recommend/advise/should returns no body-text hits. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Consistently declarative: “Used in all clinical protocols”, “Any recurrent anxiety on dosing days is the primary stopping signal”. |
| 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 | 🟢 | Jargon glossed or replaced; e.g. ER’s “acute chronotropic (heart-rate-raising) response” becomes “acute heart-rate-raising response” in [marker_2_why]. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every span is compressed to headline-level content; no elaboration carried over. |
| 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 depth (echocardiography, CYP2D6 genotyping, hs-CRP, blinded self-check) targets a risk-aware, optimisation-oriented reader. |
| 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 assumes willingness to undertake baseline and annual cardiac imaging, genotyping and daily tracking. |
| 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 at the general population; assumes tolerance for inconvenient and unreimbursed procedures. |
| 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. | 🟢 | [time_3] “Cumulative benefit / None demonstrated” and the cognitive-control decrement are surfaced prominently, which is the audience-appropriate framing. |
| 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; [benefits_speculative] uses “brain aging” per the ER heading. |
| 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 terminology throughout the QRS’s own voice. The plain-language wording in [at_a_glance] is ER Conclusion phrasing and is required by 7.4. |
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 byte-identical to the template: Protocol, Time to effect, Benefits, Risk & Side Effects, Monitoring, Qualitative Assessment, Contraindications, Key Interactions, High/Medium/Low/Speculative, Marker/Target/Why. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 38 template variables present. The 4 repeating variables (marker_#name/target/why, qualitative_item#) are correctly instantiated as marker_1..8 and qualitative_item_1..6. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Diff against the template shows changes only inside spans that a checklist item addresses; CSS, comments, footer disclaimer and website=”…” 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 ER section mapped into the QRS is empty. The empty Benefits/High tier is governed by 12.5, not by this item. |
| 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. | 🟢 | Bold labels reproduced verbatim: protocol labels “Dose range”, “Standard schedules”, “Time of day” (ER 376-382); all 6 qualitative labels (ER 464-469); all 8 biomarker names (ER 453-460). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No label paraphrased or abbreviated. The three time-to-effect labels are derived because the ER carries no bold-labelled time-to-effect list. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji present anywhere in the file; the ER’s tier emoji and the two “⚠️ 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. | 🟢 | Content is condensed relative to the ER rather than extended: marker rationales shortened, caution-item drug lists trimmed, tier items reduced to headings. No section was carried over at ER length. |
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 spans lines 2-14, immediately after <!doctype html> and before any other comment or markup. |
| 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; the descriptive text on line 2 precedes the opening delimiter. |
| 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 and not duplicated by any visible element. |
| 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. | 🟢 | All values trimmed. Only duration is quoted, correctly, because “00:05” contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: microdosing_lsd_2026-0804-1108_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]” | 🟢 | 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) | 🟢 | qrs_creation_date: 2026-0804-1535, correct YYYY-MMDD-HHMM format. |
| 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 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]” | 🟢 | 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 number, no additional qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename matches the file on disk exactly. |
| 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 nine frontmatter 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., & for &) |
🟢 | |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | [header_topic] = Microdosing LSD for Health & Longevity, matching ER canonical_topic (ER frontmatter line 8). |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | qrs_creation_date 2026-0804-1535 renders as 08/04/2026. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | [header_subline_model] = 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. | 🟢 | Subline carries only the template-mandated date, AI4L link and model. No badge, version stamp, alternate-names line or audit date. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Distils the ER Conclusion (ER 493-497): what the practice is, what survives blinding, what does not, the leading stopping reason, and the open long-term question. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 59 words, within the 60-word limit. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause traces to a distinct Conclusion passage; the heart-valve clause is additionally anchored in the Speculative risk (ER 295). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Plain-language throughout: “dummy tablet”, “focused mental control”, “heart-valve safety”. No specialist classifications. |
| 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 effect sizes, confidence intervals or statistics; the 24.3-minute figure is deliberately confined to [time_2_sub]. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from the “Populations who should avoid this intervention” bullet of ER Key Interactions & Contraindications (ER 339-350). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All 10 ER avoid-populations map one-to-one onto the 10 [stop_items]. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Ten discrete <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. | 🟢 | Trailing rationale stripped throughout, e.g. “the standard exclusion applied in current LSD trials” (ER 341) and “given the unresolved 5-HT2B question” (ER 344) are both removed. |
| 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). | 🟢 | Qualifiers preserved: 140/90 mmHg, within 90 days, past 6 months, past 12 months, Child-Pugh Class B or C, Prodromal Questionnaire-16 score of 6 or above. |
| 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 | If no [stop_items] are present the section is left empty | N/A | [stop_items] are present. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from the drug- and supplement-class bullets of ER Key Interactions & Contraindications (ER 319-337). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Eight of the ten ER interaction bullets are carried; MAOIs (ER 321) and lithium (ER 323) are correctly excluded because both already appear in [stop_items]. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Eight discrete <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. | 🟢 | Severity labels, mechanisms, clinical consequences and mitigating actions all stripped; no trailing dash clauses 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). | 🟢 | Named example drugs preserved for every class, trimmed to the longest members that fit (e.g. CYP inhibitors and inducers both retained with named agents). |
| 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 | If no [caution_items] are present the section is left empty | N/A | [caution_items] are present. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Derived from ER Therapeutic Protocol (ER 374-394). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose range, standard schedules and time of day are the three actionable aspects; the remaining ER bullets are modifiers or context, not implementation actions. |
| 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 | Three distinct actionable aspects exist, so 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 action variables populated from ER 376, 378 and 382. |
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 | 🟢 | Same-day mood/wellbeing, post-dose sleep extension and absence of cumulative benefit are the three time-to-effect facts the ER supplies (ER 171, 177, 425). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered Medium-tier mood, then Medium-tier sleep, then the null cumulative finding, matching the ER’s own benefit ordering. |
| 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, so 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 time variables populated with ER-derived content. |
| 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 |
🟢 | Derived from ER Expected Benefits (ER 157-213). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four tier variables present and correctly named. |
| 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 ER sub-heading text only; magnitudes, posterior probabilities, trial descriptions and grading rationale all omitted. |
| 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. | 🟢 | The ER records no High-tier benefit (ER 163), and [benefits_high] is set to style=”display: none” rather than filled with empty-state phrasing. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Derived from ER Potential Risks & Side Effects (ER 233-299). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four tier variables present and correctly named. |
| 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 ER sub-heading text only; the 10% withdrawal rate, d = -0.34 and the 1.1-5.1 h window are all excluded. |
| 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 risk tiers contain items in the ER, so no span needed hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from ER Monitoring Protocol & Defining Success (ER 445-460). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All 8 rows of the ER biomarker table are present, with names and optimal ranges reproduced exactly. |
| 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. |
🟢 | [monitoring_cadence] carries the full front-loaded cadence from ER 449, including the 12-month and annual imaging repeat. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from the qualitative-marker list in ER Monitoring Protocol & Defining Success (ER 462-469). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All 6 qualitative markers present, with the ER’s bold labels verbatim. |
Issues 04/08/2026 15:44
Pass rate 100.00%. No issues found.