Audit: QRS - Lactobacillus rhamnosus for Health & Longevity

Audit conducted on 06/09/2026 03:28 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. 🟢 Spot-checked every populated span against the ER: protocol values (ER 354, 360, 364), time-to-effect (ER 379, 403, 429), benefit/risk tier headings (ER 149-229, 251-295), contraindications (ER 329-334), interactions (ER 313-325), biomarker table (ER 431-438), qualitative list (ER 442-446). All literally supported.
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. 🟢 Cautious ER phrasing carried through, e.g. “no pharmacological interaction” (ER 319) and “No established target; individual’s own baseline” (ER 438).
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 tier, threshold, or gate is up- or down-graded; “Absolute contraindication in most protocols” (ER 317) is rendered as a hard [stop_items] entry, not a caution.
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’s “Populations who should avoid” list, interactions from the ER interaction bullets, risks from Potential Risks & Side Effects. No cross-category migration.
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, study names, author names, NCT identifiers, or brand names appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No named person, institution, or organisation is credited anywhere in the QRS.

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. 🟢 Matches the ER’s sober, deflationary register (“Results do not transfer between products”, “Nothing in the human record speaks to lifespan”).
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert and data-driven (explicit CFU ranges, biomarker targets) while remaining readable; the strain-specificity caveat is stated plainly enough to act on.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents thresholds and gates as evidence, with no clinician-style directives.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperative or prescriptive constructions; the footer disclaimer is the template’s fixed text.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Fields state what protocols and trials used, not what should be done.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the file (verified by search for you/your/yours/yourself).
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language throughout; the only technical terms retained are biomarker names and severity classes that item 4.3 and item 8.5 require to be kept exact.
2.8 Information is presented in a concise and very compact manner 🟢 All fields are short noun phrases or single clauses; no field exceeds one sentence plus a sub-line.
2.9 It DOES NOT address the reader directly 🟢 Confirmed — no direct address anywhere in the QRS.
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 is framed for a proactive optimiser: dose range, timing, monitoring cadence, and the explicit note that the adult signal is weaker.
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. 🟢 Protocol assumes willingness to follow trial-matched dosing, meal timing, and an eight-to-twelve-week monitoring panel.
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. 🟢 No simplification for a casual reader; biomarker targets and severity classes are retained.
2.13 Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. 🟢 [at_a_glance] explicitly separates the paediatric signal from the adult one and states that nothing in the human record speaks to lifespan — exactly the divergence relevant to this audience.
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 string “anti-aging” does not appear; the header frames the topic as “Health & Longevity”.
2.15 The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. 🟢 Formal register throughout (“colony-forming units”, “erythrocyte sedimentation rate”, “infective endocarditis”); no consumer-grade 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” 🟢 All fixed strings verified against the template: “Protocol” (571 in template / line 440), “Time to effect” (477), “Benefits” (519), “Risk & Side Effects” (571), “Monitoring” (590), “Qualitative Assessment” (676), “Contraindications” (539), “Key Interactions” (553), tier labels High/Medium/Low/Speculative, and Marker/Target/Why headers (594-596).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All template variable spans are present: 57 data-qrs-var spans, matching the template’s 34 single-instance vars plus 6 marker rows (18) and 5 qualitative items.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 The non-checklist spans are untouched: website="evidence_review", website="audit", and website="full_review" all retain their template values.

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 N/A — no source ER section relied on by the QRS is empty; every mapped ER section has content.
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 reproduced verbatim: “Standard dose”, “Best time of day”, “Single versus split dosing” (ER 354, 360, 364) and all six interaction labels including their parenthetical drug lists (ER 313-325).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No label is invented; the time-to-effect labels (“Antibiotic-associated diarrhea”, “Mood and metabolic endpoints”, “Inflammatory markers”) are literal ER phrases from lines 403 and 429, and all six biomarker names are verbatim from the ER table.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji characters anywhere in the file; the ER’s 🟩/🟥/🟨/⚠️ 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. 🟢 Per-section budgets are respected — 7 contraindications, 6 interactions, 4 benefit lines, 4 risk lines, 6 biomarker rows, 5 qualitative items, all at 9-9.5pt within the template’s single-sheet layout.

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. 🟢 The metadata comment opens on line 2, immediately after <!doctype html> on line 1, and precedes all other 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. 🟢 Opening --- on line 3, closing --- on line 13; the preceding “QRS — Metadata (invisible, parsed by audit tooling)” text sits before the opening delimiter.
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. 🟢 The block is inside an HTML comment and nothing on the sheet reproduces it.
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; the only quoted value is duration: "00:03", which requires quoting because it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: lactobacillus_rhamnosus_2026-0906-0002_Opus_ER.md (line 4) matches 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 (line 5) matches 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-0300 (line 6) is well-formed YYYY-MMDD-HHMM.
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 (line 7).
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 (line 8).
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: lactobacillus_rhamnosus_2026-0906-0002_Opus_QRS.html (line 9) matches 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 — no stray whitespace or unnecessary quoting on any of the nine frontmatter values.

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 &) 🟢 <title> reads “Lactobacillus rhamnosus for Health & Longevity - Quick Reference Sheet” — canonical_topic (ER frontmatter line 8) 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] (line 417) reads “Lactobacillus rhamnosus for Health & Longevity”, correctly entity-encoded.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 qrs_creation_date 2026-0906-0300 renders as “09/06/2026” (line 421), correct MM/DD/YYYY.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 [header_subline_model] reads “Opus 5” (line 425), 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. 🟢 The header carries only the title and the template’s fixed subline; no badge, AKA line, version stamp, 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 🟢 Condenses the ER Conclusion (ER 468-472) into the decision-relevant core: what is firmest, in whom, non-transferability between products, the safety split, and the absence of lifespan data.
7.2 [at_a_glance] is no longer than 60 words 🟢 54 words — within the 60-word cap.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct ER Conclusion passage: “live gut bacterium … long clinical record” (ER 468), “firmest findings … adult signal is weaker” (ER 468), “results do not transfer between products” (ER 472), “safety picture is favorable … serious for those whose are not” (ER 470), “Nothing in the human record speaks to lifespan” (ER 470).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms or specialist classifications; uses “gut bacterium”, “antibiotic-caused loose stools”, “airway infections”, “defenses”.
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 relative risks, odds ratios, confidence intervals, or absolute risk figures.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All seven items trace to the ER Key Interactions & Contraindications section (ER 317 and 329-334).
8.2 [stop_items] represent the Contraindications from the ER 🟢 The ER’s six “Populations who should avoid” bullets are all represented; the first is split into immunosuppressive therapy and neutrophil count as separate gates, and the drug list is taken from ER 317.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 All seven items are discrete <li> elements inside the [stop_items] span (lines 542-548).
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. 🟢 Each item is a bare noun phrase; no rationale, mechanism, citation, or trailing dash clause survives.
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). 🟢 Decision-bearing qualifiers preserved: “below 0.5 × 10⁹/L”, “(Mayo endoscopic subscore 3)”, and the immunosuppressant drug list “(tacrolimus, ciclosporin, high-dose corticosteroids, biologics)”. The only dropped parenthetical, “(infection of the heart’s inner lining or valves)”, is a glossary definition rather than a qualifier that changes applicability, and item 8.4 requires such elaborations to be stripped.
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 N/A — the ER’s Key Interactions & Contraindications section uses no ranking notation inside parentheses.
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. 🟢 Not applicable as an exemption — the ER names six populations that should avoid the intervention and the section is correctly populated rather than empty.
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 N/A — the section is not empty; seven [stop_items] are present.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 All six items trace to the ER interaction bullets at ER 313-325.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All seven ER interaction bullets are represented except Immunosuppressants, which is correctly excluded because it is carried as a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 All six items are discrete <li> elements inside the [caution_items] span (lines 556-561).
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 reduces to the ER’s own verdict word or phrase (“timing matters”, “monitor”, “no pharmacological interaction”, “potentiating”, “additive”, “timing”); all mechanistic follow-on sentences are 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 intact: “(amoxicillin, clarithromycin, ciprofloxacin)”, “(fluconazole, nystatin)”, “(omeprazole, famotidine)”, “(prebiotic fibers, other probiotic strains)”, “(fecal microbiota transplantation, colonoscopy preparation)”.
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 N/A — the ER’s Key Interactions & Contraindications section uses no ranking notation inside parentheses.
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. 🟢 Not applicable as an exemption — the ER names seven interactions and the section is correctly populated rather than empty.
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 N/A — the section is not empty; six [caution_items] are present.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three action sets derive from the ER Therapeutic Protocol section (ER 354, 360, 364).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, administration timing, and dosing frequency are the three actionable levers in the ER Protocol section; the remaining bullets (approach philosophy, origin, persistence, polymorphisms, sex, age, baseline biomarkers, pre-existing conditions) are contextual rather than actionable.
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 N/A — the ER Therapeutic Protocol section supplies three or more distinct actionable aspects; 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 action fields carry ER-derived content; no placeholder or empty-state 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 🟢 Covers the two aspects in the ER Practical Considerations “Time to effect” bullet (ER 403) plus the inflammatory-marker interval from ER 429 (“the shortest interval over which trials detected change”).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered by benefit tier: antibiotic-associated diarrhea (ER High), mood and metabolic endpoints (ER Medium), inflammatory markers (ER Low).
11.3 If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A N/A — the ER supplies three distinct time-to-effect aspects; 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 time fields carry ER-derived content; the subs quote ER 379, ER 403, and ER 429 respectively.
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 N/A — the ER provides time-to-effect information (Practical Considerations line 403 and Monitoring Protocol line 429).

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All four tiers mirror the ER Expected Benefits sub-section headings (ER 149-229).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four variables are present and populated (lines 521-532).
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 condensed ER benefit headings with no effect sizes, mechanisms, or study detail.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses appear in any benefits item; the ER’s magnitude lines and ⚠️ Conflicted markers 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. N/A N/A — all four benefit tiers have items in the ER Expected Benefits section; none is empty.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All four tiers mirror the ER Potential Risks & Side Effects sub-section headings (ER 251-295).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four variables are present and populated (lines 573-584).
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 condensed list of ER risk headings; no frequencies, odds ratios, or mechanistic detail carried over.
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 item; the ER magnitude lines and ⚠️ Conflicted marker are 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 N/A — all four risk tiers have items in the ER Potential Risks & Side Effects section; none is empty.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 All six rows derive from the ER Monitoring Protocol & Defining Success biomarker table (ER 431-438).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All six ER table rows are present with matching targets: hs-CRP below 1.0 mg/L, fecal calprotectin below 50 µg/g, neutrophils above 1.5 × 10⁹/L, HbA1c 4.8-5.4%, ESR below 15 mm/hr men / 20 women, fecal sIgA no established target.
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] (line 670) condenses ER 429: baseline panel, eight-to-twelve-week recheck, six-to-twelve-month intervals, and blood cultures on unexplained fever.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 All five items derive from the ER qualitative-marker list at ER 442-446.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers are present: bowel habit, post-meal bloating and gas, upper-respiratory episode frequency and duration, perceived stress and mood stability, and digestive tolerance of an antibiotic course.

