Audit: QRS - ECA for Health & Longevity

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

Iterations

Summary

Items	Count
Total	94
Passed	85
Failed	0
N/A	9
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, time-to-effect, benefit, risk, contraindication, interaction, monitoring and qualitative content all trace 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.	🟢	marker_12_target carries the ER’s “No established target” wording; no ER hedge is dropped.
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; “cycling is not required” stays scoped by the “Cycling for efficacy” label.
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 come from the ER avoid-list plus the two bullets the ER itself calls absolute contraindications; modifying factors are not 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, author names or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions beyond the template’s fixed AI4L link.

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.	🟢	Sober, balanced register matching the ER Conclusion.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Benefits and risks are presented side by side without alarm or promotion.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Statements describe trial practice (“Trials dosed pre-meal”) rather than prescribing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No advisory verbs; monitoring rows state what a marker detects, not what to do.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrences of “recommend”, “advise” or “should”.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the sheet.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms carry plain glosses (e.g., “Overactive thyroid”, “prior myocardial infarction” with lay framing in the gate list).
2.8	Information is presented in a concise and very compact manner	🟢	All gate items, benefit/risk lines and monitoring rows are single compact fragments.
2.9	It DOES NOT address the reader directly	🟢	Confirmed; no direct 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.	🟢	Optimal functional ranges and a 12-row monitoring panel assume a proactive reader.
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.	🟢	Three-times-daily dosing, DEXA and a front-loaded lab cadence are presented without hedging on burden.
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 casual use.
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 aspirin trade-off and the age-70 mortality signal are both carried into the Risks card.
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 appear.
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.	🟢	The lede uses “oral drugs”; no “pill”, “shot” or “taken by mouth” anywhere.

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 twelve fixed strings are byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Every template variable name is present; marker_#* and qualitative_item# are expanded to 12 and 8 numbered instances respectively.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three website= spans, the head/CSS block and the footer disclaimer 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 source ER section is empty; the ER uses neither empty-state phrasing.
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.	🟢	“Standard regimen”, “Adding the third agent”, “Best time of day” and “Cycling for efficacy” are the ER’s bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring markers and tier labels match the ER; the two Time-to-Effect labels split the ER’s single “Time to effect” bullet into its two distinct facts, as Section 11 requires.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji present; the ER’s ⚠️ Conflicted markers are stripped.
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.	🟢	Item counts are mandated by 8.2 / 9.2 / 14.2 / 15.2; each item is condensed to its minimum fragment with rationale, dose detail and citations stripped.

