Audit: QRS - Astragalus for Health & Longevity

Audit conducted on 14/08/2026 10:48 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.	🟢	All protocol doses (9–30 g, 250 units, 1000-unit arm, 5–10 mg astragaloside IV), time-to-effect windows, benefit/risk tiers, contraindications, interactions, biomarker targets and qualitative markers trace to ER lines 369–387, 426, 159–221, 245–293, 313–345, 456–473.
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 promotion of pre-malignant cells” retains the ER’s hedge (ER line 273); speculative tiers carry the ER’s speculative framing.
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	“Pregnancy and lactation, at any stage” remains a contraindication, not a caution; “on weak studies” preserves the ER’s quality caveat.
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 map to the ER “Populations who should avoid Astragalus” list; Key Interactions map to the ER interaction bullets; no Benefit- or Risk-Modifying Factor is repurposed.
1.5	PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact.	🟢	No PMIDs, NCT numbers, author names or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind are present.

2. Focus, Tone & Audience

#	Description	Result	Comments
2.1	The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing.	🟢	Measured, evidence-first register matching the ER Conclusion; the “two products wearing one name” framing is the ER’s own.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Quantified targets and dosing sit alongside plain-language framing without hype.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Content is stated as what the evidence shows and what the protocols are, not as instruction to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Monitoring cadence and gates are presented as the ER’s documented protocol; footer disclaimer reinforces the framing.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “should”, “recommended”, or “advised” phrasing in the QRS’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns appear anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are confined to the Monitoring table, where biomarker names are load-bearing; elsewhere plain terms are used.
2.8	Information is presented in a concise and very compact manner	🟢	Gate and tier items are reduced to bare facts; interaction items are drug class plus example drugs only.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” anywhere in the file.
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.	🟢	Telomere biomarker tracking, competing whole-root vs. concentrated-activator protocols and interaction gates address exactly this audience.
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-daily blood pressure logging for four weeks, annual telomere assays and a decoction protocol assume high willingness.
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 toward casual use; optimal functional ranges are used rather than conventional lab cut-offs.
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 foregrounds the biomarker-without-function gap, the exact trade-off this audience faces.
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 appear; the QRS uses “longevity interventions” and “age-related decline”.
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.	🟢	“Gastrointestinal upset”, “hypersensitivity”, “injectable preparations”, “immunostimulant” used throughout; the plain-language wording in At-A-Glance is mandated by item 7.4.

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 present verbatim at lines 446, 492, 538, 609, 637, 760, 571, 585, 641–643, and in both tier lists.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	63 uniquely named variable spans present with no duplicates, covering header (4), at_a_glance, action 1–3, time 1–3, benefits (4), gates (2), risks (4), marker 1–8, monitoring_cadence and qualitative_item 1–5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The non-variable template spans website="evidence_review", website="audit" and website="full_review" (lines 423, 426, 440) are retained untouched.

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 drawn on by the QRS is empty.
4.2	Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label.	🟢	action_1_label “Classical whole-root decoction”, action_2_label “Concentrated telomerase activator” and action_3_label “Best time of day” match the ER Therapeutic Protocol bold labels verbatim (ER lines 369, 375, 379).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Benefit and risk items reuse the ER heading wording; all eight marker names are verbatim from the ER biomarker table; time labels reuse the ER’s own phrases from ER line 426.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters occur in the file; the ER’s “⚠️ Conflicted” marker was correctly dropped.
4.5	The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page.	🟢	Every section is condensed relative to the ER: interaction bullets stripped to class plus examples, contraindications stripped of rationale, benefits and risks stripped of magnitudes and mechanism, cadence reduced to one sentence chain.