Issues 06/09/2026 03:28

Pass rate 100.00%. No issues found.

Issues 06/09/2026 03:22

  1. 2.5 — Monitoring “Why” cell gives instruction: [marker_5_why] at line 652 reads “Slower-moving marker; use if deep-seated infection suspected”, turning the ER’s descriptive “useful when a deep-seated infection is suspected” (ER line 437) into an instruction to the reader.

Fixes 06/09/2026 03:22

  1. 2.5 — Monitoring “Why” cell instruction: Changed [marker_5_why] from “Slower-moving marker; use if deep-seated infection suspected” to “Slower-moving marker; useful when deep-seated infection is suspected”, restoring the ER’s descriptive phrasing.

Issues 06/09/2026 03:16

  1. 1.2 / 1.3 — Lifespan claim overstated: [at_a_glance] (line 433) says “Nothing speaks to lifespan”, dropping the ER Conclusion’s scoping “in the human record” (ER line 470); the QRS itself lists “Lifespan extension” as a Speculative benefit, so the unqualified form contradicts its own Benefits card.
  2. 1.3 — Antifungal interaction overstated: [caution_items] (line 558) reduces the ER’s “No pharmacological interaction” (ER line 319) to “no interaction”, broadening a scoped claim.
  3. 2.6 / 2.9 — Marker target addresses reader: [marker_6_target] (line 660) reads “No established target; track own baseline”, an unattached imperative directed at the reader; the ER (line 438) writes “track change from the individual’s own baseline”.
  4. 11.4 — Time-to-effect sub duplicates value: [time_1_sub] (line 489) “Protection applies from the first days.” restates [time_1_value] (line 486) “First days of the course” and carries no additional ER content.

