Audit: QRS - Black Tea Extract for Health & Longevity

Audit conducted on 11/09/2026 06:55 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 cells, time-to-effect cells, benefit/risk tiers, gate items, all 11 monitoring rows, cadence and the six qualitative items each trace to a named ER passage.
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.	🟢	“(monitor; theoretical only)” for anticoagulants and “No established target” for fluoride are carried through 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 and lactation remain a contraindication, not a caution; the at-a-glance retains the ER’s “several reviews combining trials find no effect”.
1.4	The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc.	🟢	Contraindications come only from the ER’s “Populations who should avoid” list; interactions only from the ER interaction bullets; no modifying factor is repurposed.
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 identifiers, author names 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 matching the ER’s own phrasing.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Thresholds and targets are concrete; the at-a-glance closes on what the reader’s own starting values determine.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as evidence and ranges, not as orders.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No prescriptive verbs; monitoring targets are presented as the ER’s optimal functional ranges.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No instances of “recommend”, “advise”, “should” or “must” in document voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain-language equivalents used throughout (“after-meal” for postprandial, “inside the gut” for luminal); retained enzyme and transporter names are the ER’s verbatim interaction labels.
2.8	Information is presented in a concise and very compact manner	🟢	Every gate item, tier item and table cell is reduced to its key fact.
2.9	It DOES NOT address the reader directly	🟢	Confirmed; no direct address in any span.
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 ranges, an 11-marker panel and meal-timing detail assume a proactive, self-directed reader.
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 across the two largest meals and separation from iron sources assume willingness to schedule intake.
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.	🟢	Content is pitched well above 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.	🟢	The at-a-glance makes the trade-off explicit: modest lipid and pressure gains against an iron-absorption penalty that depends on individual status.
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; “anti-aging” appears nowhere.
2.15	The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “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.	🟢	“Capsule”, “extract”, “aminotransferase” used; no “pill”, “shot” or “by mouth” anywhere.

3. Template Integrity

#	Description	Result	Comments
3.1	The following labels and headings on the QRS are fixed and not modified: • Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment” • Gate headings: “Contraindications”, “Key Interactions” • Tier labels: “High”, “Medium”, “Low”, “Speculative” • Table column headers in Monitoring: “Marker”, “Target”, “Why”	🟢	All headings, gate headings, tier labels and column headers match the template byte-for-byte.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template variables present; marker_#* and qualitative_item# correctly expanded to 11 and 6 numbered instances.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The website="evidence_review", website="audit" and website="full_review" spans, the full stylesheet, the override link and the footer are byte-identical to the template.

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 relied 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.	🟢	Protocol labels (“Standard extract protocol”, “Best time of day”, “Single versus split dosing”) and the interaction labels carry the ER’s bold text; only the ER’s inline lay glosses are stripped, as 9.4 requires.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No invented labels; every label is the ER’s own heading or bold lead-in.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Character scan of the file returns zero codepoints in any emoji range; the ER’s ⚠️ Conflicted markers are 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.	🟢	Every section is condensed against its ER source rather than extended; no section carries ER prose through at full length and no content is appended beyond the template’s single sheet div.

---

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; the first element 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 “—” line 3, closing “—” 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 the 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:05" 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: black_tea_extract_2026-0911-0309_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-0911-0619.
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 only.
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; consistent and clean.

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: “Black Tea 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: “Black Tea Extract for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/11/2026”, correctly derived from 2026-0911-0619.
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’s own subline; the ER’s “Also known as” line 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	🟢	Condenses all four Conclusion paragraphs and closes on the three variables that decide use.
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.	🟢	Non-absorption, luminal action, modest lipid and pressure falls, null poolings, the iron penalty and the three deciding variables each map to a separate Conclusion sentence.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “pigments”, “gut”, “starch”, “iron uptake” replace theaflavin, luminal, non-heme terminology.
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	🟢	No numbers of any kind appear.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items come from the “Populations who should avoid Black Tea Extract” list in that section.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER contraindications are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <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 trailing rationales (“where total caffeine above 200 mg/day is discouraged…”, “for whom no dosing or safety data exist”) and its inline glosses are stripped; no dash-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).	🟢	Ferritin <15 µg/L, haemoglobin <12/<13 g/dL, aminotransferase above twice the upper limit, urinary oxalate above 40 mg/day, “until repletion”, “where not decaffeinated” and “under 18” 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 the contraindication list.
8.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision.	🟢	The ER identifies seven 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 twelve items come from the ER’s twelve interaction bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All twelve bullets represented; irinotecan is correctly dropped from the UGT1A1 examples because it appears as a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Twelve <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.	🟢	Separation windows, mechanism sentences, the platelet-aggregation citation and the ACE-inhibitor/ARB explanations are all stripped; no dash-trailing clauses remain.
9.5	Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Every item keeps its “(caution; …)” or “(monitor; …)” qualifier plus two named examples; none is dropped.
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 the interaction bullets.
9.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used.	🟢	The ER identifies twelve 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 map to bullets in the ER’s Therapeutic Protocol section.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, timing and single-versus-split dosing are the three executable levers; the remaining bullets are context, attribution or population modifiers.
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 well over three actionable aspects and 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 carry ER-derived content; no placeholder text 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	🟢	Lipids, blood pressure and the after-meal effects are exactly the three latencies the ER’s “Time to effect” bullet names.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	LDL and blood pressure are the ER’s two High-tier benefits, in the ER’s own order; after-meal glucose is Medium-tier and follows.
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 are present and 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 carry ER-derived content; “4–12 weeks”, “Within a day” and “First dose” each trace to the ER.
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, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All twelve entries are the ER’s own benefit headings across the four tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans 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.	🟢	Each tier is a semicolon-separated list of bare benefit names; no magnitudes, CIs, trial notes or conflict markers carried over.
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	All four tiers have items in the ER, 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 nine entries are the ER’s own risk headings across the four tiers.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans 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.	🟢	Each tier is a semicolon-separated list of bare risk names; the ER’s magnitudes, percentages and study descriptions are all 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.
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 have items in the ER, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	All rows come from the ER’s Monitoring Protocol & Defining Success biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 11 ER table biomarkers are present, in the ER’s own order, with targets and rationales condensed but intact.
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 821-824 reproduce the ER’s baseline, 12-week and 6-12-month schedule.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items come from the ER’s “Qualitative markers worth tracking” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are present, in order, essentially verbatim.

