Audit: QRS - LSD for Health & Longevity

Audit conducted on 01/07/2026 18:32 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 91
Failed 0
N/A 0
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 content traces to the ER (Conclusion, Expected Benefits, Risks, Key Interactions, Protocol, Monitoring).
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. 🟢 “signals for depression and cluster headache are weaker” mirrors the ER’s Low grading and hedged framing.
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”). 🟢 Contraindications kept absolute; “recent heart attack <90 days” preserved from 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, interactions, benefits, and risks map to their matching ER 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 citations, NCT IDs, or expert names introduced; drug/brand names shown all appear in the ER.
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. 🟢 Objective, data-driven tone consistent with the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Balanced expert/accessible framing throughout.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence, not directives.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Footer disclaimer present; body presents information.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No recommending/advising language.
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 🟢 Plain language used; technical terms confined to biomarker labels.
2.8 Information is presented in a concise and very compact manner 🟢 Compact card/gate/table layout.
2.9 It DOES NOT address the reader directly 🟢 No direct reader 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 matches the ER’s stated 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. 🟢 Supervised high-dose protocol framing consistent with this 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. 🟢 Content assumes a proactive, protocol-following reader.
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. 🟢 Weighting mirrors the ER’s audience-specific framing.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging”. Proper names that contain “anti-aging” are quoted verbatim. 🟢 Title uses “Longevity”; no “anti-aging” usage.
2.15 The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language. Direct quotes from sources are exempt. 🟢 “lab-made compound” mirrors the ER Conclusion; at-a-glance plain-language wording is permitted.

3. Template Integrity

# Description Result Comments
3.1 The following labels and headings on the QRS are fixed and not modified: card/section headings, gate headings, tier labels, Monitoring table column headers. 🟢 All fixed headings, gate headings, tier labels, and column headers unmodified.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All template variable spans present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Non-content spans unchanged.

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. 🟢 No empty-state phrasing needed; benefits_high correctly hidden via 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. 🟢 Tier labels (High/Medium/Low/Speculative) used verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels faithful to the ER.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). 🟢 No emoji indicators; color conveyed via CSS.
4.5 The QRS is designed to render on one A4 page. Any section with more content than fits is condensed, not extended to a second page. 🟢 Content condensed to fit a single page.

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 the first element after the doctype.
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. 🟢 YAML delimited by — lines (3, 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/trailing whitespace, no surrounding quotes unless required by YAML. 🟢 Values trimmed; duration quoted for the colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: lsd_2026-0701-1516_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.5.18 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-0701-1828
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. 🟢 “Opus” is a single-word nickname.
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
5.11 The full name of the AI consists of the 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: lsd_2026-0701-1516_Opus_QRS.html
5.13 All frontmatter values are trimmed: no leading/trailing whitespace, no surrounding quotes unless required by YAML. 🟢 Values clean and consistent.

6. Page Title & Header

# Description Result Comments
6.1 [page_title] is set to the [canonical_topic] followed by “ - Quick Reference Sheet”. The [canonical_topic] is HTML-entity-encoded as needed. 🟢 “LSD for Health & Longevity - Quick Reference Sheet”.
6.2 [header_topic] is set to the [canonical_topic], with HTML entities encoded as needed. 🟢 “LSD for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 07/01/2026 from 2026-0701.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 4.8”.
6.5 No additional header content appears: no badge, version stamp, AKA line, source-AI attribution, audit date, or QRS variant marker. 🟢 Header limited to title and standard subline.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the ER Conclusion faithfully.
7.2 [at_a_glance] is no longer than 60 words 🟢 59 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Serotonin mechanism, anxiety/alcohol benefits, weaker depression/headache signals, risks, and illegality all trace to the Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 “serotonin signal”, “high-dose session” — no acronyms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial identifiers present.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No statistics present.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from the ER “Populations who should avoid” bullet.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Psychosis/schizophrenia, bipolar, CV disease, pregnancy/breastfeeding.
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, rationale, attributions, citations, study details. No content after an em-/en-/hyphen-dash. 🟢 Concise; no trailing dash clauses.
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, thresholds, staging — ARE preserved, kept concise. 🟢 “uncontrolled hypertension, recent heart attack <90 days” preserved.
8.6 When the ER uses ranking notation inside parens (e.g., “>”), normalize to a plain comma-separated list rather than carrying the bare symbol. 🟢 No ranking notation in the ER contraindications; items are plain lists.
8.7 If no [stop_items] are present the section is left empty 🟢 Contraindications are present and listed.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from the ER interaction bullets.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any already listed as Contraindications 🟢 Lists drug/OTC/supplement/psychedelic interactions; no overlap with contraindications.
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, rationale, attributions, citations, study details. No content after an em-/en-/hyphen-dash. 🟢 Concise; no trailing dash clauses.
9.5 Parenthetical qualifiers — example drug lists, time windows, severity classes, thresholds, staging — ARE preserved, kept concise. 🟢 Example drugs (amitriptyline, sertraline, venlafaxine, phenelzine, psilocybin) preserved.
9.6 When the ER uses ranking notation inside parens (e.g., “>”), normalize to a plain comma-separated list. 🟢 No ranking notation in the ER interactions; items are plain lists.
9.7 If no [caution_items] are present the section is left empty 🟢 Interactions are present and listed.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from the ER Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, Setting, Timing.
10.3 If less than three distinct actionable aspects are mentioned, unused sets are left empty and invisible. 🟢 All three sets have distinct actionable content.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 100–200 μg oral, trained monitor, morning start — all from the Protocol.

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 🟢 Durable benefit, Onset, Session.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Durable benefit (anxiety/mood) leads.
11.3 If less than three distinct time-to-effect aspects are mentioned, unused sets are left empty and invisible. 🟢 Three distinct aspects populated.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Weeks–months, 30–60 min, 8–12 hours (peak 2–4 h) — all from Practical Considerations.
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel 🟢 The ER provides time-to-effect data; section retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Mirrors the ER Expected Benefits tiers.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four variables present.
12.3 Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations. 🟢 Bare descriptors only.
12.4 Parenthetical content — effect sizes, sample notes, mechanistic hints, example studies — is stripped, NOT preserved. 🟢 No parentheticals present.
12.5 If no items of a specific sub-section are present the respective SPAN is set to “display=none”, not filled with empty-state phrasing. 🟢 benefits_high hidden via display:none (no High benefit in the ER).

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Mirrors the ER Risks tiers.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four variables present.
13.3 Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations. 🟢 Bare descriptors only.
13.4 Parenthetical content — frequencies, severity grades, sample notes, mechanistic hints, example studies — is stripped, NOT preserved. 🟢 No parentheticals present.
13.5 If no items of a specific sub-section are present the respective SPAN is set to “display=none”. 🟢 All four tiers have content in the ER; none hidden.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER Monitoring Protocol table.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 Blood pressure, heart rate, anxiety score, depression score, ECG — all five listed.
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 mirrors the ER (baseline/periodic during session; ~1 day, 1–2 weeks, 4–16 weeks).

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER qualitative markers list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Sleep, energy/functioning, cognitive clarity/mood, well-being/outlook, lingering perceptual disturbances — all five listed.

Issues 01/07/2026 18:32

Pass rate 100.00%. No issues found.