Audit: QRS - Eleuthero for Health & Longevity

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

Iterations

Summary

Items	Count
Total	93
Passed	85
Failed	0
N/A	8
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 spans traced to ER source: protocol cells to ER Therapeutic Protocol (lines 390–398), time-to-effect to ER benefit entries (lines 161, 169, 193), benefit/risk tiers to ER headings (lines 159–221, 253–305), gates to ER Key Interactions & Contraindications (lines 323–364), all 10 markers and cadence to ER monitoring table (lines 475–488).
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.	🟢	Disputed-direction items are carried as neutral tier descriptors (“blood pressure changes in treated hypertension”, “blood glucose disturbance”), and DHEA-sulfate keeps the ER’s “No established target”.
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”).	🟢	The ER’s absolute contraindication on calcineurin inhibitors / immunosuppression (ER line 329) remains in the Contraindications gate, not the Key Interactions gate; pregnancy and lactation remain a contraindication.
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.	🟢	No content from ER Benefit-Modifying Factors or Risk-Modifying Factors appears in the gates or risk card; gates draw exclusively from ER Key Interactions & Contraindications.
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.	🟢	The QRS carries no PubMed IDs, citations, author names, NCT identifiers or brand names anywhere.
1.6	The QRS does not introduce new attributions.	🟢	Sub-lines reference “the single positive trial” and “a trial of eleuthero leaf given with a second herb” without naming any new source.

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.	🟢	Reserved, non-promotional register matching the ER’s sceptical framing of the adaptogen claim.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Tiered benefits/risks, numeric protocol values and marker targets give the reader the material to decide without advocacy.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Cadence and protocol cells are stated descriptively (“Last dose before 14:00”, “Baseline before the first dose”), not as orders.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No prescriptive verbs in the QRS body; monitoring is framed as markers and targets rather than instructions.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	A scan of the rendered body returns no instance of “should”, “must”, “recommend”, “advise”, “ensure”, “consider” or “consult”.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to drug and marker names that carry the decision; the At-A-Glance lede is fully lay-readable.
2.8	Information is presented in a concise and very compact manner	🟢	Tier lines are semicolon-joined single list items; gate items are bare noun phrases; magnitudes and citations are stripped throughout.
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.	🟢	Standardisation target, marker-content verification and a 10-marker panel address an optimiser audience, not a casual buyer.
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.	🟢	Twice-weekly home blood pressure, an 08:00 fasted hormone draw and serum digoxin rechecks assume a high-effort audience.
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.	🟢	Functional ranges (fasting glucose 75–86 mg/dL, hs-CRP under 0.5 mg/L) are tighter than conventional cut-offs, as in the ER.
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 states the single clear result faded and that remaining claims conflict — the weighting a risk-aware optimiser needs.
2.14	The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim.	🟢	“anti-aging” does not occur; the title uses “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)”; “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.	🟢	“Antidiabetic medications”, “Antihypertensive medications”, “central nervous system depressants”, “Over-the-counter” are used; no “pills”, “shot” or “taken 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 match the template verbatim (lines 445, 490, 540, 570, 588, 621, 648, 652–654, 804); every populated tier keeps its “Medium: / Low: / Speculative: “ label.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Set comparison against the template returns no missing variable; the only extras are the intended repeats of marker_#_* (10 rows) and qualitative_item_# (6 items).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	website="evidence_review", website="audit" and website="full_review" are untouched; a diff of lines 15–410 against the template differs only at page_title.

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 ER section consumed by the QRS is empty; the unpopulated High tiers are sub-sections governed by items 12.5 / 13.5, which explicitly forbid empty-state phrasing.
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.	🟢	“Standard dose”, “Best time of day” and “Standardisation target” reproduce the ER bold labels at lines 390, 396 and 394 exactly.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Marker names reproduce the ER biomarker column verbatim; time-to-effect labels are drawn from the corresponding ER benefit headings.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji in the file; the ER’s “⚠️ Conflicted” markers were stripped from the benefit and risk tier lines.
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.	🟢	Content-dense sections were condensed rather than expanded: drug example lists trimmed (e.g. antidiabetics to insulin and metformin), the DHEA-sulfate target reduced from the ER’s 30-word cell, and all magnitudes, effect sizes and citations dropped from the tier lines.

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.	🟢	Comment opens at line 2, immediately after <!doctype html> at line 1, and closes at line 14 before the template comment at line 16.
5.2	Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML.	🟢	Opening --- at line 3, closing --- at line 13; the descriptive text on line 2 precedes the opener.
5.3	The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet.	🟢	Enclosed in an HTML comment; no metadata value is repeated in the header, footer or any span.
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: "00:02" is quoted, which is required because the value contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: eleuthero_2026-0920-0207_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.9.11, matching the version badge at the head 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)	🟢	Line 6: qrs_creation_date: 2026-0920-0437, conforming to the required pattern.
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 number, no context-window or other qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: eleuthero_2026-0920-0207_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 across all nine keys; git_user and git_issue are unquoted 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: Eleuthero for Health & Longevity - Quick Reference Sheet, matching ER canonical_topic with the ampersand encoded.
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: Eleuthero for Health & Longevity.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 09/20/2026, the correct reformatting of 2026-0920-0437.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: Opus 5, matching the frontmatter value.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	The header block (lines 415–428) contains only the title and the template subline; the ER’s “Also known as” list was not carried over.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Four clauses condensing ER lines 519–522: what it is, the one clear result and its fade, the conflicted claim set, and the safety picture.
7.2	[at_a_glance] is no longer than 60 words	🟢	58 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	“Far Eastern shrub” (ER 519); “only one controlled trial … faded” (ER 521); “conflict or come from multi-herb formulas” (ER 521); “side effects match placebo” and substitution harm (ER 521, 430).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “general health questionnaire”, “multi-herb formulas” and “substituted plant” replace the ER’s SF-36v2, formula names and Periploca sepium.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No author name, year, sample size or p-value appears.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No percentages, risk ratios or confidence intervals.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All eight items map to the ER “Populations who should avoid Eleuthero” list at lines 357–364.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All eight ER avoidance populations are present, and the ER’s one absolute contraindication among the interaction bullets (calcineurin inhibitors / immunosuppression, line 329) is represented by the third item.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Eight discrete <li> elements at lines 573–583.
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 dashes, rationale or citations; each item is a bare population or condition.
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).	🟢	“(sustained ≥ 160/100 mmHg)”, “during a manic or mixed episode”, “under active endocrine therapy”, “without access to serum-level monitoring”, “under 12 years” and “within the next 14 days” are all retained.
8.6	When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol.	N/A	The ER uses no ranking notation in this section; the sole “>” analogue is the threshold “at or above 160/100 mmHg”, which is a value, not a ranking.
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 section is populated, as required — the ER names eight avoidance populations.
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 fifteen items map to the ER interaction bullets at lines 323–353.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Fifteen of the ER’s sixteen interaction bullets are carried; the immunosuppressant / calcineurin-inhibitor bullet is correctly omitted because it is an absolute contraindication already held in [stop_items].
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Fifteen discrete <li> elements at lines 591–611.
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.	🟢	The ER’s “Caution, monitor” verdicts, mechanisms and mitigations are stripped, as is the “Other interventions —” prefix on the final bullet and the digoxin definitional gloss.
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 bullet that carries an example list keeps one, shortened to fit (e.g. antidiabetics to “insulin, metformin”, blood-sugar-lowering supplements to “berberine, chromium”); none is dropped entirely.
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’s parentheses in this section contain only comma-separated drug and supplement examples; no ranking notation is used.
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 section is populated, as required — the ER names sixteen 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.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three cells trace to the ER Therapeutic Protocol bullets at lines 390–398.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose, timing and standardisation target — the three bullets that determine what is taken, when, and whether the product matches trial material.
10.3	If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	The ER Therapeutic Protocol section supplies twelve bullets, so 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 populated; the sub-lines add the dried-root alternative (ER 392), dose splitting (ER 398) and the marker-content caveat (ER 394).

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	🟢	Social functioning at 4 weeks, endurance at 8 weeks and memory at 12 weeks are the only three benefits in the ER with a stated trial duration.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered Medium tier (social functioning) then Low tier (endurance, then memory), following the ER’s own tier and within-tier ordering.
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 exist in the ER, so 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 populated; each sub-line restates the ER’s own caveat on the finding (fade by eight weeks, single positive trial, leaf plus second herb).
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 data (lines 163, 169, 193, 447), so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All tier entries reproduce ER Expected Benefits headings at lines 155–221.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 542, 545, 550 and 558.
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 entry is the bare ER heading; the “Magnitude” paragraphs, p-values, risk ratios and citations are all dropped, and “Neuroprotection Through Increased Brain-Derived Neurotrophic Factor” is reduced to “neuroprotection”.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefit tier line.
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.	🟢	benefits_high carries style="display: none" with an HTML comment citing the ER’s “No benefit reaches High”; no empty-state text is rendered.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All tier entries reproduce ER Potential Risks & Side Effects headings at lines 249–305.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 623, 626, 629 and 637.
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 entry is the bare ER heading; incidence percentages, the 28.7% ratio fall and all citations are 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 risk tier line; the ER’s “(salt-balance hormone)” gloss is not carried.
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 carries style="display: none" with an HTML comment citing the ER’s “No risk reaches High”; no empty-state text is rendered.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	All rows trace to the ER Monitoring Protocol & Defining Success table at lines 477–488.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All ten ER biomarkers are present in ER order, with the “Optimal Functional Range” and “Why Measure It?” values carried across; only the ER’s “Context/Notes” column and the long DHEA-sulfate target are condensed.
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.	🟢	Line 793 reproduces the ER cadence paragraph (lines 473–475): baseline, twice-weekly then monthly blood pressure, 8-week and 6-month panels, 6–12 monthly thereafter, and the digoxin recheck.

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 alongside the laboratory values” list at lines 492–497.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are present, verbatim and in ER order.

