Audit: QRS - Ayahuasca for Health & Longevity

Audit conducted on 30/06/2026 17:33 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

Note: The QRS.md prompt declares [total_items] = 71, but the checklist as written enumerates 91 distinct items (sections 1–15). The audit was performed against the actual 91 enumerated items.


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 (at-a-glance, protocol, time-to-effect, benefits, risks, contraindications, interactions, monitoring, qualitative) traces to ER passages.
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 (e.g., “durability beyond uncertain”, “Speculative” tier matches ER Speculative sections).
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/softening; pregnancy and serotonergic-med items kept as contraindications.
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 drawn from ER Key Interactions & Contraindications; risks from Potential Risks; categories preserved.
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, expert names, 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. 🟢 Cautious, evidence-graded tone matches ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert yet accessible framing maintained.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence without prescribing.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Descriptive of research/clinical practice, not advice to reader.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Informational framing throughout.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address; cadence verbs mirror ER’s descriptive protocol language.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms expanded or avoided where appropriate.
2.8 Information is presented in a concise and very compact manner 🟢 Cells and bullets are compact.
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 fits proactive, risk-aware 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 detail (washout, screening, supervision) 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. 🟢 Not pitched to general population.
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 reflects target audience.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging”. Proper names that contain “anti-aging” are quoted verbatim. 🟢 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. 🟢 “Bad trips” is the ER’s own risk title (verbatim); otherwise formal register used.

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.
3.2 All “” from the [qrs_template] are present in the QRS. 🟢 All expected data-qrs-var spans present, including hidden benefits_high.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 No unaddressed spans altered.

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” 🟢 benefits_high (empty High tier) set to display:none rather than filled, consistent with empty-state handling.
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/monitoring labels derive from ER content.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels faithful to 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 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. 🟢 Content condensed to single-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 after doctype.
5.2 Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. 🟢 YAML delimited correctly.
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. 🟢 Inside HTML comment; not rendered.
5.4 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless required by YAML. 🟢 Values trimmed; duration quoted appropriately (contains colon).
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: ayahuasca_2026-0630-1528_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 is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” 🟢 qrs_creation_date: 2026-0630-1528.
5.8 The nickname of the AI 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” — single word.
5.10 The full name of the AI is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 qrs_creator_ai_fullname: Opus 4.8.
5.11 The full name consists of the nickname and the model version number and no additional qualifier 🟢 “Opus 4.8” — nickname + version.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: ayahuasca_2026-0630-1528_Opus_QRS.html.
5.13 All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless required. 🟢 All values clean.

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. 🟢 “Ayahuasca 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. 🟢 “Ayahuasca for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 “06/30/2026” from 2026-0630.
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 / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Header limited to title and subline; no extra content.

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 449-453).
7.2 [at_a_glance] is no longer than 60 words 🟢 56 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to ER Conclusion passages.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain-language only (“mind-altering compound”, “substances from a vine”); no acronyms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial citations.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER lines 298-312.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All ER contraindications present (psychosis/bipolar, CVD, pregnancy/breastfeeding, liver disease, serotonergic meds, monoamine-affecting agents).
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. 🟢 Items are bare facts; no trailing dash clauses.
8.5 Parenthetical qualifiers from the ER bullet — time windows, severity classes, threshold values, clinical staging — ARE preserved, kept concise. 🟢 “<90 days”, “Child-Pugh Class B or C”, “uncontrolled hypertension, serious arrhythmia” preserved.
8.6 When the ER uses ranking notation inside parens that depends on an explanatory phrase, normalize to a plain comma-separated list. 🟢 No ranking notation; lists are plain comma-separated.
8.7 If no [stop_items] are present the section is left empty 🟢 stop_items present, so condition does not trigger; section correctly populated.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER lines 298-311.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any already listed as Contraindications 🟢 Antidepressants (absolute contraindication/serious caution), tyramine foods, serotonin precursors, additive supplements, alcohol/other drugs listed; contraindication framed distinctly as “without completed washout”.
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/rationale/attributions/citations/study details. No content after an em/en/hyphen dash. 🟢 Items are concise; no trailing dash clauses.
9.5 Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved, kept concise. 🟢 Example drug lists preserved (SSRIs, SNRIs, MAO inhibitors, tricyclics, St. John’s Wort; 5-HTP, L-tryptophan, SAMe; high-dose yohimbine).
9.6 When the ER uses ranking notation inside parens, normalize to a plain comma-separated list. 🟢 No ranking notation; plain lists used.
9.7 If no [caution_items] are present the section is left empty 🟢 caution_items present; condition does not trigger; section correctly populated.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from ER Therapeutic Protocol (lines 332-356).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Research-clinical dose, best time of day, single vs. split dosing — the key actionable aspects.
10.3 If less than three distinct actionable implementation aspects are mentioned, the unused sets are left empty and made invisible. 🟢 Three aspects present; condition does not trigger.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three action cells fully populated from 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 🟢 Mood/well-being onset, acute onset, acute resolution.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Mood/well-being benefit (Medium tier, highest present) placed first; acute pharmacology timings follow.
11.3 If less than three distinct time-to-effect aspects are mentioned, the unused sets are left empty and made invisible. 🟢 Three aspects present; condition does not trigger.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All three time cells populated from ER (lines 344, 387).
11.5 If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel 🟢 ER provides time-to-effect data; section correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from ER Expected Benefits (lines 164-208).
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. 🟢 Benefit items are bare key facts.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals in benefit items.
12.5 If no items of a sub-section are present the respective is set to “display=none”, not filled with empty-state phrasing. 🟢 benefits_high (no High benefits in ER) set to display:none.

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 (lines 226-280).
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. 🟢 Risk items are bare key facts.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 The only parentheticals (“vomiting and diarrhea”, “bad trips”) are the ER’s own risk-title clarifiers, not frequencies/grades/samples/mechanism/studies.
13.5 If no items of a sub-section are present the respective is set to “display=none”, not filled with empty-state phrasing. 🟢 All four tiers populated in ER; condition does not trigger.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from ER Monitoring Protocol (lines 409-423).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All five ER table markers present (BP, RHR, ALT/AST, CMP, Medication review).
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 populated from ER line 423.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from ER qualitative markers (lines 425-431).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five qualitative markers present (mood, anxiety/rumination, well-being, substance use, tolerability).

Issues 30/06/2026 17:33

Pass rate 100.00%. No issues found.

Issues 30/06/2026 17:27

  1. 12.3 / 12.4 — Qualifier not stripped in benefits: benefits_medium (QRS line 525) keeps the parenthetical qualifier “(conflicted)” on the depression item; the tier already encodes evidence strength, so this qualifier is redundant detail that 12.3/12.4 require to be stripped.

Fixes 30/06/2026 17:27

  1. 12.3 / 12.4 — Qualifier not stripped in benefits: Removed the redundant “(conflicted)” qualifier from benefits_medium so the depression item reads “Reduction of depressive symptoms” with no parenthetical.