Audit: QRS - Tocopherols for Health & Longevity

Audit conducted on 04/10/2026 19:47 using AI4L / Opus 5.5

Iterations

Summary

Items	Count
Total	94
Passed	88
Failed	0
N/A	6
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.	🟢	All glance, protocol, time, benefit, risk, gate and monitoring content traced to ER passages (Conclusion, Therapeutic Protocol, Practical Considerations, Expected Benefits, Risks, Key Interactions, Monitoring).
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.	🟢	“(theoretical)” kept on every ER-theoretical interaction and contraindication; “doses not formally compared” and “long-term outcomes remain unproven” kept.
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	No claim strengthened or softened.
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 from the ER avoid list, interactions from the ER interaction list, modifying factors not relabelled.
1.5	PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact.	🟢	No PMIDs, NCT IDs, study names, experts or brands appear.
1.6	The QRS does not introduce new attributions.	🟢	No attributions added.

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 tone mirrors the ER.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢
2.4	The QRS avoids language that implies medical or clinical advice	🟢
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No direct address found.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language; drug classes keep ER labels with example drugs.
2.8	Information is presented in a concise and very compact manner	🟢	Items reduced to labels and key qualifiers.
2.9	It DOES NOT address the reader directly	🟢
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.	🟢
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.	🟢
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.	🟢
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.	🟢	Glance separates longevity-relevant null/harm findings from non-longevity benefits.
2.14	The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim.	🟢	No “anti-aging” wording.
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.	🟢	No colloquial or route-of-administration lay phrasing.

3. Template Integrity

