Audit: QRS - Naringin for Health & Longevity

Audit conducted on 24/09/2026 04:51 using AI4L / Opus 5.5

Iterations

Summary

Items	Count
Total	94
Passed	87
Failed	0
N/A	7
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 protocol, time-to-effect, benefit, risk, gate, marker, cadence and qualitative entry traces to ER text (e.g., Therapeutic Protocol L381/385/387, Practical Considerations L418, Monitoring table L443-452).
1.2	Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing.	🟢	Cautious ER phrasing kept: ‘no clinician-developed protocol exists’, ‘No comparison exists’, ‘plausible but untested’, ‘unconfirmed’, ‘Grapefruit juice, not isolated naringin, was tested’.
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	No claim strengthened or softened; At a Glance mirrors ER Conclusion wording (‘modest’, ‘largest trial found no cholesterol change’, ‘Safety looks favorable within the doses studied’).
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 ER Key Interactions & Contraindications with the ER’s own Caution/Monitor classes; tiers match ER tiers.
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 IDs or expert names; the only brand name (Allegra) appears in the ER for the same fact (L342).
1.6	The QRS does not introduce new attributions.	🟢	No new attributions introduced.

2. Focus, Tone & Audience

#	Description	Result	Comments
2.1	The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing.	🟢	Tone matches the ER’s measured, evidence-weighted framing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert, accessible, objective and data-driven.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Reads as an informational guide; protocol values are framed as trial-based.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No language implying medical advice.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Presents information (e.g., ‘trials dosed in the morning or at meals’) rather than recommending.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No direct address of the reader.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language; remaining technical terms (OATP1A2, CYP3A4, QTc) are ER bold labels/marker names that must be kept verbatim.
2.8	Information is presented in a concise and very compact manner	🟢	Items condensed to key facts.
2.9	It DOES NOT address the reader directly	🟢	No ‘you’/’your’ anywhere in the sheet.
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.	🟢	Content suits health- and longevity-oriented, risk-aware adults.
2.11	The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort.	🟢	Includes an effortful monitoring panel and interaction management, suitable for a committed audience.
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.	🟢	Not written for a general-population audience.
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.	🟢	Framing reflects the ER’s balance of modest human benefit versus medication-interaction risk.
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.	🟢	No ‘anti-aging’ framing; ‘longevity’ used.
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.	🟢	Formal terminology throughout; no lay route or ‘pill’ phrasing.

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 headers unchanged (L440, L477, L519, L539, L551, L576, L595, L599-601, L665).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template data-qrs-var spans present (template vars diffed against QRS; marker_# and qualitative_item_# expanded to 10 and 5 rows).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Non-variable spans (website=evidence_review/audit/full_review) and all other markup unchanged versus the template; only display:none added to empty tiers per 12.5/13.5.

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”	🟢	ER empty High/Medium tiers are hidden per the more specific 12.5/13.5 rules; no other empty ER section surfaced.
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 (‘Isolated naringin (trial-based)’, ‘Time of day’, ‘Single vs. split dosing’) and interaction labels verbatim from ER bold labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Labels not paraphrased or invented.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji in the QRS (script check).
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.	🟢	Each section condensed to key facts; lists kept as long as the ER requires (all monitoring markers, all key interactions).

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 the first element after <!doctype html> (L2-14).
5.2	Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML.	🟢	YAML delimited by ‘—’ lines (L3, L13).
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.	🟢	Inside an HTML comment; not rendered.
5.4	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Values trimmed; only duration quoted (contains colon).
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: naringin_2026-0924-0147_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.9.23 matches QRS.md version.
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-0924-0446 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]”	🟢	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 ‘Opus’.
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
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.5’ = nickname + version.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: naringin_2026-0924-0147_Opus_QRS.html matches file.
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	All values trimmed and unquoted except where YAML requires.

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 &)	🟢	‘Naringin for Health & Longevity - Quick Reference Sheet’ (L22).
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	‘Naringin for Health & Longevity’ (L417).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/24/2026 from 2026-0924-0446 (L421).
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Opus 5.5 (L425).
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.

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 what it is (bitter compound of grapefruit and pomelo, an inexpensive dietary supplement) and what it is used for.
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Dense condensation of ER Conclusion paragraphs 1-3.
7.3	[at_a_glance] is no longer than 70 words	🟢	69 words (script count).
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each fact maps to ER Conclusion L479-483 and Practical Considerations L421-422.
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms or specialist terms; ‘abnormal blood fats’ used instead of dyslipidemia.
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, sample sizes or p-values.
7.7	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect sizes or statistics.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Derived from ER ‘Populations who should avoid Naringin’ (L357-363).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER contraindications represented.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each item is an <li>.
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.	🟢	Concise; rationale parentheticals stripped; no trailing dash clauses.
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).	🟢	Qualifiers preserved: example drugs, ‘without clinician-supervised level monitoring’, QTc thresholds 450/470 ms, ‘under 18’, ‘within 2 weeks’.
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	ER uses no ranking notation in contraindications.
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.	🟢	Section is populated, as the ER names populations to avoid.
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 Key Interactions & Contraindications (L331-355).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All ER interactions with a Caution/Monitor class represented; ‘Caffeine: Minimal concern, no mitigation needed’ omitted as it does not change use.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each item is an <li>.
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.	🟢	Each item is label plus severity class only.
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).	🟢	Example drug/supplement lists preserved in parentheses.
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	ER uses no ranking notation in interactions.
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.	🟢	Section populated; ER names multiple interactions.
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 (L381-392).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose/duration, time of day and single vs. split dosing are the key actionable aspects.
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 exist in the ER.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All three action sets filled from ER Protocol text.

