Audit: QRS - Ephedrine for Health & Longevity

Audit conducted on 12/09/2026 08:12 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 83
Failed 0
N/A 10
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. 🟢 Protocol doses, time-to-effect values, contraindications, interactions, biomarkers and cadence all trace to ER Therapeutic Protocol, Practical Considerations, Key Interactions & Contraindications and Monitoring Protocol & Defining Success.
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. 🟢 ER’s “No established numeric target” / “No established target for this purpose” / “No established target” carried verbatim into marker_9/10/11 targets.
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 keep absolute framing; “Pregnancy and lactation” remains a stop item, not a caution.
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. 🟢 Stop items come only from ER “Populations who should avoid Ephedrine”; caution items only from ER interaction bullets; no Benefit-/Risk-Modifying Factor content is surfaced.
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 appear; the only study reference (“the 24-week trial”, time_2_sub) is ER wording for the same fact.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind in the QRS.

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. 🟢 Flat, declarative register matching the ER throughout.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Doses, thresholds and biomarker targets are given plainly with the trade-off stated.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 No directives; content is stated as what the evidence shows.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No “should take”, “consult”, or instruction-form sentences outside the fixed footer disclaimer.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No occurrence of recommend/advise/guidance verbs.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained are the ER’s own and are the shortest accurate form (e.g., “transient ischemic attack”, “pheochromocytoma”).
2.8 Information is presented in a concise and very compact manner 🟢 Every list item is a single clause; no elaborations carried over.
2.9 It DOES NOT address the reader directly 🟢 Confirmed; no “you”/”your”.
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. 🟢 Monitoring targets use optimal-functional ranges rather than conventional reference limits, as the ER does.
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. 🟢 Daily home blood-pressure and heart-rate tracking, split dosing, and a defined energy deficit are presented without hedging.
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. 🟢 Eleven-biomarker panel and three-times-daily schedule assume a committed 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. 🟢 At-a-glance closes on the longevity signal (“nothing in the evidence speaks to lifespan”), the distinction that matters 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. 🟢 “anti-aging” does not occur; “lifespan” and “Longevity” are used.
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 “pill”, “shot”, “taken by mouth”, or “bad reaction”; route of administration is not colloquialised anywhere, including the at-a-glance lede.

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 fourteen fixed strings verified byte-identical to the template (lines 445, 487, 536, 566, 587, 609, 638, 642-644, 783 and the tier labels).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 38 template variable names present; the repeatable marker_#_* and qualitative_item_# placeholders are expanded to 11 marker rows and 6 qualitative items.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 <span website="evidence_review">, <span website="audit"> and <span website="full_review"> are untouched; a structural diff against the template shows no other modification.

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 feeding the QRS is empty.
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. 🟢 action_1/2/3 labels and all ten caution-item labels reproduce the ER bold labels verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Marker names reproduce the ER Biomarker column verbatim; protocol labels reproduce the ER bold labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji code points in the file; the ER’s 🟩/🟥/🟨/⚠️/⭕️ markers were correctly dropped.
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. 🟢 Every section is condensed to its minimum: single-clause list items, stripped parenthetical glosses, and trimmed example-drug lists.

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. 🟢 Lines 2-14, immediately after <!doctype html> on line 1.
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 --- line 3, closing --- line 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; no metadata value is repeated in the header or body.
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. 🟢 Only duration: "00:02" is quoted, and it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: ephedrine_2026-0912-0457_Opus_ER.md (line 4).
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.9.11 matches 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-0912-0750.
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) 🟢 “Opus” — 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) 🟢 “Opus 5” — nickname plus version, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: ephedrine_2026-0912-0457_Opus_QRS.html matches the file 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. 🟢 Re-verified across all nine keys; no stray whitespace or unnecessary 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 &) 🟢 “Ephedrine for Health & Longevity - Quick Reference Sheet” (line 22).
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Ephedrine for Health & Longevity” (line 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0912-0750 → “09/12/2026” (line 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5” (line 425).
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 block (lines 415-428) is the unmodified template subline; the ER’s “Also known as” line was not carried over.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Compresses all three Conclusion paragraphs into mechanism, effect size direction, cost, and horizon.
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. 🟢 Each clause maps to a distinct Conclusion sentence (ER lines 500, 502, 504).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “thermogenic” rendered as “raises the rate at which the body burns calories”.
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 🟢 “real but small” is qualitative; no numbers appear.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All items trace to the ER “Populations who should avoid Ephedrine” list (ER lines 332-345).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All 14 ER items are present, in ER order.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 14 <li> elements inside the span (lines 569-582).
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. 🟢 Plain-language glosses (“(heart attack)”, “(an adrenaline-secreting adrenal tumour)”) and the trailing clause “where safety has not been established” are stripped; no dashes present.
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). 🟢 “within 90 days”, “(160/100 mmHg or above)”, “Class III or IV”, “above 100 mL”, “below 30 mL/min/1.73 m²”, “within the preceding 14 days”, “above 10 µg/mL” all retained.
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 in this list.
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 ER identifies 14 such populations and the section is correctly populated.
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 🟢 All items trace to the ER interaction bullets (ER lines 308-328).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 10 of the ER’s 11 interaction bullets are present; the MAOI bullet is correctly omitted because it appears as a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 10 <li> elements inside the span (lines 590-599).
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. 🟢 All consequence sentences and “Mitigation:” clauses are stripped; no dashes present.
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). 🟢 Every bullet retains its named example agents; lists are trimmed for budget but none is dropped entirely.
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 in these bullets.
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 ER identifies 11 interactions and the section is correctly populated.
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 🟢 All three cells trace to the ER Therapeutic Protocol bullets (ER lines 371-385).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The best-evidenced combination regimen, the ephedrine-alone dose, and the timing/split-dosing schedule.
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 names far more than three actionable aspects; 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 spans carry ER-derived content; no placeholder text remains.

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 🟢 Measurable fat loss (4 weeks), separation from placebo in weight (8 weeks), and stimulant/heat-generating onset (1-2 hours), all from ER Practical Considerations line 425.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Fat loss (High tier) first, the same benefit’s placebo separation second, the thermogenic/energy-expenditure effect (Low tier) 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 provides three or more distinct time-to-effect aspects; 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 spans 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 provides time-to-effect information, so the section is correctly retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All eleven entries match the eleven ER benefit sub-headings across the four tiers.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (lines 538-559).
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. 🟢 Each entry is the ER sub-heading alone; no Magnitude: content carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in any benefit entry.
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. N/A All four tiers have items in the ER.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All ten entries match the ten ER risk sub-headings across the four tiers.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (lines 611-632).
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. 🟢 Each entry is the ER sub-heading alone; no Magnitude: content carried over.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in any risk entry; the ER’s “(tachyphylaxis…)” gloss is stripped.
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 tiers have items in the ER.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Table and cadence trace to ER Monitoring Protocol & Defining Success (ER lines 455-469).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 11 rows of the ER biomarker table are present in ER order, with targets and rationales reproduced.
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. 🟢 Reproduces the ER cadence paragraph (ER line 455) in full.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Items trace to the ER qualitative-marker list (ER lines 473-478).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 6 ER qualitative markers are present, in ER order.