Issues 20/09/2026 05:06

Pass rate 100.00%. No issues found.

Issues 20/09/2026 04:58

1. 4.3 — Digoxin marker label paraphrased: marker_9_name at line 764 reads “Serum digoxin, if prescribed” where the ER biomarker table (line 487) labels the row “Serum digoxin, only if taking digoxin”; the conditional qualifier has been reworded rather than carried over.

Fixes 20/09/2026 04:58

1. 4.3 — Digoxin marker label restored: Changed marker_9_name from “Serum digoxin, if prescribed” to the ER’s verbatim row label “Serum digoxin, only if taking digoxin”.

Issues 20/09/2026 04:53

1. 1.3 — Memory time-to-effect overstated: time_3_sub (QRS lines 529-531) reports “Figure recall improved over twelve weeks” without the ER’s caveat that the trial used eleuthero leaf with a second herb and is therefore indirect (ER line 193), and appends the ER’s general “a judgement before one month has no trial basis” clause (ER line 447) to a memory-specific cell.

Fixes 20/09/2026 04:53

1. 1.3 — Memory time-to-effect caveat restored: Replaced time_3_sub “Figure recall improved over twelve weeks; a judgement before one month has no trial basis.” with “Figure recall improved over twelve weeks, in a trial of eleuthero leaf given with a second herb.”, restoring the ER’s indirectness caveat and removing the misattached general time-to-effect clause.

