Audit: QRS - Mulberry Fruit Extract for Health & Longevity

Audit conducted on 20/08/2026 08:40 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 83
Failed 0
N/A 10
Pass Rate 100.00%
  • Total = Passed + Failed + N/A
  • Pass Rate = Passed / (Passed + Failed) × 100
  • N/A items are excluded from the pass rate calculation

1. General Rules

# Description Result Comments
1.1 Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. 🟢 Every populated span traces to ER text: protocol doses to ER Therapeutic Protocol, time-to-effect to ER Practical Considerations, gates to ER Key Interactions & Contraindications, tiers to ER Expected Benefits / Potential Risks & Side Effects, all 10 markers and the cadence to ER Monitoring Protocol & Defining Success.
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. 🟢 Hedges carried over: “Where they occur at all; pooled analyses disagree.” (line 517), “Where the change occurs at all.” (line 528), “stay unsettled” (line 436).
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”). 🟢 Contraindications retain absolute framing (“Pregnancy and breastfeeding”, “Anyone under 18”); conflicted benefits keep their hedge in the time-to-effect subs.
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 come only from the ER “Populations who should avoid” list; Key Interactions only from the ER interaction bullets; no Benefit- or Risk-Modifying Factor content appears in either gate.
1.5 PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact. 🟢 No PMIDs, NCT IDs, or author names anywhere. The only brand name, “Reducose” (line 588), appears in the ER for the same interaction bullet.
1.6 The QRS does not introduce new attributions. 🟢 “one company developing the ingredient” (line 438) mirrors the ER Conclusion’s “a single food company developing the ingredient”; no other attribution is present.

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 and deflationary in the same way as the ER: one demonstrated action, the rest unsettled, sponsor concentration flagged.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Concrete doses, timing, functional biomarker targets and a cadence give the reader actionable levers without overstating the evidence.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Statements are declarative descriptions of evidence; no imperatives directed at a patient.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No prescriptive verbs in any populated span; the only advisory sentence is the fixed template footer disclaimer.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No occurrence of “recommend”, “advise”, or “guidance” in any populated span.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the document body.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms are confined to decision gates and biomarker names where they are load-bearing and ER-verbatim; the At-A-Glance is jargon-free.
2.8 Information is presented in a concise and very compact manner 🟢 Tier lines are semicolon-joined headings only; gate items are stripped to the key fact; marker “why” cells are single clauses.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by full-text scan: no “you”, “your”, “we”, or “our”.
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 optimal ranges (fasting insulin 2–5 µIU/mL, HOMA-IR below 1.0, hs-CRP below 0.5 mg/L) and CGM-based monitoring address exactly this 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. 🟢 Per-meal split dosing, continuous glucose monitoring, and a 10-marker panel assume high willingness to expend 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. 🟢 Optimal functional ranges are tighter than conventional references and the monitoring burden is well beyond general-population practice.
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 sheet foregrounds the single well-supported post-meal effect and the sponsor concentration, letting a risk-aware reader weight the rest correctly.
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. 🟢 The string “anti-aging” does not occur; the title uses “Health & Longevity”.
2.15 The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. 🟢 Clinical register throughout (e.g., “carbohydrate malabsorption”, “oral allergy syndrome”, “sucrase-isomaltase deficiency”); the plainer wording in At-A-Glance is ER-derived and required by item 7.4.

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 byte-identical to the template (lines 446, 492, 536, 565, 583, 607, 638, 642–644, 788) and both tier label sets unchanged.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variable names present; the repeatable marker_#_* and qualitative_item_# rows are correctly expanded to marker_1..10_* and qualitative_item_1..5.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Diff against the template shows changes only inside data-qrs-var spans and the metadata block; the website="…" spans, CSS, and structural markup are untouched.

4. Formatting

