Audit: QRS - Crocins for Health & Longevity

Audit conducted on 16/08/2026 09:37 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.	🟢	All spans traced to ER text: protocol cells to Therapeutic Protocol, time cells to Practical Considerations, benefit/risk lines to the ER headings, all 9 markers and cadence to Monitoring Protocol & Defining Success.
1.2	Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing.	🟢	“No established target; track change from own baseline” mirrors the ER’s marker_9 wording; the Speculative tiers are retained as speculative.
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 and breastfeeding remain absolute contraindications; the ER’s “⚠️ Conflicted” flags are carried as “— conflicted”.
1.4	The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc.	🟢	Contraindications come only from “Populations who should avoid Crocins”; interactions only from the interaction bullets; no modifying-factor content leaked into the gates.
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.	🟢	The QRS carries no PMIDs, author names, NCT identifiers, or brand names at all.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind are present.

2. Focus, Tone & Audience

#	Description	Result	Comments
2.1	The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing.	🟢	The sceptical, evidence-weighted register of the ER Conclusion is preserved in [at_a_glance] and the tier lines.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Facts and thresholds are stated without hedging or alarm; the sheet gives the reader the levers (dose, duration, markers) to act on.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as what trials did and what markers moved, not as orders.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No prescriptive verbs; the monitoring cadence is presented as the ER’s schedule, not as an instruction.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrences of “recommend”, “advise”, or “should” in the document voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere; the ER’s “for those pursuing the retinal indication” was neutralised to “for the retinal indication”.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Retained technical terms (Child-Pugh Class C, partial thromboplastin time, leukopenia) are decision-gate or biomarker terms mandated by items 8.5 and 13.4.
2.8	Information is presented in a concise and very compact manner	🟢	Tier lines are semicolon-joined heading lists; gate items are label plus example list with all rationale stripped.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text scan for second-person forms.
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.	🟢	Optimal functional ranges (hs-CRP < 1.0 mg/L, HbA1c 4.8–5.2%) rather than conventional lab flags are carried through.
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.	🟢	A 12-week minimum, twice-daily dosing and a nine-marker panel are presented without softening.
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 casual use; the sheet assumes lab access and adherence.
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] foregrounds that the whole extract outperforms the purified pigment, the decision-relevant point for this audience.
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.	🟢	“Longevity” appears only in the canonical topic; “anti-aging” appears nowhere.
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-language wording inside [at_a_glance] is mandated by item 7.4 and is ER-sourced.

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 titles, tier labels and the Marker/Target/Why headers are byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variables present; the repeatable marker_#_* and qualitative_item_# rows are expanded to 9 and 5 instances respectively.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A normalised diff against the template shows differences only inside populated variable spans and the metadata block; CSS, structure, comments and the website="…" spans 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 mapped by the QRS is empty; every benefit tier, risk tier, gate and monitoring row has content.
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”, “Split dosing”, “Duration before judging” and all nine interaction labels are verbatim ER bold labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	The three Time-to-effect labels use the ER’s own nouns (“inflammatory markers”, “mood changes”, “retinal measurements”) from the Time to effect bullet, which carries no per-item bold labels.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	A Unicode scan of the file returns no emoji; the ER’s tier emoji were dropped and the ⚠️ flags rendered as text.
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.	🟢	The unmodified A4 print stylesheet is retained, and every section is condensed rather than extended: benefit and risk tiers carry headings only, gate items are stripped to label plus example list, and the 526-line ER is reduced to single-line entries.

---

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.	🟢	The comment opens at line 2, immediately after the doctype at 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.	🟢	Opening --- at line 3, closing --- at line 13, preceded only by the “QRS — Metadata” caption.
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.	🟢	It sits inside an HTML comment and is not duplicated anywhere in the header or footer.
5.4	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Only duration: "00:03" is quoted, correctly, because the value contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: crocins_2026-0825-0657_Opus_ER.md.
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md version badge.
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	Line 6: qrs_creation_date: 2026-0816-0931.
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” is a single word with 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” is nickname plus version with no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s own name on disk.
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Re-verified across all nine keys; no stray whitespace or unnecessary quoting.

6. Page Title & Header

#	Description	Result	Comments
6.1	[page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &)	🟢	“Crocins for Health & Longevity - Quick Reference Sheet”, correctly entity-encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	“Crocins for Health & Longevity” at line 417.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0816-0931 renders as 08/16/2026.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“Opus 5” at line 425.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	The header contains only the template’s date, review link, AI4L link and model name; 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	🟢	Every clause maps to the three Conclusion paragraphs: best-supported effects, the “single studies / seller-run / animals” caveat, the safety triad, and the whole-extract comparison.
7.2	[at_a_glance] is no longer than 60 words	🟢	58 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each of the five sentences traces to a separate Conclusion sentence.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “inflammation markers”, “blood sugar control”, “kidney marker” and “clotting time” are the plain-language forms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, authors, years or sample sizes appear.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Direction of effect only (“falls”, “rises”, “shortens”); no numbers.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All eight items come from the “Populations who should avoid Crocins” list in that ER section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All 8 ER contraindications are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Eight discrete <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.	🟢	No dashes or trailing clauses; the ER’s “the most advanced grade of liver failure” gloss was 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).	🟢	30 mL/min/1.73 m², 50 × 10⁹/L, 14 days, 100 mmHg and Child-Pugh Class C 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 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 eight 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 nine items map one-to-one onto ER interaction bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Nine of the ER’s ten interaction bullets are carried; “Cytotoxic chemotherapy” is correctly omitted because it already appears as the contraindication “Active cytotoxic chemotherapy without explicit oncology approval”.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Nine discrete <li> elements inside the span.
9.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	Every Severity / Consequence / Mitigation clause was dropped; no dashes 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).	🟢	lisinopril, losartan, amlodipine, hydrochlorothiazide, glimepiride, apixaban, simvastatin, sertraline, fluoxetine, ibuprofen, naproxen and diphenhydramine are all retained.
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 parentheses in its interaction 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.	🟢	The ER names ten 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 cells derive from the ER Therapeutic Protocol bullets.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard dose, split dosing and duration before judging are the three decision-critical levers in that ER section.
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 twelve protocol bullets, so 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 action variables carry ER-sourced 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	🟢	Inflammatory markers, mood changes and retinal measurements are exactly the three the ER’s Time to effect bullet names.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Inflammatory markers (High tier) precede mood changes and retinal measurements (both Medium tier).
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 names three distinct time-to-effect aspects, so 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 time variables carry ER-sourced content; no placeholders remain.
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 does provide time-to-effect information, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All 15 ER benefit headings appear, distributed across the correct four tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four 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.	🟢	Only the ER heading text is carried; the retained “— conflicted” reproduces the ER’s own ⚠️ Conflicted heading flag, which item 1.3 forbids dropping.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefit tier line.
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 10 ER risk headings appear, distributed across the correct four tiers.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans are present and populated.
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.	🟢	Only the ER heading text is carried; the retained “— conflicted” reproduces the ER’s own ⚠️ Conflicted heading flag.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s “(Low White-Blood-Cell Count)” gloss was correctly stripped; no parentheses remain in any risk tier line.
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	🟢	The table reproduces the ER Monitoring Protocol & Defining Success biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 9 ER biomarker rows are present with their optimal functional ranges and “Why Measure It?” text.
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, weekly blood pressure for four weeks, full panel at 12 weeks, then every 6–12 months — matching the ER paragraph.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All five items come from the ER’s “Qualitative markers worth tracking alongside the laboratory work” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All 5 ER qualitative markers are present, none added.

Issues 16/08/2026 09:37

Pass rate 100.00%. No issues found.