Audit: QRS - Aged Garlic Extract for Health & Longevity

Audit conducted on 06/09/2026 07:17 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.	🟢	Spot-checked every populated span against the ER: at-a-glance against ER Conclusion (537–543), protocol cells against ER 410/412/418, time cells against ER 465, benefits/risks against the ER tier headings, gates against ER 363–388, monitoring table against ER 499–508, qualitative items against ER 512–517.
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 cautious-phrasing passage is carried into the QRS in altered form; marker_8_target retains the ER’s “No established target” hedge (ER 506).
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 keep avoidance framing (line 578 “Pregnant and breastfeeding women” matches ER 388); action_3_sub keeps the ER’s “no additional blood pressure benefit over 1,200 mg” (ER 412).
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.	🟢	Gates draw only from ER Key Interactions & Contraindications; risks draw only from ER Potential Risks & Side Effects; no Benefit- or Risk-Modifying Factor content appears 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.	🟢	The QRS carries no PMIDs, citations, 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.	🟢	Measured, non-promotional register matching the ER, including the ER’s own funding caveat carried into at-a-glance.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified doses, targets and timeframes presented without hype; limitations stated plainly.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	No imperatives; gate items are stated conditions, monitoring rows are stated ranges.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No directive verbs; the footer disclaimer is the unmodified template text.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Values are surfaced as trial-derived facts (e.g., action_3_sub “Dose used in the plaque-volume and calcium trials”).
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronoun occurs anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms retained are the ER’s own necessary endpoint names; no gratuitous jargon.
2.8	Information is presented in a concise and very compact manner	🟢	Every section is reduced to short label/value pairs or single-clause list items.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-file search for “you”/”your”/”yours” — zero matches.
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 monitoring targets (ApoB below 80 mg/dL, hs-CRP below 1.0 mg/L) rather than conventional cut-offs.
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.	🟢	Weekly home blood pressure logging, a ten-marker panel and calcium scanning are presented without hedging on effort.
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.	🟢	Monitoring depth and functional ranges are well beyond general-population framing.
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 flags that the effect concentrates where pressure is “high and poorly controlled”, and risks_medium names overshoot on existing antihypertensive therapy.
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 in the title and header; “anti-aging” does not occur.
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.	🟢	Uses “gastrointestinal discomfort”, “symptomatic hypotension”, “periodontal pocket depth”; the plainer at-a-glance wording is mandated by 7.4.

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 present unmodified at lines 446, 492, 536, 570, 583, 609, 634, 638–640, 785 and in the tier <strong> labels.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template variable names present; the repeatable marker_#_* and qualitative_item_# placeholders are expanded to 10 and 6 instances respectively.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff against the template shows changes only in checklist-addressed spans; website="evidence_review", website="audit" and website="full_review" spans, the stylesheet, and the footer 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.
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_label “Standard cardiovascular dose”, action_2_label “Best time of day”, action_3_label “Higher plaque-imaging dose” match the ER bold labels at 410, 418 and 412 verbatim; caution item heads match the ER interaction labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring marker names reproduce the ER table’s first column exactly; time labels are drawn from the endpoint names in ER 465.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Full-file Unicode search returns no emoji; tiering is carried by <strong> labels and the CSS palette.
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 discretionary section is condensed: twelve ER protocol bullets reduced to three cells, thirteen benefit/risk headings to four one-line tiers, contraindication rationale stripped. Monitoring and Qualitative retain full item counts as required by 14.2 and 15.2.