Issues 20/09/2026 04:44

1. 4.5 — Sheet overruns the A4 budget: The populated sheet carries ~750 words of visible body text plus a 15-item Key Interactions gate (lines 590-612), an 8-item Contraindications gate, a 10-row biomarker table (lines 658-789) and a 6-item Qualitative card; estimated rendered height is roughly twice the 273 mm A4 print area at the stylesheet’s 11pt/1.42 and 9.5pt card type.
2. 1.3 / 2.5 — Hedge dropped, instruction issued: [action_2_sub] (line 470) renders the ER’s “which argues for splitting the daily amount into two doses, morning and midday” (ER line 398) as the bare imperative “split into morning and midday doses”, strengthening the claim and shifting from presenting information to advising.
3. 2.6 / 2.9 — Imperative mood addresses the reader: Two spans use second-person imperatives: [action_2_sub] “split into morning and midday doses” (line 470) and [marker_6_why] “Read alongside cortisol to judge adrenal balance” (line 733).
4. 12.3 — Mechanism carried into a benefit item: [benefits_speculative] (line 560) states “neuroprotection through increased brain-derived neurotrophic factor”; 12.3 requires mechanistic explanations to be stripped, leaving “neuroprotection”.

Fixes 20/09/2026 04:44

1. 4.5 — Condensed for the page budget: Trimmed example drug lists to two entries in five Key Interactions items, shortened [marker_6_target] to “No established target; upper third of age/sex range” and [marker_9_name] to “Serum digoxin, if prescribed”, and dropped “as a decoction” from [action_1_sub]. Remaining height is driven by the eight contraindications, fifteen interactions and ten biomarkers that items 8.2, 9.2 and 14.2 require in full.
2. 1.3 / 2.5 — Hedge restored in dose splitting: [action_2_sub] changed from the imperative “split into morning and midday doses” to the descriptive “split between morning and midday”, reporting the ER’s finding instead of instructing.
3. 2.6 / 2.9 — Imperative in a biomarker rationale: [marker_6_why] changed from “Read alongside cortisol to judge adrenal balance” to “Interpreted alongside cortisol to judge adrenal balance”.
4. 12.3 — Mechanism stripped from benefit item: [benefits_speculative] changed from “neuroprotection through increased brain-derived neurotrophic factor” to “neuroprotection”.