Audit: QRS - Rose Hip for Health & Longevity
Audit conducted on 21/08/2026 04:06 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 81 |
| Failed | 0 |
| N/A | 12 |
| 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 populated span traces to ER text: protocol cells to Therapeutic Protocol, time cells to Practical Considerations “Time to effect”, benefits/risks to the ER tier headings, gates to Key Interactions & Contraindications, markers to the ER monitoring table. |
| 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. | 🟢 | Hedges preserved, e.g. marker_9_target keeps “No rose-hip-specific target exists”; marker_4_why keeps “the speculative metabolic signal”. |
| 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” remains under Contraindications, not Key Interactions; marker_1_why “may lower” matches ER “is proposed to lower”. |
| 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 only from the ER’s “Populations who should avoid Rose Hip” list; Key Interactions only from the ER interaction bullets; no Benefit- or Risk-Modifying Factor content appears in the gates. |
| 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 PMIDs, no NCT identifiers, no expert names (Winther is not carried over) and no brand names (Hyben Vital, Litozin, Rosenoids are all omitted). |
| 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. | 🟢 | Matches the ER’s measured, funding-sceptical register, e.g. at_a_glance “Almost every positive trial was manufacturer-funded” mirrors the ER Conclusion. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Actionable protocol, time-to-effect and monitoring cells give the reader a path to act on while the evidence limits stay visible. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated as findings and observed parameters, not as orders to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No prescriptive verbs directed at a reader; the contraindication and interaction lists are stated as populations and drug classes. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Cadence and qualitative items are noun phrases (“Baseline panel before starting”, “Morning joint stiffness, recorded as minutes until it eases”), not recommendations. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document body. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms retained are load-bearing (osteoarthritis, C-reactive protein, trans-tiliroside); at_a_glance uses plain equivalents such as “wear-related joint pain” and “deep abdominal fat”. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Benefit and risk items are reduced to the ER’s tier headings; explanations, magnitudes and mechanisms are stripped throughout. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed — no direct address. |
| 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. | 🟢 | Nine-marker monitoring panel with functional (not conventional-laboratory) targets addresses 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. | 🟢 | Gram-level split dosing with meals and a baseline-plus-follow-up laboratory panel assume a willing, effortful reader. |
| 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 simplified general-population framing; targets such as “hs-CRP below 1.0 mg/L, ideally below 0.5 mg/L” are optimization-grade. |
| 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 manufacturer-funding caveat and the “weaker signals” framing give the risk-aware reader the discount factor the ER applies. |
| 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 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt. | 🟢 | Uses “rescue analgesic”, “gastrointestinal upset and loose stools”, “transferrin saturation”; “loose stools” is the ER’s own clinical wording. |
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 440, 477, 519, 570, 589, 708, 539, 551, 593–595 and in the four tier <strong> labels of both the Benefits and Risks cards. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 fixed-name template spans are present, plus the repeatable marker_#_* (9 × 3) and qualitative_item_# (6) instances — 67 spans in total. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Head, CSS block, website="evidence_review", website="audit" and website="full_review" spans and the footer disclaimer are byte-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 relied 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 “Whole-fruit powder, the Danish approach”, action_2_label “Single versus split dosing” and action_3_label “Concentrated extract, the Japanese approach” reproduce the ER bold labels verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Protocol labels are verbatim; the Time-to-effect labels derive from the ER’s own enumeration in the “Time to effect” bullet (joint pain, body-fat change, skin measures). |
| 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 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. | 🟢 | Every section is condensed rather than transcribed: benefits and risks are reduced to tier headings, gate items to the key fact, monitoring “Why” cells to a single clause. |
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. | 🟢 | Lines 2–14, immediately after <!doctype html> 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 --- on line 3, closing --- on line 13; the preamble text sits on line 2. |
| 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 echoed anywhere in <body>. |
| 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, 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: rose_hip_2026-0825-2358_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-0821-0353. |
| 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. |
| 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, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: rose_hip_2026-0825-2358_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; 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: Rose Hip 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: Rose Hip for Health & Longevity. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 08/21/2026, correctly derived from qrs_creation_date: 2026-0821-0353. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: Opus 5. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | The header block (lines 415–428) contains only the template’s title and subline; the ER’s “Also known as” line 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 |
🟢 | Line 433 compresses all three Conclusion paragraphs: constituents and action, strongest signal, weaker signals, safety limit, funding caveat. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 59 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a distinct Conclusion sentence, including “Safety is unusually benign” and “loose stools at higher intakes … the practical limit”. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “osteoarthritis” is rendered as “wear-related joint pain” and “visceral fat” as “deep abdominal fat”. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year, NCT identifier or sample size appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numbers of any kind; “modest” and “weaker” are used in place of magnitudes. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All five items come from the ER’s “Populations who should avoid Rose Hip” list. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All five ER avoid-list entries are represented, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Lines 542–546: five discrete <li> elements inside the 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. | 🟢 | ER rationale clauses were correctly stripped, e.g. “on the basis of absent safety data rather than demonstrated harm” and “where vitamin C loading and oxalate handling are both impaired”. |
| 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). | 🟢 | Thresholds retained: oxalate above 40 mg/day, ferritin 300/200 ng/mL, HFE C282Y homozygotes, filtration rate below 30 mL/min/1.73 m². |
| 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 the contraindication list. |
| 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. |
N/A | The section is 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 seven items map one-to-one onto the seven ER interaction bullets. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | No overlap with the five contraindication entries. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Lines 554–560: seven discrete <li> elements. |
| 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. | 🟢 | Severity words, mechanisms and mitigations are all stripped; the em-dash clause “— blood thinners” after the vitamin K antagonist list was correctly removed. |
| 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 retained for cardiac glycosides, vitamin K antagonists, iron salts, NSAIDs and additive supplements. |
| 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 in the interaction bullets. |
| 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. |
N/A | The section is 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 derive from the ER Therapeutic Protocol bullets. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Primary dose and form (5 g/day whole-fruit powder), dosing frequency and timing (split, with meals), and the alternative preparation (100 mg/day tiliroside extract). |
| 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 supplies more than three actionable aspects; all three sets are populated. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | Lines 444–472: all nine spans carry substantive, ER-traceable content. |
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 | 🟢 | Joint pain, body fat and skin measures — the three intervals the ER’s “Time to effect” bullet names. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Order follows the ER benefit tiers: joint pain (High), body fat (Medium), skin (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 | The ER supplies three distinct time-to-effect aspects; all three sets are populated. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | Lines 483–511: “3 weeks”, “8–12 weeks” and “8 weeks” with ER-sourced 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, so the section is correctly retained. |
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, tier for tier. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated at 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. | 🟢 | Reduced to the ER headings; the ER’s Magnitude figures (SMD 0.37, NNT six, 9.26 cm², 0.105 points) are all absent. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses occur in any benefits span. |
| 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 ER benefit tiers contain items. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All seven items correspond to the seven ER risk headings, tier for tier. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated at lines 572–583. |
| 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. | 🟢 | The ER’s magnitude detail (11 events versus 2, dose-dependence, assay specifics) and the Expert Panel attribution are all omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses occur in any risks span. |
| 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 ER risk tiers contain items. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Markers, targets and rationales all trace to the ER Monitoring Protocol & Defining Success table. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All nine ER table rows are present in the same order: hs-CRP, LDL cholesterol, systolic blood pressure, fasting glucose, HbA1c, waist circumference, ferritin with transferrin saturation, 24-hour urinary oxalate, serum digoxin. |
| 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 702 reproduces the ER’s baseline / four-week / three-month / six-to-twelve-month cadence plus the two-week digoxin and INR check. |
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. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER bullets are present in the same order, with trailing commentary clauses correctly trimmed. |
Issues 21/08/2026 04:06
Pass rate 100.00%. No issues found.
Issues 21/08/2026 03:59
- 4.2 / 4.3 — Protocol labels abbreviated:
action_1_label(line 444) reads “Whole-fruit powder” andaction_3_label(line 466) reads “Concentrated extract”, but the ER’s bold labels are “Whole-fruit powder, the Danish approach:” and “Concentrated extract, the Japanese approach:” (ER lines 342 and 344). - 4.5 — Exceeds one A4 page: The sheet’s estimated rendered height is roughly 1.9 A4 pages, driven by the nine-row Monitoring table (lines 599–699, ~130 mm), the gates block (lines 537–564, ~80 mm) and multi-line
.sub,whyand cadence fields carried over from the ER at near-full length. - 11.4 — Body-fat time cell holds generic caveat:
time_2_sub(line 500) is “Nothing here works in days”, the ER’s closing general remark on ER line 399, and says nothing about the body-fat time course the “Body fat / 8–12 weeks” cell describes.
Fixes 21/08/2026 03:59
- 4.2 / 4.3 — Protocol labels restored verbatim:
action_1_labelchanged from “Whole-fruit powder” to “Whole-fruit powder, the Danish approach” andaction_3_labelfrom “Concentrated extract” to “Concentrated extract, the Japanese approach”, matching the ER’s bold labels. - 11.4 — Body-fat time cell made specific:
time_2_subchanged from the generic “Nothing here works in days” to “Deep abdominal fat, in the 12-week extract trial”, describing the cell it sits under. - 4.5 — Prose condensed for the page budget: Shortened the nine Monitoring
whycells, the marker_9 target, the cadence paragraph, the three protocolsubcells, the hemochromatosis contraindication and the “other interventions” interaction, and stripped trailing explanatory clauses from three qualitative items — all items retained, only wording tightened.