Audit: QRS - Chia Seeds for Health & Longevity

Audit conducted on 03/09/2026 01:32 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, benefits, risks, gates, monitoring and qualitative content all trace to ER Therapeutic Protocol, Practical Considerations, Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications and 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 empty-state or hedged ER passage is carried into the QRS in altered form; evidence strength is carried by the tier labels.
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 remain absolute, interactions remain cautions, and “the protective cholesterol falls slightly” matches the ER conclusion’s own hedge.
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 only from Key Interactions & Contraindications; risk tiers only from Potential Risks & Side Effects; benefit tiers only from Expected Benefits.
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, author names, NCT identifiers or brand names appear anywhere in the QRS.
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 mirrors the ER, including its explicit statement that weight and cholesterol are unmoved.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantitative dose, timing and biomarker targets are paired with plain-language framing.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated descriptively (“Protocols … start at 7 g”, “The range used in nearly every positive trial”).
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives or prescriptions; the only advisory text is the fixed template disclaimer.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No instance of “recommended”, “advised”, “should” or “must” in the document’s own voice.
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	🟢	Clinical terms appear only where the decision gate or biomarker row requires precision; the At-A-Glance uses plain equivalents.
2.8	Information is presented in a concise and very compact manner	🟢	Gate and tier items are reduced to key facts; protocol sub-lines are one to two sentences.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” occurrences.
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 rather than conventional treatment thresholds are used throughout Monitoring.
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 tracking, soaking, four-hour drug separation and titration 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.	🟢	Omega-3 Index and hs-CRP targets assume an engaged, self-measuring reader.
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.	🟢	The At-A-Glance leads with the single supported effect and flags the unfavorable HDL shift and the absence of a lifespan effect.
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 occur; the title uses “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.	🟢	Formal terminology throughout; the plain-language wording in the At-A-Glance is required by item 7.4 and matches the ER conclusion’s own 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 heads, tier labels and table headers are byte-identical to the template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variable names are present; the repeatable marker_#_* and qualitative_item_# spans are expanded to 7 marker rows and 5 qualitative items.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	website="evidence_review", website="audit" and website="full_review" spans are unchanged; a diff against the template shows no CSS or structural edits.

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 drawn on by 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.	🟢	All eight interaction labels and the three protocol labels (“Standard dose”, “Best time of day”, “Whole versus ground”) are the ER’s bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring marker names match the ER biomarker table verbatim; time-to-effect labels correspond to the three aspects named in the ER Time to effect bullet.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters occur in the file; the ER’s ⚠️ “Conflicted” markers were correctly 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.	🟢	Section volumes sit within the template budget; long ER bullets are condensed to their key fact rather than carried in full.

---

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; it is the first element after the doctype.
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, with the descriptive text on line 2.
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 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 so 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: chia_seeds_2026-0903-0002_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-0903-0100.
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, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file’s actual 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 &)	🟢	“Chia Seeds for Health & Longevity - Quick Reference Sheet” with the ampersand correctly encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	“Chia Seeds for Health & Longevity”, matching the ER canonical_topic.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0903-0100 renders as 09/03/2026.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“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.	🟢	The header carries 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 the ER conclusion’s four load-bearing points: blood pressure, post-meal glucose, null outcomes, and the HDL fall.
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 sentence in the ER Conclusion, including “Retail quality varies” and “No demonstrated effect on lifespan”.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	HDL is rendered as “the protective cholesterol” and HbA1c as “long-term blood sugar”; no acronyms appear.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years or sample sizes.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers of any kind appear.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Taken from the “Populations who should avoid Chia Seeds” list inside that ER section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-population bullets are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Five <li> elements inside the stop_items 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 glossary parentheticals for achalasia, dysphagia and gastroparesis are stripped; no dashes or trailing 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).	🟢	The four-week impaction window, the “severe” gastroparesis qualifier and the 40 mg/day 24-hour urine oxalate threshold 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 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 five 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 eight items come from that ER section’s bulleted interaction list.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eight ER interaction bullets are present with no overlap with the contraindication gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eight <li> elements inside the caution_items 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 item is reduced to label plus effect (“additive effect”, “reduced absorption”); the ER’s mechanism sentences, mmHg figure, von Willebrand citation and “Mitigation:” clauses 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).	🟢	Every ER example-drug list is preserved verbatim inside its label.
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 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 eight 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 bullets.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, timing and form are the three decisions a reader must make; split-dosing is folded into the timing sub-line.
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 Therapeutic Protocol section contains twelve bullets, well above three.
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 fields carry ER-derived 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	🟢	Blood pressure, post-meal glucose and satiety, and lipids/inflammation are exactly the three aspects named in the ER “Time to effect” bullet.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Order follows the ER benefit tiers: blood pressure and post-meal glucose (High) before lipids and inflammation (Medium).
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.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine time fields carry ER-derived content, including the four-to-eight-week separation window.
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 in Practical Considerations.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All ten items correspond one-to-one with the ER benefit headings.
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.	🟢	Items are the ER benefit headings alone; the Magnitude lines, net readings and pooled figures are all omitted.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefit item; the ER’s “⚠️ Conflicted” markers are also 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	The ER populates all four benefit tiers.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All eight items correspond one-to-one with the ER risk headings.
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.	🟢	Items are the ER risk headings alone; the pooled estimates, case reports and mechanism sentences are omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risk item; the “⚠️ Conflicted” marker on the prostate cancer item is 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 risk tiers.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Table rows reproduce the ER Monitoring Protocol & Defining Success biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All seven ER biomarkers are present: home blood pressure, HDL, triglycerides, hs-CRP, HbA1c, Omega-3 Index and waist circumference, with targets and rationales verbatim.
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 first-month blood pressure, three-month labs and six-to-twelve-month follow-up match the ER’s second monitoring paragraph.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Taken from the ER’s “Qualitative markers worth tracking alongside the laboratory values” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers are reproduced verbatim.

