Audit: QRS - Crocins for Health & Longevity

Audit conducted on 15/10/2026 05:37 using AI4L + evidence-mcp / Gemini 4 Argon

Iterations

Summary

Items Count
Total 94
Passed 88
Failed 0
N/A 6
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, timelines, biomarkers, and labels match the source ER (crocins_2026-1015-0437_Gemini-Argon_ER.md).
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. 🟢 Preserves (theoretical) qualifiers in Key Interactions (lines 557–560) and No established target in Monitoring (line 660).
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”). 🟢 Evidence tiers, contraindications, and interactions accurately reflect ER strength.
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. 🟢 Every QRS section draws strictly from its corresponding ER section without category relabeling.
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 citations, PMIDs, NCT IDs, expert names, or brand names appear in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No 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. 🟢 Matches the analytical, evidence-based tone of the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Balanced, objective, and practical throughout.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Uses descriptive protocol framing rather than commands.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Describes clinical trial regimens and protocol practices objectively.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Presents trial regimens and monitoring protocols without advising.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns or imperative commands in variable content.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Accessible language used across all sections.
2.8 Information is presented in a concise and very compact manner 🟢 Highly compact phrasing across all cards and tables.
2.9 It DOES NOT address the reader directly 🟢 Third-person descriptive phrasing maintained throughout.
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, 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. 🟢 Reflects comprehensive laboratory and OCT monitoring protocols.
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. 🟢 Appropriate depth for proactive longevity optimizers.
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. 🟢 Differentiates standard metabolic/ocular/longevity dosing (15 mg/day) from clinical disease trial dosing (30 mg/day).
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 exclusively; “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 “Oral administration”, “15 mg/day orally”, and “administered” consistently.

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, gate headings, tier labels, and table column headers match the template verbatim.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All data-qrs-var spans from QRS.html are intact.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 All website="..." spans and surrounding template structure 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” 🟢 All main ER sections are populated; empty High and Medium risk tiers are hidden via display: none per 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. 🟢 Protocol labels, Contraindications, Key Interactions, and Qualitative Assessment labels match the ER’s bold labels verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 All labels are taken verbatim from the ER.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emojis appear in the QRS HTML file.
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. 🟢 Compact single-page A4 layout maintained.

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 is lines 2–14, immediately after <!doctype html> on line 1.
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. 🟢 Delimited by --- on lines 3 and 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. 🟢 Enclosed in an HTML comment (<!-- ... -->).
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 values are trimmed; only duration: "00:05" is quoted due to the colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: crocins_2026-1015-0437_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]” 🟢 Line 5: qrs_prompt_version: 26.10.15.
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-1015-0528.
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: 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) 🟢 Gemini-Argon matches Gemini 4 Argon without the 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]” 🟢 Line 8: qrs_creator_ai_fullname: 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) 🟢 Gemini 4 Argon is properly formatted.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9: qrs_filename: crocins_2026-1015-0437_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. 🟢 Clean and trimmed frontmatter values.

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: <title>Crocins for Health &amp; Longevity - Quick Reference Sheet</title>.
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: Crocins for Health &amp; Longevity.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 10/15/2026.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: 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 header content present.

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 with: “Crocins are water-soluble plant pigments in saffron and gardenia fruit used as a dietary supplement to counter cellular stress and inflammation.”
7.2 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Summarizes dosing, key benefits, single-group evidence, null lipid findings, and 4–12 week tolerability with monitoring from the ER Conclusion.
7.3 [at_a_glance] is no longer than 70 words 🟢 65 words.
7.4 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Supported by ER Conclusion (lines 392–394) and Practical Considerations (line 351).
7.5 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Uses plain language (“water-soluble plant pigments”, “nerve pain and tingling”, “blood sugar”, “eye, heart, and lung protection”).
7.6 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trials, years, sample sizes, or p-values cited.
7.7 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes or statistical figures cited.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER lines 295–301.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Lists all five populations under “Populations who should avoid Crocins” from the ER.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Formatted as five <li>...</li> elements (lines 542–546).
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. 🟢 Only the core contraindication labels and parenthetical qualifiers are retained.
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). 🟢 Renal thresholds, leukocyte/neutrophil thresholds, 2-week surgical window, and botanical families 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. 🟢 No ranking notation is used in the ER (numeric threshold inequalities &gt; and &lt; are preserved appropriately).
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 5 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 Section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from ER lines 286–293.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Lists all 8 drug, supplement, and contrast interactions from the ER.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Formatted as eight <li>...</li> elements (lines 554–561).
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. 🟢 All trailing explanations after the em-dash are stripped; (theoretical) qualifiers are preserved.
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). 🟢 Named example drugs/supplements and (theoretical) tags are preserved verbatim.
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. 🟢 No ranking notation used in the ER.
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 8 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 Section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from ER Therapeutic Protocol (lines 319–323).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Covers standard dosing protocol, single vs. split dosing, and best time of day.
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 Three distinct actionable aspects are present and populated.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All 9 spans (action_1 through action_3 label, value, and sub) are populated with accurate protocol details.

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 Peripheral Neuropathy Symptom Relief, Depressive and Anxiety Symptom Reduction, and Glycemic Control and Insulin Sensitivity from ER line 349.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered to match the three High-tier benefits in Expected Benefits (ER lines 143, 149, 155).
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 time-to-effect aspects are present and populated.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All 9 spans (time_1 through time_3 label, value, and sub) are accurately populated.
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 data in Practical Considerations (line 349).

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Derived from ER lines 141–216.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four benefit tier spans are 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. 🟢 Lists only the concise benefit headings separated by semicolons.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content appears in Benefits.
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 sub-sections have items in the ER.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from ER lines 228–270.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four risk tier spans are 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. 🟢 Lists only the concise risk headings separated by semicolons.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content appears in Risks.
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 (line 573) and risks_medium (line 576) have style="display: none;".

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from ER Monitoring Protocol & Defining Success (lines 363–375).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 6 biomarkers from the ER table (FBG, HbA1c, hs-CRP, Serum Creatinine and eGFR, CBC with Differential, Central Macular Thickness via OCT) are listed.
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. 🟢 Populated on line 670 with baseline, 4-week, 8–12 week, and 6-month intervals from ER line 365.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from ER lines 376–378.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 3 qualitative markers (Mood and emotional resilience, Neuropathic sensory comfort, Sleep quality and daytime alertness) are listed verbatim.

Issues 15/10/2026 05:37

Pass rate 100.00%. No issues found.