Audit: QRS - Fisetin for Health & Longevity

Audit conducted on 09/09/2026 07:07 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 85
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. 🟢 Verified item by item against the ER: protocol cells map to ER Therapeutic Protocol bullets (lines 374, 378, 384, 390); time cells to Practical Considerations line 433 plus the 12-week trial durations at lines 167/173; all 13 monitoring targets and “why” strings are verbatim from the ER table (lines 465-477); cadence from line 461; qualitative items from lines 481-486; benefits/risks from the ER tier sub-headings; gates from lines 321-352.
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 phrasing is carried through: “No established target — track the change from the individual’s own baseline” (marker_13_target), “Not expected”/”Nothing subjective has been shown to change on any timescale” (time_3), “theoretical antiplatelet effect” (marker_11_why), “unproven in people” (at_a_glance).
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 strengthening or softening found. ER contraindication “Pregnancy and lactation” is carried as an absolute, not downgraded; “Active cancer treatment, unless the treating oncologist has approved it” is reproduced verbatim; “Severe hepatic impairment (Child-Pugh Class C)” keeps the severity class.
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. 🟢 All gate items originate in the ER Key Interactions & Contraindications section; no Benefit-Modifying Factors or Risk-Modifying Factors content is surfaced as a caution or side effect, and no Risk Mitigation Strategies bullet is relabelled.
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, no NCT identifiers, no study citations, no expert names and no brand names appear in the QRS. The only institutional references, “Mayo Clinic protocol” (action_1_sub) and “Copenhagen group’s trial” (action_2_sub), are present in the ER for exactly those facts (ER lines 374 and 378).
1.6 The QRS does not introduce new attributions. 🟢 No new attributions introduced; both institutional attributions are the ER’s own.

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. 🟢 Tone matches the ER’s sceptical, evidence-weighted register — the at_a_glance mirrors the ER Conclusion framing of an unreplicated mouse finding and thin human data.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert and data-driven (numeric targets, dose schedules, exposure ratio) while remaining accessible; the framing is decision-enabling rather than dismissive — it states what is cheap, tolerated and measurable alongside what is unproven.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Content is presented as evidence and measurable ranges; no prescriptive instruction to a patient.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No clinical advice language. Gate items are stated as conditions, not directives, and the cadence field reports the ER’s stated practical cadence.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommend”, “advise”, “you should” or equivalent appears anywhere in the document.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 Verified by search: no second-person pronouns (“you”, “your”, “yourself”) and no first-person plural (“we”, “our”) occur in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language in the narrative voice; technical terms that do appear (suPAR, HOMA-IR, eGFR, CYP2C8, thrombolysis) are unavoidable biomarker and interaction names taken verbatim from the ER.
2.8 Information is presented in a concise and very compact manner 🟢 Every field is compressed to a label plus key fact; gate and tier items carry no explanatory tails.
2.9 It DOES NOT address the reader directly 🟢 Confirmed — the reader is never addressed; all statements are impersonal.
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. 🟢 Content is pitched at proactive, risk-aware adults: intermittent high-dose and continuous low-dose schedules, a formulation-exposure comparison, and a 13-marker panel.
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. 🟢 Presents a monthly pulsed protocol, pre-procedure-relevant gates, and a laboratory panel — all of which assume willingness to undertake inconvenient, costly 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. 🟢 Not written for the general population: it assumes access to hs-CRP, interleukin-6, suPAR and epigenetic-age testing and to bioavailability-enhanced formulations.
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. 🟢 Risk/benefit weighting reflects the audience — the at_a_glance flags that the human signals came “mostly in people with illness or excess weight”, the distinction that matters most for a healthy optimiser.
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. 🟢 Verified by search: the strings “anti-aging” and “antiaging” do not occur. The document’s own voice uses “Longevity” (page title, header) and “human aging pilot” / “animal aging program”.
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 terminology throughout (“adverse events”, “hepatic impairment”, “antihypertensives”, “lactation”). The at_a_glance use of “blood sugar” is the ER Conclusion’s own wording (ER line 518) and is required by item 7.4’s plain-language rule.

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 strings verified unmodified: “Protocol” (line 445), “Time to effect” (491), “Benefits” (539), “Risk & Side Effects” (618), “Monitoring” (645), “Qualitative Assessment” (784), “Contraindications” (567), “Key Interactions” (587), tier labels High/Medium/Low/Speculative in both tier cards, and “Marker”/”Target”/”Why” (649-651).
3.2 All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. 🟢 Programmatic comparison of data-qrs-var names against [qrs_template]: all 34 fixed-name spans are present. The only template names absent are the repeating patterns marker_#name/target/why and qualitative_item#, which are instantiated as marker_1..13_* and qualitative_item_1..6 (45 spans), giving 79 spans in total.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Non-variable template scaffolding is untouched: the three hooks (lines 423, 426, 439), the header subline wording, the “Time to Effect row (4 cells, 2x2)” comment, the footer disclaimer and the entire stylesheet 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 section of the source ER is empty — Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications, Therapeutic Protocol and Monitoring Protocol & Defining Success all carry content, so no empty-state phrasing is called for. The ER’s High benefit tier and High/Medium risk tiers contain explanatory prose but no tier items, which items 12.5 and 13.5 govern instead.
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 are the ER’s bold labels verbatim: “Intermittent high-dose schedule”, “Continuous low-dose schedule”, “Formulation matters more than dose” (ER lines 374, 378, 390). Monitoring row labels are the ER biomarker-table names verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No paraphrased or abbreviated labels. The three time-to-effect labels (“Inflammatory markers”, “Metabolic markers”, “Felt effects”) are taken from the wording of the ER’s single Time to effect bullet (“Inflammatory and metabolic markers … felt effects”, ER line 433), whose own bold label is already used as the panel subhead.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 Verified by search: no 🟩, 🟥, 🟨 or other emoji indicators occur. The ER’s tier emoji and “⚠️ Conflicted” markers were correctly dropped; tiering is conveyed by the bold High/Medium/Low/Speculative labels and the card CSS palettes.
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 rest of this checklist permits: tier cards carry bare ER sub-headings, gate items carry no explanatory tails, qualitative items are stripped of their ER rationale clauses, and at_a_glance sits at 58 of its 60-word budget. No content is duplicated or extended beyond what items 8.2, 9.2, 12.2, 13.2, 14.2 and 15.2 mandate.

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 metadata comment opens on line 2, immediately after “<!doctype html>” on line 1, and precedes the template comment on line 16 and the <html> element on line 17.
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. 🟢 Line 2 carries the permitted pre-YAML text “QRS — Metadata (invisible, parsed by audit tooling)”; the YAML opens with “—” on line 3 and closes with “—” on line 13, inside the comment that ends on line 14.
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. 🟢 The block is wholly inside an HTML comment and no element on the sheet reproduces any of its values except header_subline_date and header_subline_model, which items 6.3 and 6.4 require.
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 nine values are trimmed and unquoted except “00:03” for duration, which is correctly quoted because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: “er_filename: fisetin_2026-0909-0434_Opus_ER.md”, which matches the ER audited.
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 the version badge at the top of 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) 🟢 Line 6: “qrs_creation_date: 2026-0909-0659”, a well-formed YYYY-MMDD-HHMM value.
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 the nickname plus the version number, with no additional qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9: “qrs_filename: fisetin_2026-0909-0434_Opus_QRS.html”, which matches the file’s actual name 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. 🟢 Re-verified: no leading or trailing whitespace and no unnecessary quoting on any value; only the colon-bearing duration value is quoted.

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 &) 🟢 Line 22: “Fisetin for Health & Longevity - Quick Reference Sheet” — the ER’s canonical_topic “Fisetin for Health & Longevity” with the ampersand entity-encoded, followed by the required suffix.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Line 417: header_topic is “Fisetin for Health & Longevity”, the canonical_topic with the ampersand encoded.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “09/09/2026”, which is qrs_creation_date 2026-0909-0659 rendered as MM/DD/YYYY.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: header_subline_model is “Opus 5”, matching qrs_creator_ai_fullname.
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. No badge, version stamp, AKA / alternate-names line (the ER’s five alternate names are not reproduced), source-AI attribution beyond the template’s own model slot, audit date, or variant marker.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 at_a_glance condenses all four paragraphs of the ER Conclusion (lines 516-522): the unreplicated mouse survival finding, the small and short human data, tolerability, and the closing “a bet on a mechanism” verdict.
7.2 [at_a_glance] is no longer than 60 words 🟢 58 words, within the 60-word limit.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each fact maps to a distinct ER Conclusion passage — the non-reproduction to line 516, the inflammation/blood-sugar/body-weight signals and the ill-or-overweight populations to line 518, tolerability to line 520, and the cheap/unproven/mechanism-bet verdict to line 522.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms and no technical classifications. Specialist terms are replaced with plain equivalents: senescent cells are not mentioned at all, the Interventions Testing Program becomes “the largest independent animal aging program”, and glucose control becomes “blood sugar”.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial name, year, sample size or p-value. The two study references are deliberately unnamed (“one mouse survival finding”, “the largest independent animal aging program”), matching the ER Conclusion’s own anonymised phrasing.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, relative risks, confidence intervals or statistical results; the outcomes are given only as directions (“improved”).

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eight items come from the “Populations who should avoid Fisetin” list in the ER Key Interactions & Contraindications section (ER lines 343-352).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All eight ER contraindications are present, in ER order: pregnancy/lactation, urushiol-family allergy, bleeding disorders/low platelets, scheduled surgery, severe hepatic impairment, advanced kidney disease, under-18s, active cancer treatment.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Lines 570-582: each item is its own <li>…</li> inside the [stop_items] span.
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. 🟢 All trailing ER clauses after em-dashes are stripped: “— no reproductive toxicity data exist at supplemental doses” (pregnancy), “— conjugation and biliary excretion are the primary clearance routes” (hepatic), and “, in whom senescent-cell burden is low and no data exist” (under-18s). No attributions, citations or study details 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). 🟢 Every decision-relevant qualifier survives: the urushiol example list, “below 100 ×10⁹/L”, “within 14 days”, “(Child-Pugh Class C)”, “(eGFR below 30 mL/min/1.73 m²) outside a supervised trial”, and “unless the treating oncologist has approved it”. The ER’s inline gloss “a calculated measure of kidney filtration” was trimmed, not the threshold.
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’s contraindication bullets use no ranking notation inside parentheses — the only parenthetical content is an allergen example list and a Child-Pugh class, and the eGFR and platelet thresholds are written out in prose (“below 30”, “below 100”), so no normalisation is required.
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 section is populated, which is correct: the ER names eight populations and scenarios that should avoid fisetin or use it only under supervision.
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. <!– empty: ER names no population that should avoid the intervention –> N/A The section is not empty — it carries eight items — so no empty-state HTML comment is required.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eleven items come from the bulleted interaction list in the ER Key Interactions & Contraindications section (ER lines 321-341).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All eleven ER interaction bullets are present in ER order. None duplicates a contraindication: the ER’s own “Active cancer treatment, unless the treating oncologist has approved it” gate and its “Cytotoxic chemotherapy and radiotherapy” interaction bullet are distinct entries in the ER and are kept distinct here.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Lines 590-608: each item is its own <li>…</li> inside the [caution_items] span.
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. 🟢 Each item is reduced to the ER’s bold label alone. All “Caution.”/”Monitor.” severity words, mechanistic rationale, “Consequence:” clauses, “Mitigation:” clauses and the clinicaltrials.gov link attached to the acid-blocker bullet are stripped.
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 example drug list is preserved in full, e.g. “(paclitaxel, repaglinide, montelukast, rosiglitazone, amiodarone)”, “(warfarin, apixaban, clopidogrel, aspirin)”, “(fish oil, ginkgo, garlic, nattokinase, high-dose vitamin E)”, “(dasatinib plus quercetin)”.
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’s interaction bullets use no ranking notation inside parentheses — every parenthetical is a plain comma-separated list of example agents — so no normalisation is required.
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 section is populated, which is correct: the ER names eleven interactions and additive effects that change how fisetin 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. <!– empty: ER names no interaction that changes how the intervention is used –> N/A The section is not empty — it carries eleven items — so no empty-state HTML comment is required.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three action sets derive from the ER Therapeutic Protocol section (ER lines 374, 378, 384, 390).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The three chosen aspects are the load-bearing implementation decisions in the ER: which schedule to run at high dose, the alternative continuous low-dose schedule, and the formulation question the ER itself flags as dominating dose (“label milligrams are close to meaningless”). The remaining ER bullets are descriptive context (half-life, competing approaches, commercial dose, pharmacogenetics, sex, age).
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 Therapeutic Protocol section lists fourteen bullets, well above three distinct actionable aspects, so all three sets are in use and none needed to be emptied or hidden.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All nine fields carry ER-derived content: the 20 mg/kg × 2 days monthly Mayo schedule with its 1,400 mg/70 kg equivalent, the 100 mg × 7 weeks Copenhagen schedule with its senomorphic intent, and the 192 mg hydrogel versus 1,000 mg powder 27-fold exposure gap with the morning fat-containing-meal default.

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 🟢 The ER’s time-to-effect information (ER line 433) resolves into exactly three aspects, all three of which are represented: inflammatory markers, metabolic markers, and felt effects.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordering follows benefit magnitude as tiered in the ER: “Lower Systemic Inflammation” is the first ER Medium benefit and leads here, the metabolic cluster follows as the next Medium benefit, and felt effects — which the ER ties to no benefit at all — come 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 time-to-effect aspects, so all three sets are in use and none needed to be emptied or hidden.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All nine fields are populated from the ER: “7–12 weeks” and “Moved over 7 to 12 weeks in the trials that measured them” (ER line 433), “12 weeks” for the metabolic cluster measured in the 12-week obesity RCTs (ER lines 167, 173), and “Not expected” / “Nothing subjective has been shown to change on any timescale” (ER line 433).
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 does provide time-to-effect information (Practical Considerations, ER line 433), so the row was correctly retained rather than removed from the protocol panel.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All tier content derives from the ER Expected Benefits section sub-headings (ER lines 153-227).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans are present at lines 541, 544, 550 and 553.
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 ER sub-heading alone, semicolon-separated. No mechanisms, trial descriptions, sample sizes, “Magnitude:” figures or citations are carried over, and the ER’s “⚠️ Conflicted” markers are dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Nothing parenthetical is carried through — the ER benefit sub-headings contain no parentheses, and the explanatory parentheticals inside the ER’s body text (e.g. “(hs-CRP, a general marker of body-wide inflammation)”, “(a calculated index of insulin resistance)”) are absent from the QRS.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 Line 541: benefits_high carries style=”display: none” with no content after the tier label, correctly reflecting the ER’s “No benefit reaches High” statement rather than importing empty-state phrasing. Medium, Low and Speculative are populated and visible.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All tier content derives from the ER Potential Risks & Side Effects section sub-headings (ER lines 251-299).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans are present at lines 620, 623, 626 and 632.
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 ER sub-heading alone. The ER’s frequency data (“1 of 25 patients (4%)”, “15 of 40 participants (37.5%)”), concentration thresholds (“40–80 micromolar”), dose figures and citations are all excluded.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content survives — the percentages, counts and glosses such as “(itching)” and “(the cell’s damage-response protein)” in the ER are absent.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 Lines 620 and 623: risks_high and risks_medium both carry style=”display: none” with no content, matching the ER’s explicit “No risk reaches High” and “No risk reaches Medium either” statements. Low and Speculative are populated and visible.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 The table and cadence derive from the ER Monitoring Protocol & Defining Success section (ER lines 461-477).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 13 quantifiable biomarkers from the ER table are present, in ER order: hs-CRP, Interleukin-6, suPAR, Fasting insulin, HOMA-IR, Fasting glucose, HbA1c, LDL cholesterol, ALT, eGFR, Platelet count, Seated blood pressure and Epigenetic age. Every target range and “why” string matches the ER verbatim.
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. 🟢 Lines 773-778: the cadence reproduces the ER’s stated schedule — baseline before the first dose, inflammation and metabolic markers at 8–12 weeks then every 6 months, liver and kidney panels at 3 months then annually, and daily home blood pressure through the first two cycles for those on antihypertensives.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 The six items derive from the “Qualitative markers worth tracking alongside the panel” list in the ER Monitoring Protocol & Defining Success section (ER lines 479-486).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER qualitative markers are present in ER order, each stripped of its trailing ER rationale: physical function, joint comfort and morning stiffness, energy and daytime fatigue, sleep quality and duration, skin bruising or gum bleeding, and itching or rash within 48 hours of a dose.

Issues 09/09/2026 07:07

Pass rate 100.00%. No issues found.