Audit: QRS - hTERT Gene Therapy for Health & Longevity

Audit conducted on 27/09/2026 21:58 using AI4L + evidence-mcp / GPT 6

Iterations

Summary

Items Count
Total 94
Passed 87
Failed 0
N/A 7
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. 🟢 Claims map to the named ER’s Conclusion, therapeutic protocol, benefit/risk headings, interactions, and 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. 🟢 Unproven benefit, unknown duration, absent targets, experimental administration, and precautionary cancer framing remain explicit.
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 efficacy or safety claim is strengthened; cognition remains an uncontrolled combination finding.
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. 🟢 Benefits, adverse effects, avoidance populations, and interactions retain their ER 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. 🟢 Libella, named medicines, TA-65, and cycloastragenol occur in the ER for the same facts.
1.6 The QRS does not introduce new attributions. 🟢 No new expert or study attribution is introduced.

2. Focus, Tone & Audience

# Description Result Comments
2.1 The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing. 🟢 Retains the ER’s experimental, uncertainty-aware framing.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Presents practical evidence and limitations objectively and accessibly.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Research information is presented without individualized treatment directions.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No personalized clinical instructions are introduced.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Describes documented research procedures and available evidence.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Variable content does not address the reader; fixed template disclaimer is retained.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Terms use plain descriptions, with hTERT and AAV explained in the body.
2.8 Information is presented in a concise and very compact manner 🟢 Compact protocol cells, short gates, tier lists, and condensed monitoring rows.
2.9 It DOES NOT address the reader directly 🟢 No direct address in authored variable content.
2.10 The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. 🟢 Longevity benefits and research limitations are framed for health-focused adults.
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. 🟢 Includes experimental administration and prolonged follow-up without assuming low 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. 🟢 Focus remains proactive longevity use and product-specific research requirements.
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. 🟢 Human longevity uncertainty and delivery-related risks remain prominent.
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. 🟢 Uses longevity terminology; no anti-aging framing.
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. 🟢 Uses formal route and adverse-effect terminology, including intravenous administration.

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 card, gate, tier, and table labels match the template.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All template data-qrs-var anchors are retained, including marker_# and qualitative_item_#.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Populated variable anchors are covered by explicit checklist items.

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 applicable empty source section is surfaced; absent tiers use their specific hiding rule.
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 and interaction labels preserve ER bold labels; qualitative labels are retained.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Benefit, risk, protocol, interaction, and monitoring labels reproduce ER labels.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No visible emoji indicators occur in the QRS.
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. 🟢 A4 print rules, compact typography, short content, and preserved print grids support a single-page design; source-only assessment.

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 immediately follows 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. 🟢 One opening and one closing YAML delimiter occur inside the metadata comment.
5.3 The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. 🟢 Frontmatter is in an HTML comment and is not duplicated as a metadata display.
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. 🟢 Values are trimmed; the quoted duration contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename names the supplied source ER.
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 matches 26.9.27.
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 uses 2026-0927-2151.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 Creator nickname is present as GPT.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 GPT is a single unversioned model 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]” 🟢 Creator fullname is present as GPT 6.
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) 🟢 Fullname combines GPT and version 6 without qualifiers.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename exactly matches the target basename.
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. 🟢 No unneeded quotation or whitespace in metadata values.

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 &) 🟢 Title matches canonical_topic plus the required suffix; ampersand is encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Header topic matches canonical_topic with ampersand encoded.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/27/2026 matches the creation date.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Header model matches GPT 6.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Only the fixed header and required variable content appear.

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 with gene therapy supplying cellular instructions to preserve tissue renewal.
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses rationale, unresolved combination evidence, harms, reversibility, and uncertainty from Conclusion.
7.3 [at_a_glance] is no longer than 70 words 🟢 The lede contains fewer than 70 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each lede statement corresponds to the source Conclusion.
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Uses plain descriptions without specialist acronyms or classifications.
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial identifiers, sample sizes, dates, or statistical tests.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numerical effect sizes or statistical findings.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Avoidance entries derive from Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All four source avoidance populations are represented.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Every avoidance entry uses li tags.
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. 🟢 Entries retain key eligibility facts and the cancer precaution qualifier without mechanistic explanation.
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). 🟢 Preserves contraception requirements, seven-day window, clinical significance, and protocol exceptions.
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 No severity-ranking notation appears in source avoidance bullets.
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. 🟢 Nonempty source avoidance list is represented.
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 Contraindications are not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All entries derive from the source interaction section.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All seven interaction classes appear without duplicating avoidance populations.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Every interaction entry uses li tags.
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. 🟢 Content is limited to labels, named agents, and relevant procedure/exposure qualifiers.
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). 🟢 Named example medicines and spinal/invasive procedure qualifiers are retained.
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 No severity-ranking notation appears in source interactions.
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. 🟢 Nonempty source interaction list is represented.
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 Key Interactions are not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Regimen status, Libella administration, and timing derive from Therapeutic Protocol.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Covers absent validated regimen, documented route/frequency, and absent maintenance/timing rules.
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 At least three distinct implementation aspects are available and used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 Every used action label, value, and subtext contains relevant supported protocol information.

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 🟢 Covers the only described time to useful effect: cognition over months; no typical time exists.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 The sole human benefit timing occupies the first slot.
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. 🟢 Unused time slots two and three are empty and hidden.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Cognition timing and its uncertainty derive from Practical Considerations and Expected Benefits.
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.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 One Low and eight Speculative benefits match Expected Benefits.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four prescribed benefit variables are present.
12.3 Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. 🟢 Only concise benefit descriptors appear.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical study or effect-size content remains in benefit tiers.
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. 🟢 Empty High and Medium tiers use display: none with no empty-state text.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Seven Low and three Speculative risk descriptors match Potential Risks & Side Effects.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four prescribed risk variables are present.
13.3 Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact. 🟢 Risk tiers contain concise descriptors only.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical frequency, severity, or study detail remains in risk tiers.
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. 🟢 Empty High and Medium risk tiers use display: none without empty-state text.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows and cadence derive from Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All seven source table markers, relevant pregnancy testing, and urine testing are represented.
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. 🟢 Includes baseline, weeks 1/4/13/26/39/52, earlier acute surveillance, and multiyear follow-up.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Qualitative content derives from the three monitoring bullets.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 Daily function, stamina, recovery, sleep, energy, clarity, pain, and new sensory/systemic symptoms are retained.

Issues 27/09/2026 21:58

Pass rate 100.00%. No issues found.

Issues 27/09/2026 21:54

  1. 2.7 — Unexplained gene-therapy abbreviations: Protocol and Monitoring use “hTERT” without a plain-language explanation; Key Interactions uses “AAV” in “Previous AAV exposure” without explaining the viral delivery vehicle. These abbreviations reduce accessibility for the intended non-specialist audience.

Fixes 27/09/2026 21:54

  1. 2.7 — Explain gene-therapy abbreviations: Added a plain-language explanation of hTERT in Protocol and expanded AAV with its viral gene-delivery meaning in Key Interactions.