Audit: QRS - Delphinidins for Health & Longevity

Audit conducted on 16/08/2026 00:15 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 span traced to ER text: protocol doses (ER 366–370), time-to-effect (ER 426), benefit/risk tier headings (ER 165–231, 257–299), contraindications (ER 339–344), interactions (ER 319–335), biomarker table (ER 458–469), qualitative markers (ER 473–477), cadence (ER 456).
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.	🟢	At-a-glance mirrors the ER Conclusion’s hedges (“inconsistently over months”, “stay out of reach”); time_3_sub carries “sustained dosing gives inconsistent results” from ER 181/426.
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 stay in the STOP gate at ER strength; interactions stay in the CAUTION gate. No directive is up- or down-graded.
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.	🟢	stop_items map only to ER “Populations who should avoid Delphinidins”; caution_items only to the ER interaction bullets; risks_* only to Potential Risks & Side Effects. Benefit- and Risk-Modifying Factors are not surfaced anywhere.
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 identifiers, author names, or brand names (Delphinol, MaquiBright) appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind in the QRS body.

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.	🟢	Declarative, measured, non-promotional — matches the ER throughout.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified targets and doses paired with plain-language framing in the at-a-glance.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Protocol and monitoring cells state what was studied and measured, not what the reader must do.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives outside the fixed template disclaimer; doses are presented as trial protocols.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, “should”, or “must” in any authored span.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are confined to the monitoring table where they are the marker names themselves.
2.8	Information is presented in a concise and very compact manner	🟢	Every field is condensed relative to its ER source: contraindication rationales stripped, marker_3_why trimmed from ER 462, marker_9_target compressed from ER 468.
2.9	It DOES NOT address the reader directly	🟢	Confirmed — no direct address in any authored span.
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 biomarker ranges and a ten-marker panel presuppose a self-tracking 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.	🟢	Empty-stomach timing, pre-meal dosing, and a staged testing cadence all assume effort tolerance.
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.	🟢	No simplification toward general-population framing; INR bands and Schirmer’s targets are retained.
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.	🟢	At-a-glance closes on the bioavailability ceiling and manufacturer funding — the two facts that matter most to a discerning self-experimenter.
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.	🟢	Title and header use “Health & Longevity”; no “anti-aging” string occurs.
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 register throughout; the plain-language phrasing in at_a_glance is mandated by item 7.4 for that section specifically.

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 verified verbatim: lines 446, 492, 540, 617, 645, 798, 571, 587, tier labels in the benefits and risks spans, and column headers at lines 649–651.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	69 named spans present, covering page_title, header_, at_a_glance, action_1–3 (label/value/sub), time_1–3 (label/value/sub), benefits_, stop_items, caution_items, risks_*, marker_1–10 (name/target/why), monitoring_cadence, qualitative_item_1–5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Non-variable template spans (website="evidence_review" line 423, website="full_review" line 440, website="audit" line 426), the style block, and the footer disclaimer 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; every benefit tier, risk tier, gate, protocol, and monitoring section is populated in the ER.
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.	🟢	action_1–3 labels “Glycaemic protocol”, “Ocular protocol”, “Whole-food alternative” are verbatim from ER 366, 368, 370; monitoring row labels are verbatim from the ER table’s first column.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect labels “Lipid changes”, “Tear production”, “Post-meal glucose” are lifted from the ER’s own phrasing at line 426.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code points in the file; the ER’s “⚠️ Conflicted” markers are correctly dropped.
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.	🟢	Single-sheet layout with @page A4 print rules intact; every populated field is a condensation of its ER source rather than a transcription, and no content is carried past the sheet.

