Audit: QRS - 9-Methyl-β-Carboline for Health & Longevity

Audit conducted on 06/09/2026 06:00 using AI4L / Opus 5

Summary

Items	Count
Total	93
Passed	85
Failed	0
N/A	8
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.	🟢	Verified line by line against the ER: protocol figures (5-50 mg, 7-21 days, 10-14 day course), gate items, biomarker targets and at-a-glance facts all trace to ER text.
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 ER phrasing carried over verbatim, e.g. “No validated human protocol exists”, “Undetermined”, “No pharmacokinetic study exists”.
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; “Caution to contraindication” items stay in Key Interactions, absolute contraindications stay in 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.	🟢	No Benefit- or Risk-Modifying Factor is surfaced as a gate or side effect; all gate items come from the ER interactions/contraindications 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.	🟢	No PMIDs, study names, author names, NCT identifiers or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions 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 cautious, evidence-scarcity framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert, objective and data-driven while remaining accessible.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence and observed practice rather than instructing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No advisory or prescriptive constructions.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Information is presented; passive/descriptive constructions used throughout (e.g. “Evening dosing is avoided because…”).
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person address anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language; jargon limited to necessary biomarker names.
2.8	Information is presented in a concise and very compact manner	🟢	Compact throughout; ER bullets condensed to single clauses.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” in the rendered content.
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 a risk-aware, proactive longevity 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.	🟢	Content assumes willingness to follow inconvenient measures (UV avoidance, low-tyramine diet, laboratory panels).
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 written for the 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 the audience, foregrounding the blank human column against the documented chemical hazards.
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.	🟢	No “anti-aging” phrasing; only “anti-inflammatory” appears, in a biomarker rationale.
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 clinical terminology used in the document’s own voice; the deliberately plain wording in At-A-Glance is required by item 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, gate headings, tier labels and Monitoring column headers match the template exactly.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variables present; marker_#* and qualitative_item# expanded to the seven and five instances required.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A full diff against the template shows no change outside the variable spans.

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 that maps to a QRS field is empty with an empty-state phrasing; the empty ER benefit/risk tiers are handled under items 12.5 and 13.5.
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.	🟢	ER bold labels reused verbatim as cell/row labels (“Self-experimentation range”, “Best time of day”, “Competing approaches without a default”, “Time to effect”, “Half-life”, “Interaction washout on stopping”, and all five qualitative labels).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No paraphrased or invented labels.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators present.
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 to the per-section budget: gate items are single clauses, benefit and risk tiers collapsed to one line each, and biomarker rationales trimmed to the ER’s “Why Measure It?” text.

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.	🟢	HTML comment opens at line 2, immediately after “<!doctype html>”.
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.	🟢	YAML delimited by “—” at lines 3 and 13, inside the comment.
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.	🟢	Metadata is inside an HTML comment and is not surfaced elsewhere.
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, which is required because the value contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: 9_methyl_carboline_2026-0906-0404_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-0906-0553, correct 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.
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)	🟢	Nickname plus version number, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename matches the actual filename on disk.
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 clean and consistent.

#	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 `&`)	🟢	“9-Methyl-β-Carboline for Health & Longevity - Quick Reference Sheet”, with the ampersand entity-encoded.
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 matches the ER canonical_topic with & encoding.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/06/2026, correctly derived from qrs_creation_date 2026-0906-0553.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	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.	🟢	No badge, version stamp, alternate-names line, audit date or variant marker in the header.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER `Conclusion` section	🟢	Dense distillation of the ER Conclusion covering the mechanism claims, the absent human evidence, the conflict of interest and the two concrete hazards.
7.2	[at_a_glance] is no longer than 60 words	🟢	55 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct passage in the ER Conclusion (paragraphs 1-3).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Plain-language substitutions used throughout: “genetic material” for DNA, “laboratory-made molecule”, “blocked dopamine breakdown”; no acronyms.
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 or statistics.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	Derived from the ER “Key Interactions & Contraindications” section, including its “Populations who should avoid” list.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All ten ER avoid-list populations plus the absolute-contraindication serotonergic supplements from the interaction bullets are represented, eleven items in total.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is a separate <li> inside the [stop_items] 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.	🟢	Items reduced to the key fact; ER glossary asides such as “an inherited defect in repairing ultraviolet damage” stripped. 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 and classes preserved: “within 14 days”, “at or above 140/90 mmHg”, “Child-Pugh Class B or C”, “eGFR below 30 mL/min/1.73 m²”.
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	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 section is populated, and the ER does identify populations that should avoid the intervention.
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	🟢	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	🟢	Eight caution items; MAOIs, serotonergic antidepressants, tramadol/meperidine and the five contraindicated serotonergic supplements are correctly excluded and the mixed ER bullets split accordingly.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each item is a separate <li> inside the [caution_items] 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.	🟢	Mechanistic rationale and mitigation text from the ER bullets removed; 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 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 preserved for every item (amphetamine/methylphenidate/pseudoephedrine/phenylephrine/ephedrine, dextromethorphan, sumatriptan/rizatriptan, carbidopa-levodopa/pramipexole/ropinirole, and the tyramine food list).
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	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 section is populated, and the ER does identify 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	The section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER `Protocol` section	🟢	Derived from the ER “Therapeutic Protocol” section.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Dose, timing and course pattern are the three actionable aspects; the remaining ER bullets are contextual rather than actionable.
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 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 action variables carry ER-derived content; each sub retains the ER’s caveat about the absent human evidence.

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	🟢	Time to effect, half-life and interaction washout are the three time-related aspects the ER provides.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered with the cognitive time-to-effect result first, matching the only benefit for which a time course was measured.
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 time variables carry 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 the ER “Expected Benefits” section.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four benefit variables present.
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.	🟢	The five speculative benefits are reduced to their ER subheading wording, with no elaboration or citation.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content carried over.
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.	🟢	High, Medium and Low spans are set to display: none, matching the ER where no benefit reaches those tiers.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	Derived from the ER “Potential Risks & Side Effects” section.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four risk variables present.
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.	🟢	The five speculative risks are reduced to their ER subheading wording.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content carried over.
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.	🟢	High, Medium and Low spans are set to display: none, matching the ER.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Derived from the ER “Monitoring Protocol & Defining Success” section.
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All seven biomarkers from the ER table are listed with their optimal ranges and rationales.
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.	🟢	Populated with the ER cadence: baseline, two weeks, six weeks, then every three to six months, with home blood pressure twice weekly.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Derived from the ER “Monitoring Protocol & Defining Success” section.
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All five qualitative markers listed with the ER’s bold labels verbatim.

Issues 06/09/2026 06:00

Pass rate 100.00%. No issues found.