Audit: QRS - Uridine for Health & Longevity
Audit conducted on 16/09/2026 03:05 using AI4L / Opus 5
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. | 🟢 | Every span traces to ER text: protocol cells to ER lines 367/377/379, time cells to ER 169/175/404/426, benefits/risks to the ER tier headings, gates to ER 313–343, monitoring to the ER table at ER 458–466. |
| 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. | 🟢 | “continuous human use is untested” mirrors ER 501 “continuous long-term use has never been tested in humans”; “no trial has compared schedules” carried verbatim from ER 377. |
| 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”). | 🟢 | Contraindication and caution assignments match the ER; leflunomide/teriflunomide sits in Contraindications because ER 339 lists it under “Populations who should avoid Uridine”. |
| 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. | 🟢 | No Benefit- or Risk-Modifying Factor appears in the gates; gate content is drawn only from ER Key Interactions & Contraindications. |
| 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 or brand names present. The single named source, “Examine” (line 450), appears in ER 367 for the same dosing fact. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attribution appears that is absent from the ER. |
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, sceptical register of the ER Conclusion is preserved throughout. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Tiered benefits/risks, quantified targets and explicit uncertainty statements throughout. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Descriptive noun phrasing throughout (“Splitting doses above 300 mg into two”), no imperatives. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No directives; monitoring cadence is stated as practice, not instruction. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “recommended”, “advised” or “should” constructions appear. |
| 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 are confined to decision gates and the biomarker table where they are load-bearing; glosses retained where the ER supplies them. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate and tier items are short noun phrases; protocol subs are single sentences. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no “you”/”your” in the document. |
| 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. | 🟢 | Functional biomarker targets and off-period logic address a proactive 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. | 🟢 | Seven-marker panel with baseline/12-week/6–12-month cadence assumes willingness to test and track. |
| 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. | 🟢 | Targets are tighter than conventional clinical cut-offs, as in the ER. |
| 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 lede foregrounds the untested continuous-use question, which is the decision-relevant point 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 appear; 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. | 🟢 | No route-of-administration colloquialism, no “pill”, “shot” or “bad reaction”; lede wording tracks the ER Conclusion (ER 497–501). |
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 present verbatim at lines 440, 477, 519, 539, 553, 574, 593, 597–599, 690 and in the tier <strong> labels. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variable names present; marker_#_* and qualitative_item_# correctly expanded to numbered instances. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | website="evidence_review", website="audit" and website="full_review" spans, the stylesheet link, CSS block and footer disclaimer are byte-identical to 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 that feeds 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. | 🟢 | “Standard supplement dose”, “Single versus split dosing”, “Best time of day” match the ER bold labels at ER 367, 377, 379 exactly. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Protocol labels verbatim; marker names carry the ER biomarker names with only the parenthetical gloss trimmed. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji characters in the file; the ER’s ⚠️ / ⭕️ markers are 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 single-line tier entries or short gate items; no section carries ER prose at full length. |
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. | 🟢 | Single comment at 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 --- at line 3, closing --- at line 13; the descriptive text precedes the opener. |
| 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 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, and it contains a colon requiring it. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: uridine_2026-0916-0010_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-0254. |
| 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. |
| 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” — nickname plus version, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9 matches the file on disk: uridine_2026-0916-0010_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 trimmed; quoting 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: “Uridine 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: “Uridine for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “09/16/2026”, matching qrs_creation_date: 2026-0916-0254. |
| 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” line is 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 497–501: established use, supplement-scale findings and their maker linkage, and the untested continuous-use question. |
| 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 in ER 497–501. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “blood sugar”, “liver fat”, “rodents” and “maker-linked” are non-specialist terms. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | “a single maker-linked trial” characterises the evidence base without naming or dating any trial. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numbers of any kind appear in the lede. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All seven items map to ER 337–343 under “Populations who should avoid Uridine”. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All seven ER avoid-populations are represented, none omitted and none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Seven <li> elements at lines 542–548. |
| 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. | 🟢 | No dashes or trailing clauses; ER 342’s “for whom no human safety data at supplemental doses exist” correctly reduced to “Pregnancy and breastfeeding”. |
| 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 4 weeks of the last dose”, “flare in the past 12 months”, “serum urate above 6.8 mg/dL” and “ALT above twice the upper limit of normal” 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 seven such populations, and the section is correctly populated rather than empty. |
| 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 nine items map to the ER interaction bullets at ER 317–333. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Nine of the ER’s eleven interaction bullets appear; fluoropyrimidines (ER 313) and leflunomide/teriflunomide (ER 315) are correctly omitted as Contraindications. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Nine <li> elements at lines 556–564. |
| 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. | 🟢 | Mechanism and mitigation text stripped throughout; the em-dash gloss in ER 323 (“— drugs that mimic DNA building blocks”) correctly removed. |
| 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 ER example-drug list retained: gemcitabine/cytarabine/capecitabine, allopurinol/benzbromarone, dipyridamole/ticagrelor, zidovudine/stavudine, calcium carbonate, ibuprofen/naproxen. |
| 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 eleven interactions, and the section is correctly populated rather than empty. |
| 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 map to ER Therapeutic Protocol bullets at ER 367, 377 and 379. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose, dose schedule and timing are the three directly actionable bullets; the remaining ER bullets are modifiers or approach descriptions. |
| 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 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 populated; subs reproduce the ER’s own caveats (Examine range, trial regimens, DHA meal pairing, overnight fasting rise). |
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 | 🟢 | Muscle thickness (ER 169/426), dry-eye signs (ER 175) and mood scores (ER 404/426) are the three readouts attached to the highest-tier benefits. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Muscle thickness and dry eye are Medium-tier benefits (in ER order), mood is Low; the Speculative phosphomonoester readout is correctly not selected. |
| 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 more than three 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 populated; each sub traces to ER 169, 175 or 404. |
| 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 (ER 426), so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All thirteen entries correspond one-to-one with the ER benefit headings at ER 157–227. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated at lines 521–532. |
| 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 bare ER heading; no magnitudes, PMIDs or conflict markers carried through. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear 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 ER tiers contain benefits, so no span needs hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All seven entries correspond one-to-one with the ER risk headings at ER 253–293. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated at lines 576–587. |
| 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 bare ER heading; frequencies (35% vs 37%) and the ⚠️ Conflicted marker 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 risk entry. |
| 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 ER tiers contain risks, so no span needs hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows reproduce the ER biomarker table at ER 458–466, including the “Why Measure It?” column verbatim. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All seven ER biomarkers present: fasting glucose, HbA1c, fasting insulin, ALT, serum urate, HDL cholesterol, plasma uridine. |
| 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 684 reproduces ER 456: baseline, 12 weeks, then every 6–12 months with an earlier recheck trigger. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Items taken from the ER’s “Qualitative markers tracked alongside the laboratory panel” list at ER 470–475. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers present verbatim at lines 693–708. |
Issues 16/09/2026 03:05
Pass rate 100.00%. No issues found.
Issues 16/09/2026 02:59
- 2.4 / 2.5 / 2.6 / 2.9 — Imperative dosing instruction: [action_2_value] at line 458 reads “Split doses above 300 mg into two”, an imperative that addresses the reader directly and delivers dosing guidance rather than presenting the ER’s observation at line 377 that “the short half-life favours splitting doses above 300 mg into two”.
Fixes 16/09/2026 02:59
- 2.4 / 2.5 / 2.6 / 2.9 — Imperative dosing instruction: Changed [action_2_value] from the imperative “Split doses above 300 mg into two” to the descriptive “Splitting doses above 300 mg into two”, so the cell presents the ER’s observation instead of addressing the reader with dosing guidance.