11. Time to Effect

#	Description	Result	Comments
11.1	The three sets of [time] items cover the three most important time-to-effect aspects from the ER	🟢	Covers the ER’s time-to-effect statements: lipids and weight 4-12 weeks, arterial stiffness 6 months (L418).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	All three related benefits are Low-tier; LDL and body weight (4-12 weeks) precede arterial stiffness; ordering is defensible.
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 exist in the ER.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All used time sets filled with ER-derived content.
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	ER provides time-to-effect information.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Derived from ER Expected Benefits.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	benefits_high/medium hidden; benefits_low and benefits_speculative filled.
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.	🟢	Items are bare ER benefit headings, no qualifiers or effect sizes.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content.
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.	🟢	High and Medium spans set to display: none (L521, L524).

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Derived from ER Potential Risks & Side Effects.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	risks_high/medium hidden; risks_low and risks_speculative filled.
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.	🟢	Items are bare ER risk headings; dose qualifiers are part of the ER heading.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content.
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.	🟢	High and Medium spans set to display: none (L578, L581).

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Derived from ER Monitoring Protocol & Defining Success.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 10 ER table biomarkers listed with ER targets.
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.	🟢	Cadence populated from ER L439.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Derived from ER Qualitative markers (L454-460).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All 5 ER qualitative markers listed verbatim.

Issues 24/09/2026 04:51

Pass rate 100.00%. No issues found.

Issues 24/09/2026 04:48

1. 1.2 — Timing qualifier dropped: Protocol action_2 (lines 455–462) states “Morning or with meals” without the ER’s cautious phrasing “No comparison exists; trials dosed in the morning or at meals”.
2. 4.2 / 4.3 — Invented protocol label: action_1_label (line 444) reads “Dose” instead of the ER’s bold label “Isolated naringin (trial-based)”.
3. 8.4 — Rationale parentheticals in contraindications: Stop items at lines 544–546 keep explanatory parentheticals “(no human safety data)”, “(no dosing or safety data)” and “(theoretical antiplatelet effect)” instead of just the key fact.

Fixes 24/09/2026 04:48

1. 1.2 — Timing qualifier restored: Prefixed action_2_sub with the ER phrasing “No comparison exists; trials dosed in the morning or at meals.” ahead of the levothyroxine note.
2. 4.2 / 4.3 — Protocol label corrected: Changed action_1_label from “Dose” to the ER bold label “Isolated naringin (trial-based)”.
3. 8.4 — Rationale parentheticals removed: Stripped “(no human safety data)”, “(no dosing or safety data)” and “(theoretical antiplatelet effect)” from the pregnancy, under-18 and elective-surgery stop items.