Audit: QRS - Epitalon for Health & Longevity

Audit conducted on 30/09/2026 08:21 using AI4L / Opus 5.5

Iterations

Summary

Items Count
Total 94
Passed 86
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. 🟢 Lede, protocol, time-to-effect, gates, tiers, markers and cadence all trace to ER text (Conclusion, Therapeutic Protocol, Practical Considerations, Key Interactions & Contraindications, Monitoring).
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 phrasing kept: “no dose-finding trial behind it”, “no trial has compared morning and evening dosing”, “absorption … is unproven”, “this is anecdotal”, “Possible Cancer Promotion”.
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 found; “Contraindicated during active treatment” and all Caution/Monitor classes match the ER.
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. 🟢 Cancer therapies surfaced as a contraindication because the ER itself labels them “Contraindicated”; no modifying factor relabeled.
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, citations or NCT IDs; brand/product names (TA-65, Thymalin, Vilon, Pinealon) appear in the ER for the same interaction.
1.6 The QRS does not introduce new attributions. 🟢 “almost entirely from its developers” mirrors the ER Conclusion; no new attributions.

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. 🟢 Measured, evidence-weighing tone mirrors the ER Conclusion.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢  
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢  
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Protocol items describe common practice (“Evening injection is common”) rather than prescribing.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢  
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address found.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Lede is plain; acronyms in Monitoring are expanded (CBC, eGFR, HbA1c, hs-CRP, aMT6s, PSA).
2.8 Information is presented in a concise and very compact manner 🟢  
2.9 It DOES NOT address the reader directly 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢 Lede explicitly weighs the cancer risk “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. 🟢 No “anti-aging” wording.
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. 🟢 Routes stated formally (“subcutaneous injection”, “oral / sublingual”, “is injected”); no “shot”, “pill” or “by mouth”.

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 unchanged.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All template spans present; marker_# and qualitative_item_# expanded to 1–8 and 1–6.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Diff against the template shows only addressed variables and display:none on empty tiers changed.

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 QRS section maps to an empty ER section; empty ER tiers (High benefit, High/Medium risk) are governed by 12.5/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. 🟢 Protocol labels (“Common practitioner course”, “Time of day”, “Alternative routes”) and interaction labels are the ER bold labels verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Marker names only expand ER acronyms using the ER’s own Context/Notes text; time-to-effect labels are taken from the ER sentence.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 ER tier emojis and the ⚠️/⭕️ flags 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. 🟢 ER content condensed (monitoring paragraphs reduced to one cadence line, gate items stripped of rationale).

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Metadata comment at line 2, directly 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. 🟢  
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. 🟢  
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 is quoted (“00:02”), which contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: epitalon_2026-0930-0707_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.9.29 matches QRS.md.
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-0930-0808
5.8 The nickname of the AI used to create the document is stated as “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) 🟢  
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 Opus 5.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) 🟢  
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: epitalon_2026-0930-0707_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. 🟢  

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 &) 🟢 “Epitalon 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., &amp; for &) 🟢  
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/30/2026
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Opus 5.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. 🟢  

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 “Epitalon, a lab-made four-amino-acid peptide modeled on a cattle brain-gland extract, is injected in short courses hoping to slow cell aging…”.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses all four Conclusion paragraphs.
7.3 [at_a_glance] is no longer than 70 words 🟢 69 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each fact maps to the ER Conclusion/Motivation (e.g., “sleep hormone melatonin”, “low-cost, plausible but largely unproven add-on”).
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Melatonin glossed as “the sleep hormone”; “add-on” used instead of “adjunct”.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢  
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢  

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢  
8.2 [stop_items] represent the Contraindications from the ER 🟢 All seven ER “Populations who should avoid” bullets plus the ER-labeled “Contraindicated” cancer-therapy interaction.
8.3 Individual [stop_items] are formatted as <li></li> 🟢  
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. 🟢 Rationale stripped (e.g., the WADA category clause, cancer-therapy mechanism).
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). 🟢 5-year window, basal-cell exclusion, gene variants, relative-count threshold and “banned at all times” preserved.
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 ER uses no ranking notation.
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. 🟢 Section populated; ER names populations to avoid.
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 Section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is 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 🟢 The eight non-contraindicated ER interactions are listed; cancer therapies excluded.
9.3 Individual [caution_items] are formatted as <li></li> 🟢  
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. 🟢 Only label and severity class kept (Caution / Monitor / additive).
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 verbatim, including the sulfonylurea gloss.
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 ER uses no ranking notation.
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. 🟢 Section populated; ER names 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 Section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 From ER Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose/course, timing and route are the key actionable Epitalon items; the Russian schedule concerns Epithalamin.
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 ER gives more than three actionable aspects.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢  

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 🟢 The three ER time-to-effect statements (Practical Considerations) are used.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Mortality (Low-tier benefit) > nighttime melatonin (Speculative) > sleep changes (anecdotal).
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 ER gives three time-to-effect aspects.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢  
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 ER provides time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢  
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢  
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. 🟢 ER headings used verbatim, without magnitudes.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢  
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. 🟢 benefits_high set to display: none.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢  
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢  
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. 🟢 ER headings used verbatim; “Conflicted” flag stripped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢  
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. 🟢 risks_high and risks_medium set to display: none.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢  
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight ER table biomarkers listed with verbatim targets.
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. 🟢 Cadence derived from both ER Monitoring paragraphs.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢  
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER qualitative markers listed verbatim.

Issues 30/09/2026 08:21

Pass rate 100.00%. No issues found.

Issues 30/09/2026 08:16

  1. 1.3 / 2.13 — Cancer risk severity softened: At a Glance (line 433) says “The main risk is theoretical”, dropping the ER Conclusion’s “theoretical but serious for this audience”, which softens the risk and removes the audience-specific weighting.

Fixes 30/09/2026 08:16

  1. 1.3 / 2.13 — Cancer risk severity restored: Changed At a Glance “The main risk is theoretical” to “The main risk is theoretical but serious for this audience”, matching the ER Conclusion; rephrased “in hope of slowing/restoring/extending” to “hoping to slow/restore/extend” and “thin and comes almost entirely” to “thin, almost entirely” to stay within 70 words.

Issues 30/09/2026 08:13

  1. 2.7 — Lynch syndrome left unexplained: The Contraindications item “High hereditary cancer risk (BRCA1/BRCA2 or TP53 variants, Lynch syndrome, …)” (QRS line 544) uses “Lynch syndrome” without the plain-language gloss the ER supplies (“inherited colon and uterine cancer predisposition”, ER line 292).

Fixes 30/09/2026 08:13

  1. 2.7 — Lynch syndrome gloss added: In the Contraindications item on hereditary cancer risk, “Lynch syndrome” became “Lynch syndrome [inherited colon and uterine cancer predisposition]”, using the ER’s own gloss.

Issues 30/09/2026 08:10

  1. 1.3 — Optional tests presented as routine: The monitoring_cadence (QRS line 695) drops the ER qualifier that telomere and melatonin tests are “Optional baseline measures” (ER line 365), strengthening them into apparent routine monitoring.

Fixes 30/09/2026 08:10

  1. 1.3 — Optional tests restored as optional: Changed monitoring_cadence from “telomere and melatonin tests only with the same laboratory and method” to “optional telomere and melatonin tests repeated only with the same laboratory and method”, matching the ER wording.