Issues 11/09/2026 06:55

Pass rate 100.00%. No issues found.

Issues 11/09/2026 06:46

1. 4.5 — Sheet overruns one A4 page: The populated QRS is roughly twice the single-page budget; the Key Interactions gate runs about 28 wrapped lines in a half-width column (lines 595–649) and the Monitoring table carries 11 rows (lines 697–841), on top of a 5-line at-a-glance, the Protocol panel and the Benefits, Risks and Qualitative cards.

Fixes 11/09/2026 06:46

1. 4.5 — Condensed over-budget sections: Trimmed the Protocol and Time-to-Effect sub-lines, four Key Interactions example lists (e.g. “theophylline, clozapine, tizanidine” → “theophylline, clozapine”), seven Monitoring cells (e.g. “Screens for the hepatotoxicity signal seen across concentrated tea extracts” → “Screens for the hepatotoxicity signal”) and the monitoring cadence. All 34 template spans, 7 contraindications, 12 interactions, 11 biomarkers and 6 qualitative markers are retained, so the completeness required by items 8.2, 9.2, 12.x, 13.x, 14.2 and 15.2 caps how far the sheet can be shortened.

Issues 11/09/2026 06:35

1. 9.5 — Interaction severity classes dropped: All twelve Key Interaction items (QRS lines 596–607) drop the ER’s parenthetical severity class and effect direction — “(caution; substantially reduced iron absorption)”, “(caution; increased drug levels)”, “(monitor; additive fall in blood pressure)” and the rest (ER 333–355) — which 9.5 allows to be shortened but never dropped entirely.

Fixes 11/09/2026 06:35

1. 9.5 — Interaction severity classes restored: Re-added the ER’s parenthetical severity class and effect direction to all twelve Key Interaction labels — e.g. “Oral iron salts and iron-rich meals” became “Oral iron salts and iron-rich meals (caution; substantially reduced iron absorption)” and “Antihypertensive drug classes” became “Antihypertensive drug classes (monitor; additive fall in blood pressure)”. The two glossed parentheticals were shortened to plain language for the one-page budget (“additive hypotension, meaning low blood pressure” → “additive low blood pressure”; “tachycardia, meaning rapid heart rate, plus tremor and insomnia” → “rapid heart rate, tremor, insomnia”).

Issues 11/09/2026 06:32

1. 1.3 — ER hedge “typically” dropped: [action_2_sub] (QRS lines 471–473) reads “Non-decaffeinated products are confined to morning and early afternoon”, whereas the ER (line 403) says “Non-decaffeinated products are typically confined to morning and early afternoon” — removing the hedge strengthens a descriptive tendency into an absolute rule.

Fixes 11/09/2026 06:32

1. 1.3 — Restored ER hedge “typically”: [action_2_sub] changed from “Non-decaffeinated products are confined to morning and early afternoon” to “Non-decaffeinated products are typically confined to morning and early afternoon”, matching the ER wording at line 403.

Issues 11/09/2026 06:25

1. 4.5 — One-page budget exceeded: The Key Interactions gate (lines 599–641) carries all twelve ER interactions with full 4–6-drug example lists in a half-width column, and several other cells (stop_items threshold parenthetical at line 574, marker_11_target at lines 823–826, the three protocol sub-texts) are longer than needed, pushing the sheet past the one-A4-page budget without applying the trimming lever that item 9.5 explicitly permits.

Fixes 11/09/2026 06:25

1. 4.5 — Key Interactions drug lists trimmed: Shortened the example drug list in each of the twelve caution_items to two or three representatives (e.g. “ferrous sulfate, ferrous fumarate, ferric sodium EDTA, plant-source iron” to “ferrous sulfate, plant-source iron”), applying the trimming lever item 9.5 permits while dropping no interaction.
2. 4.5 — Contraindication wording condensed: Tightened four stop_items without losing any threshold or qualifier — “or haemoglobin <12 g/dL in women and <13 g/dL in men) until repletion is complete” became “; haemoglobin <12 g/dL women, <13 g/dL men) until repletion”, and the oxalate, decaffeination and UGT1A1 items lost their redundant trailing words.
3. 4.5 — Monitoring and protocol cells shortened: Reduced marker_11_target to “track change from own baseline” and condensed action_1_sub and action_2_sub, removing an em-dash clause and about fifteen words of wrapping from the protocol panel.