Audit: QRS - Rutin for Health & Longevity
Audit conducted on 15/08/2026 09:56 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. | 🟢 | All protocol cells, tier entries, gate items, biomarker rows and qualitative items trace to ER text (Therapeutic Protocol, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications, Monitoring Protocol & Defining Success, Conclusion). |
| 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 wording is carried over where present, e.g. marker_9_target “No established target; track change from the individual’s own baseline in millimetres” and marker_8_why “Tracks the metabolic claim that human trials have so far failed to confirm”. |
| 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”). | 🟢 | Pregnancy and breastfeeding remain in the Contraindications gate, not in Key Interactions; action_3_sub retains “a different molecule” rather than implying the venous trial evidence applies to plain rutin. |
| 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-Modifying or Risk-Modifying Factor appears in the gates or risk card; each QRS section draws from its matching ER section. |
| 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 identifiers, author names or brand names (Venoruton, Paroven, Relvène, Swanson, Solaray) appear anywhere in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind are 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. | 🟢 | The measured, deflationary register of the ER (“Support is narrow”, “Nothing about rutin is acute”, “Where they occurred at all”) is preserved. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Quantified doses, ranges and targets sit alongside an actionable close (“The calculation differs for those already managing swollen legs”). |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated descriptively (“The dose used in the only well-controlled human trial”), not prescribed. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives or directives; the footer disclaimer defers any decision to a qualified clinician. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No instances of “recommended”, “advised”, “should” or equivalent directive framing. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are limited to those required for fidelity (cytochrome P450 3A4, P-glycoprotein, estimated glomerular filtration rate); the At-A-Glance is entirely plain. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Tier entries are bare noun phrases; gate items carry no trailing rationale; biomarker rows carry only marker, target and reason. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Consistently third person (“Those on anticoagulants add a clotting-time check”, “the individual’s own baseline”). |
| 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, self-tracked qualitative measures and interaction gates address a proactive, risk-aware 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. | 🟢 | A nine-marker baseline panel, staged rechecks and daily symptom scoring assume a reader willing to invest 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. | 🟢 | Nothing is simplified to general-population reassurance; the monitoring and interaction detail exceeds general-population framing. |
| 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 closes on exactly this divergence: “The calculation differs for those already managing swollen legs.” |
| 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” and the speculative tier uses “Healthspan and lifespan extension”. |
| 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Formal terms throughout (gastrointestinal upset, hypersensitivity, platelet aggregation, non-heme iron); plainer wording in the At-A-Glance is required there by item 7.4 and is taken verbatim from the ER Conclusion. |
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 table column headers match the template byte for byte. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 38 template variable names are present; marker_#* is instantiated nine times and qualitative_item# six times. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The three non-variable spans (website=”evidence_review”, website=”audit”, website=”full_review”) and the footer disclaimer are unchanged; a normalised diff against the template shows no structural divergence. |
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. |
| 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. | 🟢 | action_1_label “Standard supplemental dose”, action_2_label “Time of day” and action_3_label “Conventional pharmaceutical approach” match the ER Therapeutic Protocol bold labels verbatim (ER lines 350, 352, 358). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Time-to-effect labels take their wording from the ER prose (“venous symptom relief”, “Biomarker changes”, “Nothing about rutin is acute”); biomarker names are the ER table’s own row labels. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji characters occur; the ER’s tier emojis and “⚠️ Conflicted” markers were 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 the minimum the checklist permits: tier entries reduced to bare headings, gate items stripped of rationale, biomarker rows reduced to the ER’s own short “Why Measure It?” clause with the Context/Notes column dropped entirely. |
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. | 🟢 | The comment opens at line 2, immediately after <!doctype html> on line 1, and closes at line 14 before any other content. |
| 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 and closing --- at line 13; the preceding label text sits outside the block. |
| 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. | 🟢 | It lives entirely inside an HTML comment and is not duplicated 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. | 🟢 | All values are trimmed and unquoted except duration: "00:03", which contains a colon and therefore requires quoting. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: rutin_2026-0815-0554_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.7.02, matching this prompt’s 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-0815-0949, 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, with no trailing qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: rutin_2026-0815-0554_Opus_QRS.html, matching 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. | 🟢 | Confirmed across all nine keys, including the appended git_user and git_issue 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., & for &) |
🟢 | Line 22: “Rutin for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic with the ampersand encoded. |
| 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: “Rutin for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/15/2026”, the correct reformatting of 2026-0815-0949. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”, matching the frontmatter value. |
| 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 contains only the title and the template’s own subline; the ER’s “Also known as” list 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 |
🟢 | It compresses all three Conclusion paragraphs: the absorption problem, the narrow venous and haemorrhoid support, the animal-only findings, and the audience divergence. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 57 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to ER lines 467–471; “well-tolerated” maps to “this well tolerated” at ER line 471. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | “quercetin” is rendered as “a related compound”, “chronic venous insufficiency” as “where veins drain poorly”; no acronyms appear. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, sample sizes or p-values. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numeric results; “modestly” carries the magnitude qualitatively. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All five items come from the “Populations who should avoid Rutin” list at ER lines 324–328. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All five ER contraindications are present, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Five discrete <li> elements at QRS lines 564–568. |
| 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 ER’s trailing rationales (“given the unresolved topoisomerase-related genotoxicity signal”, “given the interaction margin”) and the leading “Anyone with/within” are stripped; no dash-trailing 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). | 🟢 | The threshold “platelets below 50,000 per microlitre” and the windows “within 7 days of planned surgery” and “within 14 days of a major operation” 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. |
| 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 five such populations and the section is correspondingly populated, not 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 come from the bulleted interaction list at ER lines 302–318. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Nine of the ER’s ten interaction bullets are carried; the tenth (“Other interventions (compression therapy, exercise)”) is correctly omitted because the ER classifies it as “no interaction”. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Nine discrete <li> elements at QRS lines 576–590. |
| 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/monitor” verdict and its mitigation prose is stripped; only the agent or class name plus its parenthetical remains. |
| 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 seven parenthetical drug lists are preserved; only “including nirmatrelvir” is trimmed inside the CYP3A4 parenthetical, which itself is retained in full otherwise. |
| 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 nine such interactions and the section is correspondingly populated, not 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 derive from the ER “Therapeutic Protocol” bullets at lines 350, 352 and 358. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose, timing and the drug-grade alternative are the three decision-relevant levers; the remaining ER bullets are modifiers or attribution rather than actions. |
| 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 cells carry substantive ER-derived content; no placeholders remain. |
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 | 🟢 | Venous symptom relief, biomarker changes and the absence of acute effects are exactly the three aspects the ER states at line 402. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Venous symptom relief, the ER’s only High-tier benefit, leads; biomarker changes follow; the null acute case is last. |
| 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 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. | 🟢 | “4–8 weeks”, “6–12 weeks” and “None” with their subs all match the ER wording at line 402. |
| 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 eleven entries are the ER’s own benefit headings from lines 148–214. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans are present and populated at QRS lines 536–554. |
| 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 a bare heading-level noun phrase; no magnitude text, certainty language or mechanism is carried across. |
| 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 items, so none needed hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All eight entries are the ER’s own risk headings from lines 236–286. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans are present and populated at QRS lines 602–619. |
| 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 a bare heading-level noun phrase; the ER’s magnitude figures and mechanism paragraphs are not carried across. |
| 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 items, so none 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 at lines 430–440. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All nine ER biomarkers are present in ER order: ferritin, haemoglobin, platelet count, alanine aminotransferase, estimated glomerular filtration rate, thyroid-stimulating hormone, high-sensitivity C-reactive protein, fasting glucose, ankle circumference. |
| 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. |
🟢 | QRS lines 767–771 reproduce the ER cadence at lines 426–428: baseline, 12 weeks, then every 6–12 months, with the anticoagulant and thyroid-replacement add-ons. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All six items come from the ER “Qualitative markers worth tracking alongside the labs” list at lines 444–449. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six are present in ER order and wording: leg symptoms, night cramps, visible bruising, haemorrhoidal symptoms, digestive comfort, energy and general wellbeing. |
Issues 15/08/2026 09:56
Pass rate 100.00%. No issues found.