Issues 12/09/2026 08:12

Pass rate 100.00%. No issues found.

Issues 12/09/2026 08:02

  1. 9.4 — Redundant caffeine in interaction item: The first Key Interactions item (line 590) reads “Caffeine and other stimulants (caffeine, guarana, synephrine, yohimbine, DMAA)”, repeating “caffeine” inside the example list after it has already been named in the label.

Fixes 12/09/2026 08:02

  1. 9.4 — Redundant caffeine in interaction item: Removed the duplicated “caffeine” from the parenthetical of the first Key Interactions item, changing “Caffeine and other stimulants (caffeine, guarana, synephrine, yohimbine, DMAA)” to “Caffeine and other stimulants (guarana, synephrine, yohimbine, DMAA)”.

Issues 12/09/2026 07:59

  1. 11.4 — Time-to-effect subs are tautological: All three time_#_sub cells (lines 499, 510, 521) merely restate their own label and value — e.g. label “Measurable fat loss” + value “4 weeks” + sub “Measurable fat loss appears by four weeks.” — so the sub row carries no information the cell does not already show.

Fixes 12/09/2026 07:59

  1. 11.4 — Time-to-effect subs rewritten: Replaced all three tautological time_#_sub cells with ER-traceable context — time_1_sub from “Measurable fat loss appears by four weeks.” to “Only alongside a defined energy deficit; every positive trial imposed one.”; time_2_sub from “Took eight weeks in the 24-week trial.” to “From the 24-week trial, where the caffeine combination beat placebo and ephedrine alone did not.”; time_3_sub from “Felt within one to two hours of the first dose.” to “The half-life runs roughly three to six hours, lengthening when urine is alkaline.”