---

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 the doctype at line 1 and before the template comment at 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 --- at line 3, closing --- at line 13; the preceding title text sits before the opening delimiter.
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 entirely in an HTML comment; none of its values are duplicated into the 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:02" is quoted, and it contains a colon requiring it.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: delphinidins_2026-0825-2155_Opus_ER.md, matching the ER on disk.
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 badge version.
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-0816-0007, correct format.
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, no context-window or other qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual filename delphinidins_2026-0825-2155_Opus_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.	🟢	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., & for &)	🟢	Line 22: “Delphinidins for Health & Longevity - Quick Reference Sheet”, matching ER canonical_topic with the ampersand encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	Line 417: “Delphinidins for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/16/2026”, the correct reformat of 2026-0816-0007.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the frontmatter value.
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 holds only the title and the template subline; the ER’s “Also known as” list is 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 ER 501–505 into the two decision-relevant findings, the bioavailability ceiling, and the funding caveat.
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.	🟢	Blue-purple pigments and maqui (ER 501, 39); arteries and blood fats (ER 501); tear production (ER 501); short-term vs sustained glucose (ER 501); absorption ceiling and cancer/brain findings (ER 503); manufacturer funding (ER 505).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “blood fats” for lipids, “arteries widening” for flow-mediated dilation, “very little is absorbed” for bioavailability.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No author names, years, or sample sizes appear.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	The ER’s mmol/L and percentage-point figures are omitted; only directional language is used.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All six items trace to ER 339–344 under “Populations who should avoid Delphinidins”.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER avoidance populations are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Six <li> elements at lines 574–582.
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.	🟢	The ER’s trailing rationales “on absence of safety data rather than evidence of harm” and “for the same reason” are correctly stripped; the “Anyone…” lead-ins are dropped; no dash-trailing clauses 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).	🟢	Preserved: INR “above 3.0”, the “14 days” surgical window, “below 50 × 10⁹/L”, the named bleeding disorders, and “HbA1c already below 6.5%”.
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 inside parentheses in its contraindication list.
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 such 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 to the ER interaction bullets at lines 319–335.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All nine ER interaction bullets are carried; none duplicates a stop_item, since the contraindications are narrower patient-state conditions rather than drug classes.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Nine <li> elements at lines 590–607.
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.	🟢	The ER’s Caution/Monitor severity words, mechanism sentences, and “Mitigation:” clauses are all stripped; only class plus example drugs remain.
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 ER example-drug list is preserved intact across all nine items, including the “Other interventions” list (time-restricted eating, ketogenic diets, prolonged fasting).
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 inside its interaction parentheses.
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.
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 action sets trace to the ER Therapeutic Protocol bullets at lines 366–376.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The two indication-specific dosing protocols plus the whole-food route — the only three bullets that specify an executable regimen.
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 three or more distinct actionable aspects; all three sets are used.
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 populated; action_1_sub combines ER 366 and the “Best time of day” bullet at ER 376, action_2_sub condenses ER 368, action_3_sub condenses ER 370 with the sourcing caveat at ER 420.

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	🟢	Lipids, tear production, and post-meal glucose — drawn from the ER “Time to effect” bullet at line 426.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Lipid changes map to a High-tier benefit and lead; tear production and post-meal glucose map to Medium-tier benefits and follow.
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 four distinct time-to-effect aspects; all three sets are used.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine spans populated; time_2_sub folds in the oxidative-stress timescale from ER 426, time_3_sub carries the sustained-dosing inconsistency from ER 181.
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 at line 426, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All eleven entries correspond one-to-one with the ER benefit headings at lines 165–231.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 542, 547, 553, 559.
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 benefit names only; the ER’s Magnitude paragraphs and mechanism sentences are excluded.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s FMD/PWV figures, mmol/L differences, and cited authors are absent; the “⚠️ Conflicted” qualifiers 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 ER benefit tiers contain items, so no span needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All seven entries correspond one-to-one with the ER risk headings at lines 257–299.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 619, 622, 628, 634.
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 risk names only; the ER’s pharmacokinetic figures and mechanistic paragraphs are excluded.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s parenthetical drug-class glosses and cited studies do not appear.
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 ER risk tiers contain items, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows and targets trace to the ER Monitoring Protocol & Defining Success table at lines 458–469.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All ten ER biomarkers present in ER order: fasting glucose, HbA1c, fasting insulin, LDL-C, triglycerides, HDL-C, hs-CRP, ferritin, clotting time (INR), Schirmer’s test.
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.	🟢	Line 788 carries the full baseline-to-12-week-to-6–12-month schedule condensed from ER 454–456.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All five items trace to the qualitative-marker list at ER 473–477.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers present and none added: eye comfort, visual fatigue, post-meal energy stability, unusual bruising/bleeding, digestive comfort.

Issues 16/08/2026 00:15

Pass rate 100.00%. No issues found.