---

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 form the first comment after the doctype.
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 “—” at line 3, closing “—” at 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 value is repeated in the 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, correctly, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: eca_2026-0912-1640_Opus_ER.md at 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.22 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-0922-1650.
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” is a single word.
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” carries no extra qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: eca_2026-0912-1640_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.

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 &)	🟢	“ECA 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 &)	🟢	“ECA for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0922-1650 → “09/22/2026”.
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.	🟢	The header block is structurally identical to the template.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence	🟢	Opens “ECA is three inexpensive, long-established oral drugs — ephedrine, caffeine and aspirin — used together for fat loss.”
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses the first two Conclusion paragraphs into effect, durability, lipid change and the direction of harm.
7.3	[at_a_glance] is no longer than 70 words	🟢	64 words.
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a Conclusion sentence.
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“Cholesterol readings”, “heart rate”, “blood pressure”; no specialist term.
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial is named.
7.7	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers other than none at all.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All 17 items trace to that ER section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All 16 ER “Populations who should avoid ECA” bullets plus the two bullets the ER labels absolute contraindications (MAOIs/linezolid merged, anticoagulants/antiplatelets).
8.3	Individual [stop_items] are formatted as <li></li>	🟢	17 <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.	🟢	The Reye-syndrome rationale, the mortality clause and the ≥180/105 trial aside are all stripped; no trailing dash clauses remain.
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).	🟢	≥160/≥100 mmHg, >100 mL residual, eGFR <45, Child-Pugh B/C, 14 days, <50 kg with 75–100 mg, and 10 µg/mL 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 in this section; every “>” or “<” is a numeric threshold.
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 many 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 12 items trace to that ER section.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	12 of the ER’s 14 interaction bullets; the two absolute-contraindication bullets are correctly routed to the stop gate instead.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	12 <li> elements inside the 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.	🟢	Every “avoid / caution / monitor” verdict, mechanism and mitigation sentence is stripped; only the agent class 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 named drug and supplement lists are carried through; only the ER’s lay glosses of drug classes are trimmed.
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 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 many 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.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard regimen and ratio, the aspirin decision including the co-equal two-agent variant, and dose timing.
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 provides well over three; 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 variables carry ER-derived content; no placeholder 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	🟢	Fat-loss separation at week 8, acute thermic/appetite onset at 1–2 hours, and persistence to 50 weeks.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Fat loss (High tier) first, then the two Low-tier thermic/appetite and persistence facts.
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 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 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 provides time-to-effect data in Practical Considerations and Discontinuation & Cycling.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All ten entries are ER benefit headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four present; High 4 items, Low 5 items, Speculative 1 item.
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 heading phrase; no magnitude line is carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	“(Aspirin Component)” is stripped from both the cardiovascular and colorectal entries.
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.	🟢	The ER states “No benefit reaches Medium”; [benefits_medium] carries style="display: none" with no content.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All thirteen entries are ER risk headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four present and populated; High 7, Medium 1, Low 4, Speculative 1.
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 heading phrase; no hazard ratio or frequency is carried over.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	“(Aspirin Component)” is stripped from the bleeding and mortality entries.
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 at least one ER item.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows mirror the ER Monitoring Protocol & Defining Success biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 12 ER table rows are present, in ER order, with their optimal functional ranges intact.
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’s front-loaded schedule: daily for two weeks, weekly, 6-week panel, 3-month full panel then 6-monthly, body composition every 12 weeks.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Taken from the ER’s “Qualitative markers worth tracking alongside the laboratory values” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All 8 ER qualitative markers are present, in ER order.

Issues 22/09/2026 17:06

Pass rate 100.00%. No issues found.

Issues 22/09/2026 16:58

1. 4.2 / 4.3 — Invented Time to Effect label: time_3_label at line 525 reads “Durability”, but its value and sub-text are taken verbatim from the ER bullet “Cycling for efficacy:” (ER line 455); the ER’s own bold label was available and should have been used unchanged.
2. 4.5 — Sheet overflows one A4 page: Content was transcribed at ER volume rather than condensed. The Contraindications gate wraps to roughly 34 lines (~180 mm) and the 12-row Monitoring table to ~127 mm, which alone exceed the 273 mm printable height of an A4 page before the header, At-A-Glance, Protocol, Benefits, Risks and Qualitative blocks are added; the Monitoring “Why” cells, monitoring_cadence (lines 874-879) and the Protocol/Time sub cells (lines 470-473, 484-487, 504-507) each carry full ER sentences.

Fixes 22/09/2026 16:58

1. 4.2 / 4.3 — Time to Effect label restored: Changed time_3_label from the invented “Durability” to the ER’s own bold label “Cycling for efficacy” (ER line 455).
2. 4.5 — Contraindications gate condensed: Tightened all 17 stop_items without dropping any item or qualifier — e.g. “estimated glomerular filtration rate” to “eGFR”, “Atrial fibrillation or another abnormally fast heart rhythm” to “Atrial fibrillation or other fast heart rhythm”, “Monoamine oxidase inhibitor use within the past 14 days” to “Monoamine oxidase inhibitors within 14 days”.
3. 4.5 — Key Interactions gate condensed: Trimmed the example lists on the over-the-counter and other-interventions items while keeping every ER bold label verbatim and every named drug or exposure.
4. 4.5 — Protocol and Time to Effect sub-cells condensed: Shortened all three action_#_sub and all three time_#_sub cells from full ER sentences to fragments, e.g. time_1_sub from “Separation from placebo in weight became statistically detectable from week 8…” to “Weight separated from placebo from week 8…”.
5. 4.5 — Monitoring column and cadence condensed: Shortened nine marker_#_why cells, the DEXA marker_12_target, and monitoring_cadence (335 to 258 characters) so the 12-row table and its cadence line occupy fewer wrapped lines. All 12 biomarkers, their targets and the full cadence schedule are retained.