Audit: QRS - AITC for Health & Longevity

Audit conducted on 06/09/2026 06:15 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 86
Failed 0
N/A 7
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. 🟢 Every span traced to ER: at_a_glance to ER Conclusion (L462-466), actions to ER Therapeutic Protocol (L330-346), times to ER Practical Considerations L393 and Benefits L167/L173, gates to ER L283-306, tiers to ER Benefits/Risks headings, markers to ER table L425-431.
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. 🟢 ER hedges are carried over: “No established target; change from the individual’s own baseline” (marker_7_target), “Target set by the prescriber” (marker_6_target), “appears to dissolve where iodine intake is adequate” (at_a_glance).
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 strengthening or softening. Contraindications stay absolute (“Pregnancy and breastfeeding”), and the ER’s negative human read on thermogenesis/cancer stays inside the Low tier rather than being upgraded.
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. 🟢 ER categories map straight across: Populations who should avoid AITC to Contraindications, the eight interaction bullets to Key Interactions, Benefit/Risk-Modifying Factors surfaced nowhere.
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, expert names or brand names appear in the QRS; Angocin/Repha and all citations from the ER are correctly omitted.
1.6 The QRS does not introduce new attributions. 🟢 No new attributions; the QRS contains no source, author or organisation names.

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. 🟢 Tone matches the ER’s sober, two-sided framing of a reactive compound with real irritant cost.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert, objective and data-driven throughout; concrete quantities (5-15 g, 12-74 micromoles, 90 days) without hype.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Reads as a knowledgeable guide; protocol cells describe what was tested rather than instructing.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No clinical advice language; all statements are descriptive of the evidence.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Presents rather than advises, e.g. “The regimen with placebo-controlled support”, “Taken with meals in divided doses”.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person address anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language preferred where possible (“bladder infection” concepts rendered as “recurrent urinary tract infection”, “clotting time” reasoning kept plain); remaining technical terms are ER-verbatim marker and drug-class names.
2.8 Information is presented in a concise and very compact manner 🟢 Compact throughout; tier lines are semicolon-joined headings and gate items are single clauses.
2.9 It DOES NOT address the reader directly 🟢 Confirmed: 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. 🟢 Content assumes a proactive, risk-aware reader: biomarker targets, cadence and interaction gates rather than general reassurance.
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. 🟢 Presents effortful options (fresh grating, divided dosing with meals, 8-12 week thyroid rechecks) without softening them.
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. 🟢 Not pitched at the general population; assumes willingness to test biomarkers and follow a 90-day regimen.
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. 🟢 Weighting mirrors the ER: the strongest human signals sit in Medium, the irritant risk sits in High, and the isolated-compound case is left unelevated.
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. 🟢 The term “anti-aging” does not appear; ageing framing is longevity-oriented (“Preservation of heart relaxation with age”).
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 register throughout: “oral malodour”, “mucosal”, “adverse” framing; no colloquial substitutes.

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 the template confirms all fixed headings unchanged: Protocol, Time to effect, Benefits, Risk & Side Effects, Monitoring, Qualitative Assessment, Contraindications, Key Interactions, tier labels, and Marker/Target/Why column headers.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 concrete template spans present, plus correct expansion of the repeatable marker_#* rows (1-7) and qualitative_item# (1-6).
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Non-variable spans left untouched: , , all 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 mapped to the QRS is empty; the ER supplies content for every mapped section, so no empty-state phrasing is required.
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. 🟢 ER bold labels used verbatim: “Dietary route (the best-characterised exposure)”, “Licensed herbal combination, prophylaxis”, “Preparation matters more than dose”; Monitoring rows use the ER biomarker names verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No paraphrased or invented labels; time-to-effect labels condense the ER benefit headings without renaming the underlying facts.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji present; the ER’s tier emoji and the ⚠️ Conflicted markers are correctly stripped.
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. 🟢 Free text is already at the concise end (gate items are single clauses, marker rows are ER-verbatim short strings); the list volume that remains is mandated by items 8.2, 9.2, 14.2 and 15.2.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Metadata comment opens at line 2, immediately after <!doctype html>, before any other comment or head content.
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. 🟢 YAML delimited by “—” at line 3 and line 13; the preceding title text is permitted.
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, so it does not render and is not echoed by any 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. 🟢 All values trimmed; only duration is quoted, correctly so because “00:03” contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: aitc_2026-0906-0341_Opus_ER.md, matching the source ER.
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.7.02, matching the version badge at the top of QRS.md.
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-0906-0553, in the required YYYY-MMDD-HHMM form.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 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]” 🟢 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 number with no additional qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: aitc_2026-0906-0341_Opus_QRS.html, matching the file 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: values trimmed and unquoted except the colon-bearing duration value.

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., &amp; for &) 🟢 AITC for Health & Longevity - Quick Reference Sheet, matching canonical_topic with the ampersand entity-encoded.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 header_topic is “AITC for Health & Longevity”, the ER canonical_topic, entity-encoded.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 header_subline_date is 09/06/2026, the MM/DD/YYYY form of qrs_creation_date 2026-0906-0553.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 header_subline_model is “Opus 5”, matching qrs_creator_ai_fullname.
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 carries only the title and the template subline; no badge, version stamp, alternate-names line, audit date or variant marker.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Distils the ER Conclusion (L462-466) into the compound’s dual nature, the negative isolated-compound result, the preparation point and the thyroid resolution.
7.2 [at_a_glance] is no longer than 60 words 🟢 Word count is exactly 60, within the 60-word ceiling.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct Conclusion passage: L462 (dual reactivity), L464 (unremarkable or negative), L466 (fresh preparation; thyroid worry dissolves with adequate iodine).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain-language throughout (“sharp compound”, “protective and detoxification genes”, “powerful irritant”, “thyroid worry”); the only initialism is the intervention’s own canonical name, which the sheet title defines.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years or sample sizes appear.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, relative risks or statistical results appear.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from the ER “Key Interactions & Contraindications” section, specifically the “Populations who should avoid AITC” list at ER L299-306.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All six ER avoid-populations are represented, one to one, in the same order.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each of the six items is a separate <li></li> 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. 🟢 Trailing rationales stripped, e.g. ER “…given the anaphylaxis risk from seed-protein contamination in extracts” reduced to “Confirmed mustard, horseradish or wasabi allergy”; 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). 🟢 The threshold parenthetical is preserved and merely tightened: “(filtration rate below 30 mL/min/1.73 m²)”; the “under 6 years” age cut-off is likewise 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. 🟢 The ER uses no ranking notation in this list, and none is carried through.
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 is populated, and correctly so: the ER names six populations that should avoid AITC.
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, so no explanatory HTML comment is required.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Derived from the ER “Key Interactions & Contraindications” section, the eight interaction bullets at ER L283-297.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All eight ER interactions represented, with no overlap against the Contraindications gate.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each of the eight items is a separate <li></li> 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. 🟢 Caution/Monitor tags, mechanisms and mitigation sentences 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). 🟢 Named example drugs preserved throughout: (ibuprofen, naproxen, aspirin), (omeprazole, famotidine), (co-trimoxazole, nitrofurantoin), (cinnamaldehyde, garlic allicin, ginger, capsaicin), (fish oil, garlic, ginkgo, high-dose vitamin E), and (phenytoin, glipizide) for the CYP2C9 item.
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. 🟢 The ER uses no ranking notation in these bullets, and none is carried through.
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 is populated, and correctly so: the ER documents eight interactions.
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, so no explanatory HTML comment is required.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three action cells trace to the ER “Therapeutic Protocol” section (L330-346).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 The three chosen aspects are the load-bearing ones: the best-characterised dietary exposure, the only placebo-controlled regimen, and the preparation step that governs whether any AITC is released at all.
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 Protocol section supplies fourteen bullets, well over three distinct actionable aspects, so no set is unused.
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 or empty-state phrasing 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 🟢 Covers the three time-to-effect facts in the ER: 90 days for recurrence prophylaxis (L393), day three for bronchitis (L167, L393), and immediate for oral malodour (L173).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered as the ER orders the corresponding Medium-tier benefits: urinary tract infection prophylaxis, then bronchitis, then oral malodour.
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 supplies three distinct time-to-effect aspects, so no set is unused.
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 ER’s decay detail for oral malodour (“declining over the following three hours”).
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 does provide 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 🟢 Derived from the ER “Expected Benefits” section (L151-197).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four tier variables present and correctly assigned to the ER’s High/Medium/Low/Speculative headings.
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 reduce to the ER subheadings alone; magnitudes, hazard ratios, sample sizes and mechanisms are all dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried through; the ER’s ⚠️ Conflicted markers and effect figures are stripped.
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. 🟢 The ER states “No benefit reaches High”, and benefits_high is correctly set to style=”display: none” with no empty-state text.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from the ER “Potential Risks & Side Effects” section (L221-263).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four tier variables present and correctly assigned to the ER’s High/Medium/Low/Speculative headings.
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 reduce to the ER subheadings alone; patch-test rates, the 0.8%/16.6% figures and the 153 mg challenge dose are all dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried through; the ER’s ⚠️ Conflicted marker on the thyroid item is stripped.
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, so no sub-section is empty and no span needs hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER “Monitoring Protocol & Defining Success” section (L419-431).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All seven ER biomarkers listed with ER-verbatim targets and rationales: thyroid-stimulating hormone, free thyroxine, urinary iodine concentration, urinalysis with microscopy, alanine aminotransferase, international normalised ratio, urinary dithiocarbamate metabolites.
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. 🟢 monitoring_cadence carries the ER’s schedule verbatim in substance: 8-12 weeks then every 6-12 months, urinalysis at 6 months, clotting time at 2 and 6 weeks after a dose change, and no testing for food-level intake.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER “Monitoring Protocol & Defining Success” qualitative list (L435-440).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All six ER qualitative markers listed, in ER order, with wording preserved.

