Audit: QRS - Cyanidin-3-Glucoside for Health & Longevity

Audit conducted on 08/09/2026 06:03 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	84
Failed	0
N/A	9
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.	🟢	Spot-checked every populated span against the ER; protocol subs, time-to-effect subs, monitoring rows and cadence are ER text.
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.	🟢	Marker 9 target carries the ER’s “No established target; track change from the individual’s own baseline” verbatim.
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	Pregnancy sits in the Contraindications gate, matching the ER’s “should avoid” list; no tier or gate was upgraded or downgraded.
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.	🟢	Gate items come from Key Interactions & Contraindications; benefits/risks from their own ER sections; modifying-factor bullets are not surfaced.
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 (Medox, CurraNZ) appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	ER attributions (Norwich/Belfast, Sun Yat-sen, Wenhua Ling) were dropped, none added.

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, net-reading framing of the ER carries through (“claims fade once all trials are counted”).
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	States what is supported and what is not without hedging or discouragement.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Protocol cells describe what trials used rather than instructing.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative or second-person constructions; cadence is stated as impersonal noun phrases.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommend”, “advise”, “should” or “must” anywhere in the body.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	Scanned body text: no “you”/”your”.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms retained are biomarker and drug-class names that carry the fact; At-A-Glance is fully plain.
2.8	Information is presented in a concise and very compact manner	🟢	Every span is a stripped noun phrase or single short sentence pair.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by the same scan as 2.6.
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 biomarker targets and a 10-item interaction gate assume a proactive, risk-aware 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.	🟢	Flow-mediated dilation, daily capillary glucose and early INR rechecks are retained despite their burden.
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 to general-population advice; specialist ultrasound endpoint kept.
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 and time_2_sub both flag that the metabolic signal is confined to impaired glucose regulation.
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 in the file.
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; the plain wording in At-A-Glance is mandated by item 7.4 and mirrors the ER Conclusion.

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 headings, gate labels, tier labels and column headers are byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Extracted and compared span names: all present; marker_#_* and qualitative_item_# correctly expanded to 9 and 5 instances.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff against the template shows changes confined to metadata, <title> and variable spans; style block, website="…" spans and footer 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 is empty; the Risks High/Medium subsections carry explanatory prose and are handled under item 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.	🟢	“Standard dose”, “Best time of day” and “Competing approach — food first” match the ER Protocol bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect labels (“Artery dilation”, “Glucose tolerance”, “Inflammatory and metabolic markers”) are literal ER phrases from the Time to effect bullet.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Character scan of the body returns no emoji or symbol characters; the ER’s ⚠️ Conflicted markers were 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.	🟢	Every section is condensed to bare facts: rationales, magnitudes and attributions stripped, drug parentheticals reduced to one example each.

---

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.	🟢	Comment opens at line 2, immediately after the doctype.
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.	🟢	Lines 3 and 12 carry the delimiters.
5.3	The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet.	🟢	Enclosed in an HTML comment; no metadata value is repeated in 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.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: cyanidin_3_glucoside_2026-0908-0300_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]”	🟢	qrs_prompt_version: 26.7.02 matches 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)	🟢	qrs_creation_date: 2026-0908-0526.
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢	qrs_creator_ai_nickname: Opus.
5.9	The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT)	🟢	Single word, no version.
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢	qrs_creator_ai_fullname: Opus 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 qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: cyanidin_3_glucoside_2026-0908-0300_Opus_QRS.html matches the file 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 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 &)	🟢	“Cyanidin-3-Glucoside 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 &)	🟢	“Cyanidin-3-Glucoside for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0908-0526 → 09/08/2026.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“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 markup is identical to the template apart from the two variable spans; the ER’s “Also known as” line 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 into what works, what does not, and the practical concerns.
7.2	[at_a_glance] is no longer than 60 words	🟢	56 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a Conclusion sentence: poor absorption, artery widening, restored glucose handling, faded claims, unremarkable safety, GI upset and mislabeling.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“plant pigment”, “arteries widening”, “blood sugar handling”, “blood fat” — no acronyms, no clinical classifications.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial name, year or sample size appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All five items come from the ER’s “Populations who should avoid Cyanidin-3-Glucoside” list.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-list entries are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Five <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.	🟢	The ER’s “given the absence of safety data at supplemental doses” was stripped; 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).	🟢	Berry list, the 14-day surgery window, the 50 × 10⁹/L platelet threshold and the “unless glucose is actively monitored” caveat are all retained.
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 this section.
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 five such populations and the section is correctly populated.
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 ten items map one-to-one to the ER’s ten interaction bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	“elective surgery” is correctly omitted from the last item because it appears in the Contraindications gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Ten <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.	🟢	Caution/Monitor verdicts, mechanisms and management steps are all stripped; each item is a bare drug-class phrase.
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 bullet keeps a named example (apixaban, clopidogrel, glipizide, metformin, ibuprofen, ferrous sulfate, fish oil, berberine, dietary nitrate), trimmed to one per item.
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 parentheses are already plain comma-separated lists; no ranking notation is used.
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 lists ten interactions and the section is 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 cells trace to bullets in 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	🟢	Dose, timing and the food-first alternative are the three decision-bearing bullets; half-life and genotype notes are correctly omitted as non-actionable.
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 more than three 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 carry substantive ER-derived content; no placeholders remain.

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	🟢	Artery dilation, glucose tolerance and inflammatory/metabolic markers are the only three the ER names.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Endothelial function (High) → glycemic control (High) → inflammatory markers (Low).
11.3	If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	Three distinct aspects exist; 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.	🟢	Values (1–2 hours, 12 weeks, 6–12 weeks) and subs all trace to the ER Practical Considerations and Therapeutic Protocol bullets.
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 a dedicated “Time to effect” bullet, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All twelve benefit headings are reproduced in their ER tiers and order.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated.
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 bare ER heading; magnitudes and net-reading sentences are stripped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefits span.
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 benefit tiers contain items in the ER.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All seven risk headings are reproduced in their ER tiers and order.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present.
13.3	Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact.	🟢	Each entry is the bare ER heading; magnitude paragraphs are stripped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risks span.
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.	🟢	The ER reaches no High or Medium risk; both spans carry style="display: none" and are empty.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Names, targets and rationales are drawn from the ER Monitoring Protocol & Defining Success table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 9 ER table rows appear as marker_1 through marker_9; programmatic comparison matched name, target and rationale for every row.
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.	🟢	Baseline week, 12-week repeat, 6–12-month interval, 4-week glucose checks and 1/2-week warfarin rechecks all match the ER prose.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Taken from the ER’s “Qualitative markers worth tracking alongside the panel” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All 5 ER qualitative markers reproduced verbatim and in order.