Fixes 06/09/2026 03:16

  1. 1.2 / 1.3 — Lifespan claim rescoped: Changed [at_a_glance] from “Nothing speaks to lifespan.” to “Nothing in the human record speaks to lifespan.”, restoring the ER Conclusion’s scoping clause (at-a-glance now 53 words, within the 60-word budget).
  2. 1.3 — Antifungal interaction rescoped: Changed the antifungals [caution_items] entry from “no interaction” to “no pharmacological interaction”, matching the ER’s scoped wording.
  3. 2.6 / 2.9 — Marker target no longer imperative: Changed [marker_6_target] from “No established target; track own baseline” to “No established target; individual’s own baseline”, removing the imperative directed at the reader.
  4. 11.4 — Time-to-effect sub made substantive: Replaced [time_1_sub] “Protection applies from the first days.” with “Trial windows spanned the course plus a week.”, drawn from the ER’s Discontinuation & Cycling section, so the sub no longer restates the value.

Issues 06/09/2026 03:07

  1. 4.5 — Sheet overruns one A4 page: Un-condensed fields push the estimated rendered height to roughly 1.7 A4 pages — [action_2_sub] (137 chars, QRS line 461) and [action_3_sub] (148 chars, QRS line 472) carry near-verbatim ER sentences into one-third-width cells, [monitoring_cadence] (230 chars, QRS line 669) reproduces ER line 429 almost intact, [marker_6_target] (QRS line 659) is a 70-char ER phrase, [at_a_glance] runs five rendered lines at 16px, and the first contraindication plus the Low benefits row wrap to three and two lines respectively.