Issues 06/09/2026 06:15

Pass rate 100.00%. No issues found.

Issues 06/09/2026 06:07

  1. 4.5 — Protocol subs not condensed: The three protocol sub texts (QRS lines 456-459, 470-474, 485-488) run 24-31 words each and carry whole ER sentences uncondensed, including the redundant “This is the regimen with placebo-controlled support.”, pushing the sheet past the one-page budget in the only area with discretionary slack.
  2. 10.2 — Wrong third protocol aspect: The third action cell uses “Best time of day”, whose ER bullet states “There is no circadian rationale” (ER line 338), while omitting “Preparation matters more than dose” (ER line 346), which the ER Conclusion and the QRS at-a-glance both identify as the dominant practical lever.

Fixes 06/09/2026 06:07

  1. 10.2 — Third protocol aspect replaced: The “Best time of day” action cell was replaced with the ER bullet “Preparation matters more than dose” (ER line 346), with value “Raw, or added after cooking”; the meal-timing and divided-dosing content was folded into the sub so no ER information was lost.
  2. 4.5 — Protocol subs condensed: All three action sub texts were shortened (action_1 from 24 to 22 words, action_2 from 31 to 21 words, action_3 from 25 to 22 words), removing the redundant sentence “This is the regimen with placebo-controlled support.” in favour of a single clause.