#	Description	Result	Comments
3.1	The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why”	🟢	All fixed headings, gate headings, tier labels and column headers unchanged from template.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All template spans present (marker_# and qualitative_item_# expanded to 1–5).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff against template shows only variable content and the risks_high display:none change.

4. Formatting

#	Description	Result	Comments
4.1	When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied”	🟢	ER Risks High is empty (“No risk reaches High”); span hidden with an HTML comment quoting the ER wording.
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 “Nutritional baseline”, “Fatty liver regimen”, “Best time of day” match ER bold labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators found.
4.5	The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page.	🟢	Each section condensed to labels and key qualifiers; no section extended beyond its block.

5. Metadata

#	Description	Result	Comments
5.1	The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content.	🟢	Metadata comment directly follows <!doctype html> (line 2).
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.	🟢
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.	🟢
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 is quoted (“00:02”), which contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	qrs_prompt_version: 26.10.1
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	qrs_creation_date: 2026-1004-1903
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢
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
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢
5.11	The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4)	🟢	Opus 5.5
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢
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.	🟢

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 &)	🟢	Tocopherols 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 &)	🟢
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	10/04/2026
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Opus 5.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.	🟢

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence	🟢	Opens with “Tocopherols, the vitamin E family, are taken as supplements for disease prevention.”
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses ER Conclusion paragraphs 1–2.
7.3	[at_a_glance] is no longer than 70 words	🟢	70 words (script count).
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “imaging-dye”, “bleeding strokes” in plain language.
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢
7.7	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER avoid-populations listed.
8.3	Individual [stop_items] are formatted as <li></li>	🟢
8.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	No trailing dash clauses or rationale.
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).	🟢	Dose thresholds, age, percentile, staging and upper limits preserved.
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.	🟢	ER uses no ranking notation.
8.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision.	🟢	Section populated; ER names populations to avoid.
8.8	If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	Section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All ER interactions listed except radiotherapy (already a contraindication) and CYP3A4 drugs (ER: no interaction found).
9.3	Individual [caution_items] are formatted as <li></li>	🟢
9.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢
9.5	Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely).	🟢	Example drug lists and “(theoretical)” qualifiers preserved.
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.	🟢	ER uses no ranking notation.
9.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used.	🟢	Section populated.
9.8	If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	Section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Nutritional baseline, fatty liver regimen, best time of day.
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	ER provides more than three actionable aspects.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢

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	🟢	Menstrual pain, fatty liver, sleep quality.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	High-tier benefit first, then the two Medium-tier benefits.
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	ER provides at least three time-to-effect aspects.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from 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	ER provides time-to-effect information.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢
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.	🟢	ER benefit headings only.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheticals.
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 benefit tiers have items.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢
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.	🟢	ER risk headings only.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheticals.
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.	🟢	risks_high span set to display: none with ER-basis comment; no empty-state text shown.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All five ER table biomarkers listed; AST noted with ALT.
14.3	[monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty.	🟢	Cadence mirrors ER Monitoring narrative.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers listed verbatim.

Issues 04/10/2026 19:47

Pass rate 100.00%. No issues found.

Issues 04/10/2026 19:44

1. 1.3 / 7.4 — “Best-confirmed” strengthens ER claim: At a Glance (QRS line 433) states “Best-confirmed gains lie outside longevity”, while the ER Conclusion (line 532) says “best-replicated benefits” and flags the kidney benefit as Conflicted and the menstrual-pain trials as small and varied.

Fixes 04/10/2026 19:44

1. 1.3 / 7.4 — At a Glance wording: Changed “Best-confirmed gains lie outside longevity” to “Best-replicated gains lie outside longevity” to match the ER Conclusion’s “best-replicated benefits” (word count stays at 70).

Issues 04/10/2026 19:39

1. 7.5 — Specialist term in lede: Line 433 [at_a_glance] uses “Best-replicated gains”, a research-register term a non-specialist would not use unprompted; plain wording (e.g., “most consistently confirmed”) is required.

Fixes 04/10/2026 19:39

1. 7.5 — Specialist term in lede: Replaced “Best-replicated gains” with “Best-confirmed gains” in [at_a_glance]; word count stays at 70.

Issues 04/10/2026 19:36

1. 1.2 / 1.3 — Lower-dose hedge dropped: At a Glance (QRS line 433) states “Fatty-liver inflammation eases, also at lower doses” as fact, dropping the ER Conclusion’s cautious “lower doses appear to work about as well as higher ones” (ER line 532); lower-dose data cover liver enzymes only and doses were not formally compared.

Fixes 04/10/2026 19:36

1. 1.2 / 1.3 — Lower-dose hedge restored: In At a Glance, changed “Fatty-liver inflammation eases, also at lower doses” to “Fatty-liver inflammation eases, lower doses appearing comparable”, restoring the ER’s tentative phrasing while keeping the lede at 70 words.

Issues 04/10/2026 19:33

1. 7.2 — Not execution-oriented At-a-Glance: The at_a_glance text (line 433) condenses the Conclusion’s verdicts but omits its only execution-relevant point, that in fatty liver “lower doses appear to work about as well as higher ones” (ER line 532).

Fixes 04/10/2026 19:33

1. 7.2 — Dose point added to lede: Changed “Fatty-liver inflammation eases;” to “Fatty-liver inflammation eases, also at lower doses;” (ER line 532), and tightened wording elsewhere to stay within 70 words.

Issues 04/10/2026 19:30

1. 1.3 — Selenium testing qualifier dropped: The Monitoring cadence (line 665) lists “selenium status for men considering 400 IU/day or more” as part of the baseline panel unconditionally, while the ER (line 494) qualifies it with “where testing is available”.

Fixes 04/10/2026 19:30

1. 1.3 — Selenium testing qualifier restored: Monitoring cadence changed from “including PSA and selenium status for men considering 400 IU/day or more” to “including PSA and, where testing is available, selenium status for men considering 400 IU/day or more”, matching the ER.

Issues 04/10/2026 19:27

1. 14.1 — Selenium row not from Monitoring: Monitoring row 6 “Toenail selenium” with target “At or above the 40th percentile” (QRS lines 663-669) is absent from the ER Monitoring section and biomarker table; the cut-off is taken from ER Risk-Modifying Factors and recast as a target the ER never states.

Fixes 04/10/2026 19:27

1. 14.1 — Selenium row not from Monitoring: Removed Monitoring row 6 (“Toenail selenium”, target “At or above the 40th percentile”); selenium status remains only in the cadence line, as stated in the ER Monitoring section.

Issues 04/10/2026 19:25

1. 1.1 — INR target misstated for warfarin users: The Monitoring INR row (line 644/647) pairs the target “0.8–1.2” with “Safety check for warfarin users”, while the ER states warfarin users “follow their prescriber’s target”.
2. 2.15 — Colloquial phrase in lede: At a Glance (line 433) says “in weak kidneys” in the document’s own voice instead of the ER’s formal “impaired kidneys”.

Fixes 04/10/2026 19:25

1. 1.1 — INR target for warfarin users: Changed the INR Target from “0.8–1.2” to “Prescriber’s target (reference range 0.8–1.2)”, matching the ER note that warfarin users follow their prescriber’s target.
2. 2.15 — Formal kidney wording in lede: Replaced “in weak kidneys” with “in impaired kidneys” in At a Glance (word count unchanged at 70).

Issues 04/10/2026 19:21

1. 1.3 — Null finding broadened to family: At a Glance (QRS line 433) says “Large trials did not lower heart disease, cancer or death” for tocopherols as a whole, while the ER Conclusion (line 530) limits this to trials “of the single form in most supplements”.

Fixes 04/10/2026 19:21

1. 1.3 — Null finding scoped to form: Changed “Large trials did not lower heart disease, cancer or death” to “Large trials of the common supplement form did not lower…”, matching the ER’s “single form in most supplements”; trimmed “dietary”, “also”, “liver”, “in people” and reworded the kidney phrase to “in weak kidneys” to stay within 70 words.

Issues 04/10/2026 19:16

1. 14.2 — Selenium and AST markers missing: The ER Monitoring section names selenium status as a baseline measure for men considering 400 IU/day or more (ER line 494) and pairs ALT with AST (ER line 502), but the QRS Monitoring table (QRS lines 597-662) lists neither.

Fixes 04/10/2026 19:16

1. 14.2 — Selenium and AST markers added: Added a Monitoring row for toenail selenium (target at or above the 40th percentile; baseline for men considering 400 IU/day or more), noted AST alongside ALT in the ALT row, and added baseline PSA and selenium status to the cadence.

Issues 04/10/2026 19:13

1. 2.15 — Colloquial “weak kidneys” phrasing: At-a-Glance (line 433) says “fewer imaging-dye kidney injuries in weak kidneys”, consumer-grade wording instead of formal terminology such as “reduced kidney function”.
2. 9.2 — Anticoagulant/antiplatelet interactions missing: The ER interactions for vitamin K antagonists, antiplatelet drugs and direct oral anticoagulants (ER lines 384–386) are absent from [caution_items]; the contraindication only covers these users at doses near or above the upper limit.

Fixes 04/10/2026 19:13

1. 2.15 — Colloquial “weak kidneys” phrasing: Changed “in weak kidneys” to “with reduced kidney function” in At-a-Glance and shortened “the vitamin E nutrient family” to “the vitamin E family” to stay within 70 words.
2. 9.2 — Anticoagulant/antiplatelet interactions added: Added three caution items: “Vitamin K antagonists (warfarin, phenprocoumon)”, “Antiplatelet drugs (aspirin, clopidogrel, ticagrelor)” and “Direct oral anticoagulants (apixaban, rivaroxaban, dabigatran; theoretical)”.

Issues 04/10/2026 19:10

1. 1.3 — Fatty-liver benefit overstated: At a Glance (line 433) groups fatty-liver inflammation under “The best-replicated gains lie outside longevity”, strengthening a Medium-tier, Conflicted benefit and omitting the ER caveat that long-term liver outcomes remain unproven (ER line 532).

Fixes 04/10/2026 19:10

1. 1.3 — Fatty-liver benefit overstated: Moved fatty-liver inflammation out of the “best-replicated gains” sentence into its own sentence, “Fatty-liver inflammation also eases; long-term liver outcomes remain unproven.”, restoring the ER caveat; trimmed other wording to keep At a Glance at 70 words.

Issues 04/10/2026 19:09

1. 1.3 — “Best-proven” strengthens ER claim: At a Glance (line 433) says “The best-proven gains lie outside longevity”, while the ER Conclusion says “The best-replicated benefits lie outside longevity”; the ER notes small, varied and conflicted trials, so “proven” overstates the evidence.

Fixes 04/10/2026 19:09

1. 1.3 — “Best-proven” wording restored: Changed “The best-proven gains” to “The best-replicated gains” in At a Glance, matching the ER Conclusion wording (word count unchanged at 70).

Issues 04/10/2026 19:05

1. 7.5 — Research jargon in lede: At a Glance (line 433) uses “best-replicated”, a research-register term a non-specialist would not use unprompted; a plain-language equivalent is needed.

Fixes 04/10/2026 19:05

1. 7.5 — Research jargon in lede: Replaced “best-replicated” with the plain-language “best-proven” in At a Glance, keeping the text at 70 words.