Audit: QRS - Delphinidins for Health & Longevity
Audit conducted on 19/10/2026 02:08 using AI4L + evidence-mcp / Gemini 4 Argon
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 claims, doses, timeframes, labels, and targets match the source ER. |
| 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 (“theoretical”, “low-level, indirect”, “conflicted across randomized trials”) is 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”). | 🟢 | No ER claims are strengthened or softened. |
| 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 items remain in their exact ER decision categories. |
| 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. | 🟢 | Brand names (Delphinol, MaquiBright) appear only where supported by the ER for the same facts. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No new attributions are introduced. |
2. Focus, Tone & Audience
| # | Description | Result | Comments |
|---|---|---|---|
| 2.1 | The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing. | 🟢 | Tone matches the objective, evidence-graded framing of the source ER. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Language is accessible, objective, data-driven, and practical. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents trial parameters and evidence levels without prescriptive directives. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Uses descriptive trial reporting rather than medical advice. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Describes studied regimens and trial findings rather than advising or recommending. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns or direct imperatives addressing the reader. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Uses plain language throughout while preserving verbatim ER labels. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | All cards, cells, and table rows are compactly formatted. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | 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. | 🟢 | Framed for proactive, risk-aware longevity-oriented adults. |
| 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. | 🟢 | Includes specific pre-meal timing, split dosing, iron separation, and biomarker tracking. |
| 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. | 🟢 | Maintains rigorous protocol and biomarker detail suited to proactive health optimization. |
| 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. | 🟢 | Highlights indirect extract evidence, industry sponsorship, and baseline metabolic modifiers. |
| 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. | 🟢 | Uses longevity framing; “anti-aging” does not appear. |
| 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. | 🟢 | Uses formal clinical terminology (“oral dietary supplements”, “administered orally”, “adverse events”). |
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 card headings, gate headings, tier labels, and table column headers are intact. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All template data-qrs-var spans are present. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Website placeholder spans (evidence_review, audit, full_review) and footer 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 | All source ER sections mapped to text-bearing QRS sections contain content; empty benefit and risk tiers are hidden via display: none per 12.5 and 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. | 🟢 | All ER bold labels are used verbatim in Protocol, Contraindications, Key Interactions, and Qualitative Assessment. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No labels are paraphrased, abbreviated, or invented; example drug lists in Key Interactions are trimmed per 9.5. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji indicators appear anywhere in the QRS. |
| 4.5 | The QRS is designed to render on one A4 page: every section is condensed to the shortest form the other checklist items allow, not extended onto a second page. | 🟢 | All sections are condensed to the shortest form permitted by the checklist. |
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 immediately follows <!doctype html>. |
| 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 block is delimited by — opening and closing lines. |
| 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. | 🟢 | Metadata is enclosed in an HTML comment and 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. | 🟢 | All frontmatter values are properly trimmed and only duration is quoted due to its colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename is set to delphinidins_2026-1019-0014_Gemini-Argon_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]” | 🟢 | qrs_prompt_version is set to 26.10.18. |
| 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 is set to 2026-1019-0152. |
| 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 is set to Gemini-Argon. |
| 5.9 | The nickname of the AI is the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT) | 🟢 | Nickname Gemini-Argon follows the hyphen-joined format without version number. |
| 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 is set to Gemini 4 Argon. |
| 5.11 | The full name of the AI consists of the model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y) | 🟢 | Full name Gemini 4 Argon follows the capitalized model name, version, and variant format. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename is set to delphinidins_2026-1019-0014_Gemini-Argon_QRS.html. |
| 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. | 🟢 | All frontmatter values are trimmed and cleanly formatted. |
6. Page Title & Header
| # | Description | Result | Comments |
|---|---|---|---|
| 6.1 | [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &) |
🟢 | page_title is “Delphinidins 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., & for &) |
🟢 | header_topic is “Delphinidins for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | header_subline_date is “10/19/2026”. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | header_subline_model is “Gemini 4 Argon”. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | No extra badges, version stamps, or alternate name lines appear in the header. |
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 by defining delphinidins as blue-red plant pigments in berries used as oral dietary supplements for blood sugar, blood vessel flexibility, and tear production. |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Summarizes the ER Conclusion section with execution-relevant takeaways. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | 67 words (within the 70-word maximum). |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Every statement maps directly to the ER Motivation, Practical Considerations, and Conclusion sections. |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Uses plain-language terms (“post-meal blood sugar”, “blood vessel flexibility”, “long-term blood sugar”) with no acronyms. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No specific trial names, years, sample sizes, or p-values are cited. |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numerical effect sizes, relative risks, or statistical figures are cited. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from the ER Key Interactions & Contraindications section. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All four populations listed under “Populations who should avoid Delphinidins” in the ER are included. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each item is formatted as an <li> element. |
| 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. | 🟢 | Trailing trial exclusions, NCT numbers, and mechanistic explanations are 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). | 🟢 | Parenthetical qualifiers and clinical thresholds (stage 5 CKD, eGFR <15 mL/min/1.73 m², within 3 months, Schirmer’s test <5 mm/5 min, warfarin) are 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. | N/A | The source ER does not use ranking notation inside parentheses in the Contraindications bullets. |
| 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. |
🟢 | Populated with the four contraindicated populations from the ER. |
| 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 Contraindications section is populated because the ER identifies excluded populations. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | 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 six interaction classes from the ER are included, excluding warfarin from the anticoagulant examples as it appears in Contraindications. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Each item is formatted as an <li> element. |
| 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. | 🟢 | Trailing mechanistic explanations and clinical management clauses are stripped, leaving only the label and severity/evidence tag. |
| 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). | 🟢 | Parenthetical example drugs and qualifiers are preserved and concisely trimmed. |
| 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 source ER does not use ranking notation inside parentheses in the Key Interactions bullets. |
| 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. |
🟢 | Populated with the six interactions from the ER. |
| 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 Key Interactions section is populated because the ER identifies six theoretical interactions. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Derived from the ER Therapeutic Protocol section. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Covers Standardized extract dosing, Best time of day, and Single versus split dosing. |
| 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 | All three action sets are populated with distinct actionable implementation aspects from the ER Protocol section. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All three action label, value, and sub spans are populated with ER Protocol data. |
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 | 🟢 | Covers the three time-to-effect intervals stated in the ER Practical Considerations section. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by the corresponding Expected Benefits order (Tear secretion first, then acute postprandial glucose/FMD, then conflicted HbA1c/lipids). |
| 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 | All three time-to-effect sets are populated with distinct time-to-effect aspects from the ER. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All three time label, value, and sub spans are populated with ER data. |
| 11.5 | If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel |
N/A | The ER provides time-to-effect information for three distinct outcomes. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Derived from the ER Expected Benefits section. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | Uses benefits_high, benefits_medium, benefits_low, and 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. | 🟢 | Lists only concise benefit names separated by semicolons without effect sizes or study details. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | All parenthetical content and badges 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. | 🟢 | benefits_high and benefits_medium spans are hidden with style=”display: none”. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Derived from the ER Potential Risks & Side Effects section. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | Uses risks_high, risks_medium, risks_low, and 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. | 🟢 | Lists only concise risk names under Speculative without explanations or citations. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content is present. |
| 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, risks_medium, and risks_low spans are hidden with style=”display: none”. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from the ER Monitoring Protocol & Defining Success section. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All six quantitative biomarker rows from the ER Monitoring table are included. |
| 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. |
🟢 | monitoring_cadence is populated with the baseline, 1–2 week, 4-week, 12-week, and 6-month schedule from the ER. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from the ER Monitoring Protocol & Defining Success section. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All three qualitative markers from the ER are listed verbatim. |
Issues 19/10/2026 02:08
Pass rate 100.00%. No issues found.
Issues 19/10/2026 02:01
- 4.3 — Abbreviated time-to-effect labels: In the
Time to effectsection (lines 483 and 505),time_1_label(Postprandial glucose & acute FMD) andtime_3_label(HbA1c & lipid shifts) abbreviate “and” to&and truncate the source ER wording (“Postprandial glucose blunting and acute FMD increases” and “HbA1c and lipid shifts”). - 11.2 — Time-to-effect ordering by magnitude: In the
Time to effectsection (lines 481–513), the three items are ordered chronologically (60–120 minutes,4 weeks,8–12 weeks) rather than by the magnitude and order of the related benefits in the ERExpected Benefitssection (Tear secretion/Tear Production and Dry Eye Symptom Relieffirst, followed byPostprandial glucose blunting and acute FMD increases, andHbA1c and lipid shiftslast).
Fixes 19/10/2026 02:01
- 4.3 — Abbreviated time-to-effect labels: Replaced
Postprandial glucose & acute FMDandHbA1c & lipid shiftsin theTime to effectsection with the unabbreviated ER phrasesPostprandial glucose blunting and acute FMD increasesandHbA1c and lipid shifts. - 11.2 — Time-to-effect ordering by magnitude: Reordered the three
Time to effectsets by the magnitude and order of their related benefits in the ERExpected Benefitssection (Tear secretionat4 weeksfirst,Postprandial glucose blunting and acute FMD increasesat60–120 minutessecond, andHbA1c and lipid shiftsat8–12 weeksthird).