Issues 06/09/2026 06:00

  1. 1.2 / 1.3 — Hedging removed from At-A-Glance: The span at lines 436–438 states “the thyroid worry dissolves where iodine intake is adequate” and “Fresh preparation of the foods matters more than any capsule”, while ER line 466 hedges both (“appears to dissolve”; “the sensible reading is that fresh preparation matters more”).
  2. 7.2 — At-A-Glance exceeds 60 words: [at_a_glance] (lines 434–438) runs to 62 words against the 60-word limit.
  3. 11.4 — Irrelevant sentence in time_3_sub: [time_3_sub] (lines 532–535) ends with “Irritant effects are immediate.”, a side-effect timing appended under the “Oral malodour” time-to-effect cell where it does not belong.

Fixes 06/09/2026 06:00

  1. 1.2 / 1.3 — Hedging restored in At-A-Glance: Rewrote the closing sentence of [at_a_glance] from “Fresh preparation of the foods matters more than any capsule; the thyroid worry dissolves where iodine intake is adequate” to “Fresh preparation appears to matter more than capsules; the thyroid worry appears to dissolve where iodine intake is adequate”, matching the ER’s hedged wording.
  2. 7.2 — At-A-Glance word count: Condensed “Given to people on its own” to “Given alone to people” and tightened the closing sentence, bringing the span from 62 words to exactly 60.
  3. 11.4 — Irrelevant sentence removed from time_3_sub: Deleted the trailing “Irritant effects are immediate.” from the “Oral malodour” time-to-effect cell, leaving only the malodour timing.