---

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.	🟢	Single comment at lines 2–14, immediately after the doctype on line 1.
5.2	Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML.	🟢	Opening “—” 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; none of its values are echoed by a visible element.
5.4	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Only duration: "00:02" is quoted, correctly, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: astragalus_2026-0814-0926_Opus_ER.md.
5.6	Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]”	🟢	Line 5: qrs_prompt_version: 26.7.02, matching the QRS.md version badge.
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	Line 6: qrs_creation_date: 2026-0814-1026, correct format.
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” 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]”	🟢	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” is nickname plus version with no trailing qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual filename astragalus_2026-0814-0926_Opus_QRS.html.
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; no stray whitespace or unnecessary 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 &)	🟢	Line 22: “Astragalus 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: “Astragalus for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “08/14/2026”, the correct reformat of 2026-0814-1026.
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.	🟢	Header holds only the title and the template subline; the ER’s long “Also known as” list was correctly 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	🟢	Distils all three ER Conclusion paragraphs: the two-product split, the whole-root outcomes, the biomarker-without-function gap, and the one-year safety horizon.
7.2	[at_a_glance] is no longer than 60 words	🟢	54 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	“Two products wearing one name” (ER 495), root outcomes and study-quality caveat (ER 495), telomere gain without function (ER 497), one-year safety and missing long-term follow-up (ER 499).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“Protective caps on chromosomes” replaces telomeres; “better heart pumping” replaces ejection fraction; no acronyms appear.
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 effect sizes, confidence intervals or risk ratios; “One-year” denotes follow-up duration, not a statistic.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items map one-to-one onto the ER “Populations who should avoid Astragalus” list (ER lines 339–345).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoid-populations are represented, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <li> elements inside the [stop_items] span, lines 574–580.
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 or trailing clauses; “Solid-organ” and “Known” prefixes trimmed, rationale omitted.
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).	🟢	“within 12 months”, “at any time”, “(lupus, multiple sclerosis)”, “at any stage”, “below 100 mmHg”, “(eGFR below 30)” and “Fabaceae” 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 inside parentheses in this section.
8.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision.	🟢	The ER identifies seven such populations and the section is correspondingly populated, not 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	The section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All twelve items map one-to-one onto the twelve ER interaction bullets (ER lines 313–335).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Twelve interactions carried; none duplicates a contraindication entry.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Twelve <li> elements inside the [caution_items] span, lines 588–599.
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 is drug class plus examples only; the ER’s Caution/Monitor labels, consequences and mitigations are all 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 one of the twelve items retains a shortened example-drug parenthetical; “narrow margins” is preserved as “Narrow-margin”.
9.6	When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol.	N/A	The ER uses no ranking notation inside parentheses in this section.
9.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used.	🟢	The ER identifies twelve interactions and the section is correspondingly populated, not 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	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 369–381.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The two competing dosing approaches (whole root, concentrated activator) plus timing, which are the ER’s central implementation axes.
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 names twelve implementation aspects, well above three.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All nine spans carry substantive ER-derived content; the granule dose and isolated astragaloside IV range are folded into the sub-lines rather than dropped.

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	🟢	Kidney slope separation, telomere change and fatigue/immune shifts — the three windows named in ER line 426.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Kidney decline and telomere lengthening are the ER’s two High-tier benefits and lead; fatigue and immune shifts are Medium-tier and follow.
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 names 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 spans populated: “Most of 48 weeks”, “1 to 6 months”, “4 to 12 weeks” with ER-derived sub-lines.
11.5	If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel	N/A	The ER provides time-to-effect information at line 426.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All ten items correspond to the ten ER benefit headings across the four tiers.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present at lines 540, 546, 553, 559.
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.	🟢	Benefit names only; no eGFR slopes, standardized mean differences or confidence intervals carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefit item; the ER’s “⚠️ Conflicted” marker on immune modulation is 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	All four tiers carry items in the ER, so none needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All eight items correspond to the eight ER risk headings across the four tiers.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 611, 614, 620, 626.
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.	🟢	“Herb–drug interactions” drops the ER’s “via Metabolizing Enzymes and Transporters”; the 12.4% incidence figure and pharmacovigilance percentages are omitted.
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 item.
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four tiers carry items in the ER, so none needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Drawn from the ER “Monitoring Protocol & Defining Success” biomarker table at lines 456–465.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All eight are present: seated systolic blood pressure, eGFR, urine albumin-to-creatinine ratio, hs-CRP, ALT, fasting glucose, leukocyte telomere length, CD4/CD8 ratio, with targets and rationales matching the ER.
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 751: baseline panel, blood pressure twice daily for four weeks then weekly, bloodwork at 12 weeks then six-monthly, telomere length annually at most — matching ER lines 452–454.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Drawn from the ER qualitative-marker list at lines 469–473.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five are present and carried verbatim: daytime energy and exercise recovery, upper respiratory infection frequency, dizziness on standing, digestive comfort, sleep quality and cognitive clarity.

Issues 14/08/2026 10:48

Pass rate 100.00%. No issues found.

Issues 14/08/2026 10:41

1. 9.5 — Truncated supplement example: The Key Interactions item at line 597 renders the ER’s “beetroot nitrate” (ER line 331) as bare “nitrate”, which names nitrate vasodilator drugs rather than the dietary supplement the ER cites.
2. 1.3 — Hypotension threshold strengthened: The contraindication at line 578 drops “persistently” from the ER’s “seated systolic pressure persistently below 100 mmHg” (ER line 343), broadening a persistent-threshold criterion into a single-reading one.

Fixes 14/08/2026 10:41

1. 9.5 — Restored supplement example: Key Interactions item changed from “Blood-pressure-lowering supplements (nitrate, magnesium)” to “(beetroot nitrate, magnesium)”, matching the ER’s named example.
2. 1.3 — Hypotension threshold qualifier restored: Contraindication changed from “systolic below 100 mmHg” to “systolic persistently below 100 mmHg”, matching the ER’s persistent-threshold criterion.

Issues 14/08/2026 10:33

1. 4.5 — Sheet overruns the one-page budget: Rendered content is roughly twice the A4 budget; the decision-gate columns alone (19 items carrying the ER’s full example lists, lines 573-605) plus the eight-row monitoring table with a three-line cadence (lines 653-762) exceed a full page, and the protocol subs (lines 456-488) and 59-word [at_a_glance] (lines 433-439) were not condensed to a per-section budget.

Fixes 14/08/2026 10:33

1. 4.5 — At-A-Glance condensed: Trimmed [at_a_glance] from 59 to 54 words (“though study quality is weak” → “on weak studies”, “Safety across one year is unremarkable” → “One-year safety is unremarkable”), cutting one rendered line.
2. 4.5 — Protocol subs shortened: Rewrote all three [action_#_sub] texts to two rendered lines each instead of four, keeping every ER fact (angelica pairing, 15 g granule equivalent, 1000-unit arm, 5–10 mg astragaloside IV, once-daily dosing).
3. 4.5 — Contraindication items trimmed: Shortened all seven [stop_items] to single lines, retaining every threshold and time window (12 months, at any time, below 100 mmHg, eGFR below 30) and dropping only redundant wording.
4. 4.5 — Interaction items trimmed: Reduced each of the twelve [caution_items] to one rendered line by cutting the parenthetical drug lists to two named examples apiece, as permitted for the one-page budget.
5. 4.5 — Monitoring cells compacted: Shortened [marker_7_target] and [monitoring_cadence], removing three rendered lines from the Monitoring card without dropping any biomarker or cadence step.
6. 4.5 — Risks low tier compacted: Reduced “Herb–drug interactions via metabolizing enzymes and transporters” to “Herb–drug interactions”, which also removes mechanistic detail that section 13.3 asks to be stripped.