Audit: QRS - Eloralintide for Health & Longevity

Audit conducted on 16/09/2026 10: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.	🟢	All protocol figures (3→6 mg week 4, 9 mg week 8; 19.9%/45.8%; 9% and 12%), all 12 monitoring targets, the cadence, both gate lists, all benefit/risk tier items and all 7 qualitative markers trace to ER lines 410–414, 463, 491–516, 348–382, 154–222 and 244–328.
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 framing is carried over, e.g. “Kidney handling of the drug is not yet characterized” (marker_9_why) and “Hepatic impairment studies are still running” (marker_10_why), both verbatim from the ER monitoring table.
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 stay absolute (“Pregnancy, trying to conceive, or breastfeeding”; “Anyone outside a clinical trial”), and the at-a-glance retains “Evidence is manufacturer-funded and under a year; the drug is unapproved”.
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.	🟢	Gates come only from ER Key Interactions & Contraindications; benefits from Expected Benefits; risks from Potential Risks & Side Effects. No modifying-factor content is carried across categories.
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, author names or brand names appear; the drug names in [caution_items] are generic and all present in the same ER bullets (ER lines 348–368).
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind are present outside the fixed template footer and AI4L header line.

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.	🟢	Wording mirrors the ER’s measured, non-promotional register, including the ER Conclusion’s own phrasing (“copying amylin, the fullness hormone”).
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Technical accuracy is retained with plain-language glosses, and actionable targets/cadence give the reader a usable frame without hype.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated descriptively (“Baseline panel before the first injection; … repeated at week 12 and week 24”), never as an instruction to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative or prescriptive verbs appear anywhere in the populated spans.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, “should” or “must” in the document.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns occur in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms that remain (eGFR threshold, Child-Pugh Class C, NYHA Class IV) are decision-gate qualifiers required by items 8.5/9.5; elsewhere plain terms are used (“blood fats”, “average blood sugar”).
2.8	Information is presented in a concise and very compact manner	🟢	Every item is a condensed phrase; ER prose bullets are reduced to their key fact throughout.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” anywhere in the source.
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.	🟢	Optimal functional ranges (hsCRP below 0.5 mg/L, ALT below 25/20 U/L) rather than conventional lab cut-offs address exactly this 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.	🟢	The dense monitoring panel, escalation schedule and body-composition reassessment assume that willingness.
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.	🟢	No simplification toward a general-population framing; 12 biomarkers and a staged escalation schedule are retained.
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.	🟢	The at-a-glance and the first contraindication (“Anyone outside a clinical trial”) foreground the unapproved, trial-only status that defines the signal 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; the title uses “Health & Longevity”.
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.	🟢	Route is always “once-weekly subcutaneous injection” / “injection”; “adverse-event” is used in both the protocol and risk spans; no “shot”/”pill” phrasing.

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”	🟢	Diff against [qrs_template] shows every fixed heading, gate heading, tier label and table header byte-identical.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template span names are present; the enumerated forms marker_1–12name/target/why and qualitative_item_1–7 instantiate the marker#/qualitative_item_# placeholders.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three website= spans (evidence_review, audit, full_review) and all CSS/structure are unchanged from the template.

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; all source sections carry content.
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 labels “Standard regimen”, “Competing approach — maximum efficacy”, “Competing approach — minimum dose” are the ER bold labels verbatim (ER lines 410–414).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Protocol labels and all 12 marker names match the ER exactly; the time-to-effect cells label the three aspects contained in the single ER “Time to effect:” bullet, which provides no per-aspect label of its own.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Character scan returns no emoji; the only non-ASCII symbol is the minus sign in “−10%”.
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 relative to the ER (prose bullets reduced to key facts, tier items reduced to ER headings); the remaining length is driven by the completeness requirements of items 8.2, 9.2, 9.5, 14.2 and 15.2.

