Audit: QRS - Pterostilbene for Health & Longevity

Audit conducted on 29/09/2026 04:18 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. 🟢 All lede, protocol, time-to-effect, tier, gate, marker and cadence content traces to ER text (e.g., ER lines 145, 320–324, 355, 374–396, 414–418)
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 study compares timing”, “(uncontrolled)”, “no harmful interaction identified”
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 claim strengthened or softened; contraindications mirror ER lines 297–302
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. 🟢 Items stay in their ER categories (interactions, contraindications, benefits, risks)
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 numbers, expert or brand names added
1.6 The QRS does not introduce new attributions. 🟢 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-weighted tone matches ER
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 🟢  
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 direct address found
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical labels (CYP2C9, UGT1A9) are ER bold labels kept verbatim per 4.2
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. 🟢  
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. 🟢 “healthy aging” framing; no “anti-aging”
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 colloquial route or product terms

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, tier labels and column headers present unmodified (lines 440, 477, 519, 539, 552, 576, 595, 599–601, 725)
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All template data-qrs-var spans present
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Diff against template shows changes only inside variable spans

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 is sourced from an empty ER section; empty High tiers 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 and interaction labels match ER bold labels (ER lines 282–293, 320–324)
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢  
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji in 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. 🟢 Content condensed per section (interactions reduced to label + severity, tiers to key facts)

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. 🟢  
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. 🟢 duration quoted because value contains a colon
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢  
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 26.9.28 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) 🟢 2026-0929-0354
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢  
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]” 🟢  
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]” 🟢  
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 &) 🟢  
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/29/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 “Pterostilbene is a dietary supplement … of interest for healthy aging”
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢  
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. 🟢  
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢  
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 six ER populations (ER lines 297–302) listed
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 “(no safety data)” stripped
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). 🟢 Thresholds kept (≥190 mg/dL, under 18 years, below 90/60 mmHg)
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. 🟢 ER names populations to avoid; section populated
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A Section 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 🟢 All 12 ER interactions listed
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. 🟢  
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
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. 🟢  
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 not empty

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢  
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard dose, NAD+ combination, time of day
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 provides more than three 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 🟢 Blood pressure, liver enzymes, menopause symptoms (ER line 355)
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Medium-tier benefit first, then Low-tier in ER order
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 provides at least three 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. 🟢  
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 hidden with 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. 🟢  
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 hidden with 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 10 ER biomarkers listed
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. 🟢  

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 6 ER qualitative markers listed

Issues 29/09/2026 04:18

Pass rate 100.00%. No issues found.

Issues 29/09/2026 04:14

  1. 8.4 — Rationale kept in contraindications: The pregnancy/breastfeeding and under-18 contraindications (lines 542-543) retain the explanatory parenthetical “(no safety data)”, which is a rationale rather than a threshold or time-window qualifier and should be stripped.

Fixes 29/09/2026 04:14

  1. 8.4 — Rationale removed from contraindications: Removed the explanatory parenthetical “(no safety data)” from the pregnancy/breastfeeding and under-18 contraindication items.

Issues 29/09/2026 04:12

  1. 1.1 — Blood-pressure dose claim overgeneralized: Protocol action_1_sub (line 450) says “blood pressure lowered only at 250 mg/day”, dropping the ER’s qualifier “Pterostilbene alone” (ER line 320); the ER also reports 50 mg twice daily plus grape extract lowered systolic pressure (ER line 145).

Fixes 29/09/2026 04:12

  1. 1.1 — Blood-pressure dose claim qualified: Changed action_1_sub from “blood pressure lowered only at 250 mg/day” to “pterostilbene alone lowered blood pressure only at 250 mg/day”, matching the ER Therapeutic Protocol wording.

Issues 29/09/2026 04:09

  1. 7.5 — Unexplained technical compound name: The at_a_glance text (line 433) calls pterostilbene “a berry-derived relative of resveratrol” without explaining resveratrol, a chemical name a non-specialist would not know; the ER glosses it as “the red-wine compound”.

Fixes 29/09/2026 04:09

  1. 7.5 — Resveratrol explained in plain language: Changed “a berry-derived relative of resveratrol” to “a berry-derived relative of the red-wine compound resveratrol” (ER gloss), and tightened two phrases (“a modest blood-pressure drop”, “weaker liver-health hints”) to stay within the 70-word limit.

Issues 29/09/2026 04:05

  1. 1.1 — Cholesterol risk overgeneralized: At a Glance (QRS line 433) says “a rise in cholesterol”, while the ER Conclusion (ER line 418) specifies a rise in “bad” cholesterol and the ER notes HDL fell at 250 mg/day (ER line 234).

Fixes 29/09/2026 04:05

  1. 1.1 — Cholesterol risk wording aligned: Changed At a Glance from “a rise in cholesterol” to ‘a rise in “bad” cholesterol’ to match the ER Conclusion (still 70 words).

Issues 29/09/2026 04:03

  1. 2.15 — Colloquial cholesterol term in lede: The At-a-Glance (line 433) says “a rise in “bad” cholesterol”, consumer-grade phrasing in the document’s own voice; the ER’s own wording “rise in cholesterol” is plain and non-colloquial.

Fixes 29/09/2026 04:03

  1. 2.15 — Colloquial cholesterol term in lede: Replaced “a rise in “bad” cholesterol” with the ER wording “a rise in cholesterol” in the At-a-Glance.

Issues 29/09/2026 04:00

  1. 4.2 / 4.3 — Stilbene interaction label abbreviated: The Key Interactions item at line 563 reads “Resveratrol and other stilbene supplements”, dropping the gloss from the ER bold label “Resveratrol and other stilbene (resveratrol-family plant compound) supplements” and leaving “stilbene” unexplained.

Fixes 29/09/2026 04:00

  1. 4.2 / 4.3 — Stilbene interaction label restored: Changed the Key Interactions item from “Resveratrol and other stilbene supplements: Monitor” to the ER’s verbatim bold label “Resveratrol and other stilbene (resveratrol-family plant compound) supplements: Monitor”.

Issues 29/09/2026 03:57

  1. 1.3 — Risk signal hedge dropped: At a Glance (line 433) says “The most consistent risk is a rise in ‘bad’ cholesterol”, while the ER Conclusion (line 418) says “The most consistent risk signal”, strengthening the ER’s claim.
  2. 2.7 — Unexplained NRPT acronym: The Monitoring “Why” cell for whole-blood NAD+ (line 712) reads “NRPT response”; NRPT is not expanded anywhere on the sheet.

Fixes 29/09/2026 03:57

  1. 1.3 — Restored risk signal hedge: Changed At a Glance “The most consistent risk is a rise” to “The most consistent risk signal is a rise”, matching the ER Conclusion (70 words).
  2. 2.7 — Expanded NRPT acronym: Changed the whole-blood NAD+ “Why” cell from “NRPT response” to “Nicotinamide riboside + pterostilbene response”.