# Description Result Comments
4.1 When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” N/A No source ER section that feeds the QRS is empty.
4.2 Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. 🟢 “Standard dose”, “Dose most consistently effective”, “Timing within the meal” and the five qualitative labels (“Post-meal energy dip”, “Gut comfort”, “Afternoon carbohydrate cravings”, “Sleep continuity”, “Training quality”) are ER-verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Biomarker names match the ER table verbatim; the three time-to-effect labels are drawn from the ER’s own wording (“the glucose endpoint”, “Lipid, glycated hemoglobin, and inflammation changes”).
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji in the document; the ER’s tier emojis and “⚠️ Conflicted” markers were correctly dropped in favour of CSS palettes and bold tier 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. 🟢 Every section is condensed to its minimum consistent with items 8.2, 9.2, 12.2, 13.2, 14.2 and 15.2: tier lines are heading-only, gate items are single clauses, marker rationales are single clauses.

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. 🟢 Lines 2–14, immediately after <!doctype html> on line 1 and before the template comment on line 16.
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 --- on line 3, closing --- on line 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. 🟢 Fully enclosed in an HTML comment; no metadata value is repeated in the header, footer, 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. 🟢 Only duration: "00:03" is quoted, and it contains a colon requiring YAML quoting.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: mulberry_fruit_extract_2026-0825-0548_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 the QRS.md version badge.
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢 Line 6: qrs_creation_date: 2026-0820-0828.
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” — single word, 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” — nickname plus version only.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9 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 across all nine keys; no stray whitespace or unnecessary 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 &) 🟢 Line 22: “Mulberry Fruit Extract for Health & Longevity - Quick Reference Sheet”.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Line 417: “Mulberry Fruit Extract for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: “08/20/2026”, correctly derived from 2026-0820-0828.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: “Opus 5”.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Header contains only the title and the template subline; the ER’s “Also known as” list was 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 🟢 Compresses all four Conclusion paragraphs — the demonstrated action and its execution condition (“taken with a starchy meal”), the unsettled chronic markers, the dose-linked side effects, and the sponsor concentration.
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 a distinct ER Conclusion sentence (paragraphs 1, 2 and 3 respectively).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms; “alpha-glucosidase”, “1-deoxynojirimycin”, “HbA1c” and “postprandial” are all avoided in favour of “slows starch breakdown”, “blood sugar”, “longer-term blood sugar”.
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 percentages, effect sizes, or statistics; the ER’s “20–27%” and “0.55 percentage points” figures are absent.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All eight items trace to the ER’s “Populations who should avoid Mulberry Fruit Extract” list.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER bullets are represented; the compound first and last bullets are correctly split into two items each, giving eight.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Lines 568–578: eight well-formed <li> elements inside the 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. 🟢 Rationales stripped: the ER’s “by analogy to the labeling restriction on the renally cleared iminosugar miglitol” and “because no safety data exist in these groups” do not appear; no dashes carry trailing 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). 🟢 “Mayo endoscopic subscore ≥ 2 in ulcerative colitis” and “creatinine clearance < 25 mL/min” preserved verbatim; “delayed gastric emptying” retained in trimmed form.
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 these bullets; “≥ 2” is a self-interpreting clinical staging threshold, not a severity ordering.
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 six avoid-populations and the section is correctly populated rather than empty.
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All nine items trace one-to-one to the ER’s nine interaction bullets, in ER order.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Nine of nine ER interaction bullets present; no overlap with the eight contraindication items.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Lines 586–597: nine well-formed <li> elements inside the 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. 🟢 Every “Caution;/Monitor;” rationale and every “Mitigation:” clause is stripped, as are the in-paren em-dash glosses (“— drugs that make the pancreas release more insulin”, “— drugs that make the kidney excrete glucose”).
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 five ER drug lists preserved: glimepiride/glibenclamide/repaglinide; acarbose/miglitol/voglibose; Reducose and similar; empagliflozin/dapagliflozin; berberine/gymnema/chromium picolinate/cinnamon extract/white kidney bean extract/alpha-lipoic acid.
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 these bullets; all parentheses hold plain comma-separated example lists.
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 interactions and the section is correctly populated rather than empty.
9.8 If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells derive from the ER Therapeutic Protocol bullets, with the split-dosing bullet folded into the timing sub-line.
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose range, the dose that worked most consistently, and meal-relative timing are the three levers that determine whether the mechanism engages at all.
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 well over three actionable aspects and all three sets are populated.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All nine spans (lines 450–487) carry substantive ER-derived content; no placeholder text remains.

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 🟢 Glucose endpoint, lipids/glycated hemoglobin, and inflammation — the exact three windows named in the ER Practical Considerations time-to-effect bullet.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Glucose (ER High tier) first, then the Medium-tier lipid/glycemic-marker and inflammation endpoints.
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 and all three sets are populated.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All nine spans (lines 498–529) carry ER-derived content; no placeholder text remains.
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 explicit 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 nine benefit headings from the ER’s four tiers are represented in the matching QRS tier.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present and populated (lines 538–558).
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. 🟢 Headings only, semicolon-separated; the ER’s “Magnitude:” figures and “⚠️ Conflicted” qualifiers are absent.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in any benefit tier line; the ER’s “(LDL-C, the cholesterol fraction…)” and “(HbA1c, a three-month average…)” glosses are 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. N/A All four tiers carry items in the ER, so no span needed hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All seven risk headings from the ER’s four tiers are represented in the matching QRS tier.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated (lines 609–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. 🟢 Headings only, semicolon-separated; the ER’s breath-hydrogen thresholds and “Magnitude:” paragraphs are absent.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in any risk tier line; the ER’s “(itching and swelling of lips and throat…)” and “(a rapid, whole-body allergic reaction)” glosses are 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. N/A All four tiers carry items in the ER, so no span needed hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Table and cadence both derive from the ER Monitoring Protocol & Defining Success section.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 10 ER table rows present in ER order with verbatim names, optimal ranges, and “Why Measure It?” text: CGM peak, fasting glucose, HbA1c, fasting insulin, HOMA-IR, triglycerides, LDL-C, hs-CRP, ALT, ferritin.
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 778–782 reproduce the ER’s 4-week, 12-week, 6–12-month and annual-ferritin schedule.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All five items derive from the ER’s “Qualitative markers worth tracking alongside the labs” list.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers present in ER order with their bold labels verbatim (lines 791–818).

Issues 20/08/2026 08:40

Pass rate 100.00%. No issues found.

Issues 20/08/2026 08:33

  1. 1.3 — At-a-glance overstates sponsor scope: [at_a_glance] (line 437) says “Nearly all testing came from one company developing the ingredient”, but the ER confines “nearly all of that testing” to the post-meal glucose trials (ER line 476) and otherwise says only “Most human testing” (ER line 41), while itself citing non-sponsor Thai, Pakistani and mulberry-milk trials.
  2. 4.2 — ER bold labels altered in gate: Two Key Interactions items drop the ER’s “Over-the-counter” qualifier — “Digestive enzyme blends containing amylase or glucoamylase” (line 589) and “Activated charcoal and bulk fiber laxatives” (line 590) against ER lines 305 and 307.

Fixes 20/08/2026 08:33

  1. 1.3 — At-a-glance sponsor scope narrowed: Changed “Nearly all testing came from one company developing the ingredient” to “Nearly all of the glucose testing came from one company developing the ingredient”, matching the ER’s scoping of the sponsorship claim to the post-meal glucose trials.
  2. 4.2 — “Over-the-counter” restored on gate labels: Reinstated the ER’s “Over-the-counter” qualifier on the two Key Interactions items for digestive enzyme blends and for activated charcoal and bulk fiber laxatives.