---

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: the metadata comment directly follows <!doctype html> and precedes every other element.
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.	🟢	Line 3 opens and line 13 closes the block; the title 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; no metadata value is repeated in head 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:03" 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]”	🟢	Line 4: er_filename: eloralintide_2026-0915-1539_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]”	🟢	Line 5: qrs_prompt_version: 26.9.11, 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)	🟢	Line 6: qrs_creation_date: 2026-0916-1005, 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]”	🟢	Line 7: 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” is a single word with 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]”	🟢	Line 8: 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” is nickname plus version number, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual filename eloralintide_2026-0915-1539_Opus_QRS.html.
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.	🟢	All nine values are trimmed; quoting is used only where YAML requires it.

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 &)	🟢	Line 22: “Eloralintide 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 (e.g., & for &)	🟢	Line 417: “Eloralintide for Health & Longevity”, matching ER frontmatter line 8.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/16/2026”, the correct reformatting of 2026-0916-1005.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “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.	🟢	Header contains only the title and the template subline; the ER’s “Also known as” names are 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	🟢	Line 433 condenses ER lines 546–550: mechanism, dose-dependent benefit, dose-dependent harm, and the evidence limits.
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 sentence of the ER Conclusion (lines 546, 548, 550) and to Practical Considerations line 471 for unapproved status.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “amylin” is glossed as “the fullness hormone” and incretins are rendered as “established weight-loss injections”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year, or sample size appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Direction only (“Weight loss grows with dose”); no percentages or intervals.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All 11 items derive from “Populations who should avoid Eloralintide” (ER lines 370–382).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All 11 ER avoid-populations are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Lines 542–552: 11 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 is stripped, e.g. ER “Anyone outside a clinical trial — eloralintide is investigational…” becomes “Anyone outside a clinical trial”; no dash-led clause remains.
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).	🟢	eGFR below 30 mL/min/1.73 m², Child-Pugh Class C, NYHA Class IV, the 90-day event window and the 27/30 kg/m² thresholds are 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 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 ER names 11 such populations and the section is correspondingly 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 11 items derive from the ER interaction bullets (lines 348–368).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All 11 ER interaction bullets appear; none duplicates a contraindication entry.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 560–570: 11 discrete <li> elements.
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.	🟢	Every ER “Caution — … Mitigation: …” tail is stripped; only the agent/class name and its examples 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).	🟢	All nine example-drug lists are preserved; only the ER’s inline gloss of 5-HTP is trimmed, leaving the drug name itself.
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 ER names 11 interactions and the section is correspondingly 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 derive from ER Therapeutic Protocol lines 410–414.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard regimen, maximum-efficacy alternative and minimum-dose alternative are the ER’s three dosing-decision bullets; the remaining bullets are non-actionable context.
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 supplies three distinct 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.	🟢	Lines 444–473: every label, value and sub carries ER-sourced content, including the 19.9%/45.8% and 9%/12% figures from ER lines 412–414.

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	🟢	Weight change, appetite suppression and per-step steady state are exactly the three intervals the ER gives (lines 463, 418).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Weight change (the sole High benefit) is first, followed by appetite suppression and then the pharmacokinetic steady-state interval.
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 supplies three 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.	🟢	Lines 483–511: “By week 12”, “Within the first weeks” and “About one month” with subs quoting ER lines 463 and 418.
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 11 items are the ER benefit sub-headings (ER lines 154–222).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	Lines 521–532: all four spans present and populated with the matching ER tier.
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 item is the bare ER heading; the magnitude paragraphs (−20%, 17.1 cm, 64% hsCRP) are omitted.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefits span.
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 benefit tiers carry items in the ER, so no span needed hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All 14 items are the ER risk sub-headings (ER lines 244–328).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	Lines 582–593: all four spans present and populated with the matching ER tier.
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 item is the bare ER heading; frequencies (32.7% nausea, 26.9% fatigue, 21% discontinuation) are omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risks span.
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 carry 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	🟢	The table reproduces the ER Monitoring Protocol & Defining Success biomarker table (ER lines 493–506).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 12 ER rows are present in order, with targets and rationale matching verbatim (weight, waist, lean mass, HbA1c, fasting insulin, ApoB, lipid panel, hsCRP, eGFR, ALT, B12/ferritin, blood pressure).
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.	🟢	Line 745 condenses ER line 491: baseline, weeks 4 and 8, weeks 12 and 24, then six-monthly, with body composition at six and twelve months.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Items reproduce the ER’s “Qualitative markers worth tracking alongside the laboratory values” list (ER lines 510–516).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All seven ER qualitative markers are present in the same order (appetite, nausea, energy, physical capability, sleep, mood, bowel regularity).

Issues 16/09/2026 10:12

Pass rate 100.00%. No issues found.