Audit: QRS - Celery Seed Extract for Health & Longevity

Audit conducted on 16/08/2026 23:50 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.	🟢	Protocol, time-to-effect, benefit/risk tiers, contraindications, interactions, monitoring table and qualitative markers all trace to ER lines 296–326, 350–372, 409, 441–460, 478–484.
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 ER section is empty and no cautious empty-state phrasing was required; hedged wording (“Speculative” tier, “reported hyperthyroidism signal”) is carried over unchanged.
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, breastfeeding, allergy and anticoagulation remain contraindications; interaction bullets remain interactions.
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 derive only from ER “Populations who should avoid” (lines 318–326); Key Interactions only from the ER interaction bullets (lines 296–314); no modifying-factor content is 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.	🟢	The QRS contains no PMIDs, NCT identifiers, expert names or brand names.
1.6	The QRS does not introduce new attributions.	🟢	Only “the pooled analysis” and “trials” are referenced, both used generically in the ER.

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.	🟢	Neutral, evidence-weighted register matching the ER, including its explicit flagging of small and industry-funded evidence.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified targets and thresholds throughout, framed as actionable information rather than warnings.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Statements are descriptive (“Trials gave four capsules across the day”), not directives.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative instructions in any populated span.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, or “should” in populated content.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms carry ER-supplied plain-language glosses (e.g., “Active kidney inflammation (nephritis)”, “blood pressure drops on standing (orthostatic hypotension)”).
2.8	Information is presented in a concise and very compact manner	🟢	Gate and tier items are noun phrases; protocol subs are 10–14 words each.
2.9	It DOES NOT address the reader directly	🟢	Verified: no “you”/”your” in the document.
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-optimal biomarker targets (e.g., triglycerides < 80 mg/dL, TSH 0.5–2.5 mIU/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.	🟢	Split dosing 2–4× daily, daily home blood pressure logging, and a 9-marker panel 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.	🟢	Demands of the monitoring cadence and dosing schedule presuppose a motivated user.
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 limits the benefit to already-elevated blood pressure and foregrounds the allergen gate, mirroring the ER’s own weighting.
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.	🟢	“anti-aging” does not appear; the title uses “Health & Longevity”.
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 terms in At-A-Glance (“blood fats”, “blood sugar”) are required by item 7.4 and are the ER Conclusion’s own wording.

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”	🟢	Diff against [qrs_template] shows every fixed heading, gate heading, tier label and column header byte-identical.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variable names present; marker_#* and qualitative_item# expanded to 9 and 6 instances respectively.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff against the template shows no change outside the metadata block, the title, and the checklist-governed spans; CSS, footer and website= spans 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 to 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.	🟢	“Standard supplement protocol”, “Split dosing”, “Best time of day” match ER lines 352, 358, 362 verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring markers are verbatim from the ER table (lines 443–451); time-to-effect labels are drawn from the ER “Time to effect” bullet (line 409).
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code points in the file; the ER’s “⚠️ Conflicted” markers were 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 reduced to its minimum consistent with the completeness requirements of items 8.2, 9.2, 12.2, 13.2, 14.2 and 15.2; no section carries surplus prose.

---

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 <!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.	🟢	Opening --- at line 3, closing --- at line 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; no metadata value is repeated in <head> or <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:03" is quoted, and it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: celery_seed_extract_2026-0825-2142_Opus_ER.md, matching the ER’s own filename field.
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-2344.
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)	🟢	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]”	🟢	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 qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file on disk: celery_seed_extract_2026-0825-2142_Opus_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.	🟢	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: “Celery Seed Extract 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 &)	🟢	Line 417: “Celery Seed Extract for Health & Longevity”, matching ER frontmatter line 8.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/16/2026” from qrs_creation_date 2026-0816-2344.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “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 contains only the title and the template subline; 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	🟢	Condenses ER lines 480–484: mechanism, who benefits, secondary signals, evidence limits, allergen gate.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct Conclusion sentence (ER lines 480, 482, 484).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “oily aroma compound”, “blood fats”, “blood sugar” replace 3nB, lipids and glucose.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, sample sizes or p-values.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Only qualitative magnitude (“a meaningful fall”, “smaller signals”).

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All nine items map 1:1 to ER lines 318–326.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All nine “Populations who should avoid” bullets are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Nine <li> elements inside the span (lines 554–566).
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.	🟢	Rationales stripped (e.g., ER “given the uterine-stimulant classification of celery seed oil” and “on the basis of absent safety data” removed); no trailing dash 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).	🟢	eGFR < 60 mL/min/1.73 m², TSH outside 0.4–4.0 mIU/L, systolic < 110 mmHg, two-week surgery window and the Apiaceae example list 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 identifies nine such populations and the section is correspondingly 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 1:1 to ER lines 296–314 in the same order.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	No item duplicates a contraindication; the photosensitizer and anticoagulant entries are the ER’s broader interaction bullets, not the narrower avoid-population entries.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Ten <li> elements inside the span (lines 574–584).
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 reduced to the drug class alone; mechanism, monitoring intervals and mitigation prose from the ER are all stripped.
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).	🟢	All ER example drug lists retained verbatim (antihypertensives, anticoagulants, CYP1A2 substrates, photosensitizers, urate-lowering drugs, BP-lowering supplements).
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 identifies ten interactions and the section is correspondingly 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 ER Therapeutic Protocol lines 352, 358, 360, 362.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, dosing frequency and timing — the three decisions needed to execute the protocol.
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 eleven protocol bullets; 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.	🟢	“150–1,500 mg/day” (ER line 352), “2–4 doses daily” (ER lines 358, 360), “With food, morning and early evening” (ER line 362), each with a supporting sub-line.

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, triglycerides and uric acid — exactly the three endpoints named in ER line 409.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Blood pressure (High tier) → triglycerides (Medium, blood lipid improvement) → uric acid (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 are present in the ER; all sets are used.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	“3–6 weeks” and “4–12 weeks” both trace to ER line 409; the uric acid sub also draws on ER line 170.
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 data (line 409), so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All nine items are the ER’s own benefit sub-headings (lines 144–198).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at the correct tiers, matching the ER’s 🟩🟩🟩 / 🟩🟩 / 🟩 / 🟨 grouping.
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 bare ER heading; no magnitudes, SMDs, confidence intervals or trial details carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheticals remain; the ER’s “⚠️ Conflicted” flag on Blood Lipid Improvement is dropped.
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 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 nine items are the ER’s own risk sub-headings (lines 222–274).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated at the ER’s tiers.
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.	🟢	Bare headings only; the 62 percent systemic-reaction figure, odds ratio and mmHg magnitudes are not carried over.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	“(Phytophotodermatitis)” and the “⚠️ Conflicted” flag are stripped from the Low tier.
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 tiers contain items in the ER.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Rows reproduce the ER Monitoring Protocol & Defining Success table (lines 443–451).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All nine ER biomarkers present, with ranges and rationale verbatim: blood pressure, uric acid, triglycerides, LDL, fasting glucose, TSH, eGFR, sodium/potassium, ALT/AST.
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.	🟢	Line 733 reproduces ER line 439: daily home BP for four weeks then weekly; full panel at 12 weeks then every six to twelve months.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Items reproduce the ER “Qualitative markers worth tracking” list (lines 455–460).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers present, in the ER’s order and wording.

Issues 16/08/2026 23:50

Pass rate 100.00%. No issues found.