Fixes 06/09/2026 03:07

  1. 4.5 — Protocol sub-cells condensed: Trimmed [action_1_sub] (107→57 chars), [action_2_sub] (137→71) and [action_3_sub] (148→64) from near-verbatim ER sentences to the load-bearing fact, cutting the protocol row from four rendered lines to two.
  2. 4.5 — Time-to-effect sub-cells condensed: Shortened [time_1_sub], [time_2_sub] and [time_3_sub] (e.g. “Trials ran three to six months before measuring, so shorter trials are uninformative” → “Shorter trials are uninformative”), removing wording already carried by the adjacent value cell.
  3. 4.5 — At-A-Glance tightened: Reduced [at_a_glance] from 58 to 51 words by folding the population caveat into an em-dash clause and dropping “in the human record”.
  4. 4.5 — Monitoring cadence condensed: Replaced the near-verbatim ER sentence in [monitoring_cadence] (230→166 chars) with the schedule and the fever trigger only.
  5. 4.5 — Monitoring cells shortened: Trimmed [marker_1_why], [marker_2_why], [marker_3_why], [marker_4_why], [marker_5_target], [marker_5_why], [marker_6_target] and [marker_6_why] so each fits its column, while keeping every marker, target and rationale from the ER table.
  6. 4.5 — Decision-gate items shortened: Split the combined immunosuppression/neutrophil contraindication into two shorter items and trimmed the remaining [stop_items] and the trailing verdicts in [caution_items]; all thresholds, staging and example-drug parentheticals were preserved and the ER bold labels left verbatim.
  7. 4.5 — Low benefits row shortened: Condensed [benefits_low] (194→155 chars) to the five ER benefit names without their trailing population qualifiers.
  8. 4.5 — Qualitative items shortened: Trimmed [qualitative_item_1], [qualitative_item_3] and [qualitative_item_5] so each renders on a single line.