Audit: QRS - Pterostilbene for Health & Longevity

Audit conducted on 30/06/2026 03:40 using AI4L / Opus 4.8

Iterations

Summary

Items Count
Total 91
Passed 86
Failed 0
N/A 5
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 QRS content traces to ER passages (protocol, benefits, risks, monitoring, interactions).
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. 🟢 “Mechanistically interesting but clinically unproven” mirrors ER conclusion (line 426); cautious framing preserved.
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/breastfeeding kept as contraindication; LDL risk kept; no strengthening/softening.
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. 🟢 Contraindications, interactions, benefits, risks all map to their corresponding ER sections.
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, expert names, or brand names appear in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No attributions 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. 🟢 Objective, cautious, evidence-graded tone matches the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert yet plain-language tone maintained throughout.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents evidence; no prescriptive directives.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Footer disclaimer present; content presents information, not advice.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommend”/”advise” framing in body.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Jargon expanded or avoided (e.g., “bad cholesterol”).
2.8 Information is presented in a concise and very compact manner 🟢 Compact card/table layout; concise items.
2.9 It DOES NOT address the reader directly 🟢 No direct reader address present.
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-optimization framing throughout.
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. 🟢 Monitoring/protocol detail assumes a proactive audience.
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. 🟢 Content depth targets the optimization audience, not the general public.
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. 🟢 LDL risk and BP benefit weighted for a CV-risk-aware longevity 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. 🟢 “Longevity” used; no “anti-aging” phrasing in the QRS voice.
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. 🟢 Uses “adverse events”, “blood pressure”, “LDL cholesterol”; “bad” cholesterol is parenthetical gloss for plain language.

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/labels match template (lines 440, 477, 519, 566, 585, 660, 539, 549, 589-591).
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All expected data-qrs-var spans present.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Template “website” spans and structural spans left intact.

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” 🟢 Empty High benefit/risk tiers handled by display:none per 12.5/13.5, not empty-state text; consistent with ER having no High items.
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/benefit/risk labels match ER labels.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Labels preserved (e.g., “Blood pressure reduction”, “Increased LDL”).
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji indicators present; tiers conveyed via bold labels.
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. 🟢 Interactions and benefits condensed to fit single-page budget.

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 is first element (lines 2-14).
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. 🟢 YAML delimited by — (lines 3, 13).
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 HTML comment; not rendered.
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 quoted (contains colon); all others trimmed/unquoted.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: pterostilbene_2026-0630-0211_Opus_ER.md (line 4).
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 qrs_prompt_version: 26.5.18 (line 5).
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 qrs_creation_date: 2026-0630-0211 (line 6).
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 qrs_creator_ai_nickname: Opus (line 7).
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” — single 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]” 🟢 qrs_creator_ai_fullname: Opus 4.8 (line 8).
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 4.8” — nickname plus version, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: pterostilbene_2026-0630-0211_Opus_QRS.html (line 9).
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. 🟢 Frontmatter values clean and consistent.

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 &) 🟢 “Pterostilbene for Health & Longevity - Quick Reference Sheet” (line 22).
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 “Pterostilbene for Health & Longevity” (line 417).
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 “06/30/2026” (line 421), matching 2026-0630.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 4.8” (line 425).
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 title and subline; no extra content.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Condenses the Conclusion (ER lines 422-426).
7.2 [at_a_glance] is no longer than 60 words 🟢 54 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Blueberry-derived, better absorption, broad preclinical promise, BP down/LDL up, unproven — all in Conclusion.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain language; “bad” cholesterol used instead of LDL acronym standalone.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names/years/sizes cited.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from “Populations who should avoid or use caution” (ER line 286).
8.2 [stop_items] represent the Contraindications from the ER 🟢 Pregnancy/breastfeeding, LDL/CVD, liver impairment all map to ER.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Three <li> items (lines 542-544).
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. 🟢 “given the LDL signal” rationale stripped; no trailing dash clauses.
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 90 days”, “NYHA Class III–IV”, “Child-Pugh Class C” preserved.
8.6 When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. 🟢 No bare ranking symbols carried through.
8.7 If no [stop_items] are present the section is left empty N/A Contraindications are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from ER interaction bullets (lines 272-284).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Antihypertensives, lipid-lowering, BP-lowering supplements, polyphenols, CYP/UGT drugs; no contraindication overlap.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Five <li> items (lines 552-556).
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. 🟢 Severity/mitigation text stripped; no trailing dash clauses.
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). 🟢 Drug examples preserved (ACE inhibitors, ARBs, CCBs, statins, CYP3A4 substrates, etc.).
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. 🟢 No bare ranking symbols carried through.
9.7 If no [caution_items] are present the section is left empty N/A Key interactions are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Dose, formulation, timing from ER Therapeutic Protocol (lines 304-322).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Standard Dose, Formulation, Timing & Frequency.
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 Three actionable aspects are present.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All three sets populated with ER-derived content.

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 (6–8 wk), NAD+ (4 wk), Liver enzymes (6 mo).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Blood pressure (Medium tier) first, then Low-tier NAD+ and liver markers.
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 Three time-to-effect aspects are present.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All three sets populated with ER-derived content.
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 🟢 Maps to ER Expected Benefits (lines 140-192).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four variables 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. 🟢 Bare descriptors; magnitudes/details stripped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 “(as part of nicotinamide riboside combination)” etc. stripped.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 benefits_high set display:none (no High benefit in ER); others populated.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Maps to ER Potential Risks (lines 212-252).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four variables 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. 🟢 Bare descriptors; details stripped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Only the “(bad)” gloss on LDL retained as plain-language aid; magnitudes stripped.
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 set display:none (no High risk in ER); others populated.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Maps to ER Monitoring Protocol table (lines 383-389).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All five ER biomarkers present (LDL; Total/HDL/triglycerides; BP; glucose/HbA1c; ALT/GGT).
14.3 [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. 🟢 Cadence populated (line 654), matching ER lines 381-382.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Drawn from ER qualitative markers (lines 393-396).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All four qualitative markers present (energy/tolerance, cognition/mood, wellbeing, new symptoms).

Issues 30/06/2026 03:40

Pass rate 100.00%. No issues found.

Issues 30/06/2026 03:36

  1. 13.4 — Parenthetical not stripped in risks: risks_speculative (line 578) retains the parenthetical “(CYP/UGT)” in “Drug-metabolism (CYP/UGT) interactions”; per 13.4 parenthetical content in risk items must be stripped.

Fixes 30/06/2026 03:36

  1. 13.4 — Strip parenthetical in risks: Removed the “(CYP/UGT)” parenthetical from the risks_speculative item, changing “Drug-metabolism (CYP/UGT) interactions” to “Drug-metabolism interactions”.