Issues 08/09/2026 06:03

Pass rate 100.00%. No issues found.

Issues 08/09/2026 05:56

1. 11.4 — Time-to-effect cell contradicts itself: [time_3_value] gives “6–12 weeks” (line 507) while [time_3_sub] states “Twelve weeks is the shortest interval at which these changes appeared in trials.” (line 510), so the sub-line contradicts the range it explains.

Fixes 08/09/2026 05:56

1. 11.4 — Time-to-effect cell contradiction: Replaced [time_3_sub] “Twelve weeks is the shortest interval at which these changes appeared in trials.” with “Trials needed 6 to 12 weeks before these markers moved.”, so the sub-line now agrees with the “6–12 weeks” value.

Issues 08/09/2026 05:45

1. 11.4 — Time-to-effect subs restate label and value: [time_2_sub] (line 499) and [time_3_sub] (line 510) only repeat their own label and value (“Glucose tolerance changes were measured at 12 weeks.”; “Inflammatory and metabolic markers need 6 to 12 weeks.”), carrying no information beyond the two cells directly above them.

Fixes 08/09/2026 05:45

1. 11.4 — Time-to-effect subs restate label and value: Replaced the two null restatements with ER-sourced content that adds information beyond their own cells: [time_2_sub] now reads “Confined to impaired glucose regulation; healthy adults register vascular rather than metabolic effects.” and [time_3_sub] now reads “Twelve weeks is the shortest interval at which these changes appeared in trials.”

Issues 08/09/2026 05:39

1. 9.2 — Contraindication duplicated in interactions: The Key Interactions item “Other interventions (antioxidant stacks, elective surgery)” repeats elective surgery, which is already a Contraindication (“Surgery scheduled within 14 days”), instead of drawing a non-duplicative example from the ER bullet.

Fixes 08/09/2026 05:39

1. 9.2 — Removed duplicated surgery gate: Changed the tenth Key Interactions item from “Other interventions (antioxidant stacks, elective surgery)” to “Other interventions (antioxidant stacks, therapeutic plasma donation)”, dropping the example already covered by the “Surgery scheduled within 14 days” Contraindication and substituting the remaining example from the same ER bullet.

Issues 08/09/2026 05:33

1. 4.5 — Key Interactions gate overflows the page: The ten caution items at lines 553–562 keep every ER parenthetical drug list in full (up to 119 characters, e.g. “Supplements with additive glucose-lowering effects (berberine, alpha-lipoic acid, chromium picolinate, cinnamon extract)”), wrapping to roughly 23 lines in the narrow gate column and consuming close to half the A4 print height, which pushes the sheet past one page.

Fixes 08/09/2026 05:33

1. 4.5 — Key Interactions parentheticals trimmed: Shortened the parenthetical drug lists in all ten [caution_items] to a single representative example each (e.g. “(apixaban, rivaroxaban, dabigatran)” to “(apixaban)”, “(berberine, alpha-lipoic acid, chromium picolinate, cinnamon extract)” to “(berberine)”), as item 9.5 permits for the one-page budget. This roughly halves the gate’s wrapped line count while keeping every ER bullet label verbatim and no drug list dropped entirely.