---

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 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.	🟢	Opening “—” at line 3, closing “—” at line 13; the preamble text on line 2 precedes the opener.
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 echoed into the body except the ones 6.3 and 6.4 mandate.
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 nine keys trimmed; only duration: "00:03" is quoted, correctly, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: aged_garlic_extract_2026-0906-0356_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-0906-0703.
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 tier 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 &)	🟢	Line 22: “Aged Garlic Extract for Health & Longevity - Quick Reference Sheet”, matching ER frontmatter 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: “Aged Garlic Extract for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/06/2026”, the correct MM/DD/YYYY rendering of 2026-0906-0703.
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 all four ER conclusion paragraphs (537–543) into preparation, strongest effects, disputed lipid effect, tolerability and funding limitation.
7.2	[at_a_glance] is no longer than 60 words	🟢	Exactly 60 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Maps to ER 537 (preparation, deepest testing), 539 (vessels, plaque, gums, cholesterol), 541 (mild safety) and 543 (maker funding).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Uses “blood vessels”, “plaque buildup”, “healthier gums”, “maker-funded”; no acronym or clinical-register term appears.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial, author, year or sample size named.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No mmHg values, confidence intervals, hazard ratios or percentages.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All six items trace to the ER’s “Populations who should avoid Aged Garlic Extract” list at ER 381–388.
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>	🟢	Lines 573–578, six 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.	🟢	The ER’s trailing rationale “, for whom supplement-level doses are untested” (ER 388) is stripped; no dash-trailing clause remains.
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).	🟢	Retains “7–10 days”, “platelet count below 100 × 10⁹/L” and “seated systolic pressure below 100 mmHg”.
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 six such populations and the section is correspondingly populated, not 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 eight items trace to the ER bullets at 365–379.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	The ER’s protease-inhibitor bullet (ER 363, an absolute contraindication) is correctly omitted here and carried in [stop_items] instead; the remaining eight ER interaction bullets are all present.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Lines 586–599, eight 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.	🟢	Each ER bullet’s caution level, mechanism and mitigation prose is stripped, leaving label plus example list; no dash-trailing clause remains.
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 drug lists retained throughout; the ER’s plain-language glosses (“drugs that slow blood clotting:”, “angiotensin-converting enzyme inhibitors such as”) are trimmed while every named agent is kept.
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 this section.
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 interaction bullets and the section is correspondingly populated, not empty.
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 the ER Therapeutic Protocol bullets at 410, 412 and 418.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard dose, timing and the higher plaque-imaging dose are the three executable levers; the remaining ER bullets are comparative, pharmacokinetic or population-modifier commentary.
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 states 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 spans (lines 450–487) carry ER-derived content; no placeholder remains.

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	🟢	Blood pressure, plaque/periodontal endpoints and inflammatory markers are exactly the three timescales the ER states at 465.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Blood pressure and plaque/periodontal are High-tier ER benefits and lead; inflammatory markers, a Medium-tier benefit, 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 states 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 spans (lines 498–528) carry ER-derived content; values “4 weeks”, “12–18 months” and “6 weeks” match ER 465.
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 465, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All thirteen items map one-to-one onto the ER benefit headings at 153–257.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at lines 538, 544, 552 and 558.
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 item is the ER benefit heading alone; all Magnitude and Evidence prose is dropped.
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	The ER populates all four tiers, 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 eight items map one-to-one onto the ER risk headings at 283–343.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at lines 611, 614, 620 and 623.
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 item is the ER risk heading alone; all Magnitude and Evidence prose is dropped.
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; the ER’s glosses for CYP2E1 and P-glycoprotein are dropped.
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	The ER populates all four tiers, 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 at 497–508, using its Biomarker, Optimal Functional Range and Why Measure It? columns.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All ten ER rows present in ER order: home systolic blood pressure, LDL cholesterol, apolipoprotein B, high-sensitivity C-reactive protein, homocysteine, fasting glucose, HbA1c, coronary artery calcium score, INR, serum vitamin B12.
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.	🟢	Lines 776–779 reproduce the ER’s cadence sentence at 495: weekly home pressure for a month, panel at three months then six-to-twelve-monthly, calcium scanning no sooner than three years.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items trace to the ER’s “Qualitative markers worth tracking alongside the numbers” list at 512–517.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers present in ER order, with the trial attribution on the gum-bleeding item correctly stripped.

Issues 06/09/2026 07:17

Pass rate 100.00%. No issues found.

Issues 06/09/2026 07:09

1. 1.1 / 1.3 — Funding quantifier overstated: [at_a_glance] (line 438) says “Most trials were maker-funded”, strengthening the ER Conclusion’s “A large share of the trial literature was funded by the company that makes the material” (ER line 543); the ER’s own “Most of these trials” (ER line 155) applies only to the four hypertension trials.

Fixes 06/09/2026 07:09

1. 1.1 / 1.3 — Funding quantifier overstated: Changed [at_a_glance] from “Most trials were maker-funded.” to “A large share of trials were maker-funded.”, matching the ER Conclusion’s own quantifier. The section remains within the 60-word limit at exactly 60 words.