Issues 03/09/2026 01:32

Pass rate 100.00%. No issues found.

Issues 03/09/2026 01:25

1. 4.2 — Interaction drug lists not verbatim: Three Key Interactions bold labels drop drug names present in the ER’s label — “hydrochlorothiazide” at QRS line 592 (ER line 311), “aspirin” at QRS line 595 (ER line 313), and “high-dose”/”extract” at QRS lines 610–612, which read “vitamin E, garlic” instead of the ER’s “high-dose vitamin E, garlic extract” (ER line 321).

Fixes 03/09/2026 01:25

1. 4.2 — Interaction drug lists restored verbatim: Re-added the drug names the ER’s bold labels carry — “hydrochlorothiazide” to the antihypertensives label, “aspirin” to the anticoagulants and antiplatelets label, and “high-dose vitamin E, garlic extract” in place of “vitamin E, garlic” in the over-the-counter antiplatelet label.

Issues 03/09/2026 01:18

1. 4.5 — Sheet overflows one A4 page: Estimated rendered height is roughly 500 mm against the ~273 mm available inside the 12 mm print padding, driven mainly by the eight multi-line Key Interactions items (lines 592–627), the 165–217-character action_*_sub and time_*_sub cells (lines 457–539), the seven two-line Monitoring rows (lines 670–759) and the 16 px At-A-Glance paragraph (lines 433–440).

Fixes 03/09/2026 01:18

1. 4.5 — Protocol cells condensed: Shortened all three action_*_sub cells, e.g. action_1_sub from “The range used in nearly every positive trial. 25 g is the dose most often used in the metabolic and functional-medicine setting. Protocols for adults over 70 start at 7 g and hold there for two weeks.” to “The range used in nearly every positive trial; 25 g is most common. Adults over 70 start at 7 g for two weeks.”
2. 4.5 — Time-to-effect cells condensed: Trimmed all three time_*_sub cells by one wrapped line each, dropping restated labels, e.g. time_2_sub lost the redundant opening “Both effects appear with the first serving.” already carried by time_2_value.
3. 4.5 — Key Interactions trimmed: Shortened the parenthetical drug lists (hydrochlorothiazide, aspirin and “high-dose”/”extract” qualifiers removed, none dropped entirely, per 9.5) and cut trailing words from three consequence phrases, e.g. “additive glucose lowering after meals” to “additive glucose lowering”.

Issues 03/09/2026 01:11

1. 13.3 — HDL expansion plus acronym: Line 640 renders the High risk as “Reduction in high-density lipoprotein (HDL) cholesterol”, elaborating on the ER heading “Reduction in HDL Cholesterol” and keeping the acronym in parentheses, which is neither concise nor consistent with marker_2_name on line 686 (“HDL cholesterol”).

Fixes 03/09/2026 01:11

1. 13.3 — HDL expansion plus acronym: Shortened the High risk item from “Reduction in high-density lipoprotein (HDL) cholesterol” to the ER’s own key fact, “Reduction in HDL cholesterol”, matching the bare form already used in the Monitoring table.

Issues 03/09/2026 01:04

1. 1.3 — Hedge dropped from Conclusion: at_a_glance (line 436) says “Weight, cholesterol and long-term blood sugar are unmoved”, strengthening the ER Conclusion’s “largely unmoved” (ER line 476) into an absolute claim that also contradicts the Low-tier benefit “Reduced Waist Circumference and Body Weight”.
2. 9.4 — Trailing elaboration in interaction item: The Marine omega-3 caution item (lines 618–621) appends “; chia does not supply DHA” after the key fact “additive rather than harmful”, carrying over scope rationale from ER line 323.

Fixes 03/09/2026 01:04

1. 1.3 — Hedge restored in At-A-Glance: Changed “Weight, cholesterol and long-term blood sugar are unmoved” to “…are largely unmoved”, matching the ER Conclusion’s own qualifier. The section remains within the 60-word budget at 59 words.
2. 9.4 — Trailing elaboration removed: Trimmed the Marine omega-3 caution item from “additive rather than harmful; chia does not supply DHA” to “additive rather than harmful”, leaving only the key fact.