Audit: QRS - Mycoprotein for Health & Longevity
Audit conducted on 22/09/2026 07:57 using AI4L / Opus 5
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 336–338, 350), time-to-effect (ER 393), benefit/risk tier headings (ER 149–201, 223–269), contraindications (ER 307–312), interactions (ER 289–303), monitoring table (ER 423–434), cadence (ER 421), qualitative items (ER 438–443). |
| 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. | 🟢 | At-a-glance carries the ER Conclusion’s caution verbatim in substance (“Trials are small and short, with no illness or lifespan data”; ER 467). |
| 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”). | 🟢 | Contraindications retain “should avoid” force as decision gates; interactions retain “Caution” force; no directional shift found. |
| 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. | 🟢 | All stop_items come from ER “Populations who should avoid Mycoprotein” (ER 305–312); all caution_items come from the ER interaction bullets (ER 289–303). No Benefit-/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 contains no PMIDs, no NCT IDs, no expert names, and no brand names. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions present; the ER’s attribution bullet (ER 344) was correctly not carried over. |
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. | 🟢 | Neutral, declarative, evidence-first register matching the ER throughout. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Quantified targets and protocol values paired with plain-language framing. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Cells state what trials used and what markers show, not what to do. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives in any populated span; monitoring cadence is stated descriptively. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No instances of “recommend”, “advise”, “should”, or “guidance” in populated spans. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | Grep for “you/your/yours/yourself” returned zero matches. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms retained are ER heading terms carrying the fact itself; no avoidable jargon added. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Tier lines are semicolon-joined ER headings; gate items are single clauses. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | No second-person constructions 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. | 🟢 | Functional-range monitoring targets and a baseline/4-week urate check assume a proactive optimiser. |
| 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. | 🟢 | A 240 g daily substitution split across two meals plus a ten-marker panel presumes that 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. | 🟢 | Apolipoprotein B and fasting-insulin functional targets sit well outside general-population framing. |
| 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. | 🟢 | Urate risk is elevated to High tier and given a dedicated gate plus two markers, matching the ER’s weighting for 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. | 🟢 | “anti-aging” does not appear; the page 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. | 🟢 | Lede uses the ER’s own register (“digestive upset”, ER 465); no consumer-grade substitutions for clinical terms. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” | 🟢 | Diff against the template shows all fixed headings, gate headings, tier labels, and table headers byte-identical. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 fixed-name template variables present; the four repeatable names (marker_#name/target/why, qualitative_item#) are correctly expanded to 10 markers and 6 qualitative items. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Full-file diff against the template shows changes confined to variable regions; the website="evidence_review", website="audit", and website="full_review" spans, the CSS block, and the footer disclaimer are 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 ER section feeding the QRS is empty; all source sections are populated. |
| 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/2/3_label reproduce “Standard substitution protocol”, “Acute muscle-support bolus”, “Single versus split dosing” verbatim (ER 336, 338, 350); gate items reproduce the ER interaction bold labels; monitoring row names reproduce the ER biomarker column verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No invented labels; time-to-effect cell labels derive from the ER “Time to effect” bullet’s own subjects (ER 393), which carries no per-aspect bold labels. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Grep for tier emoji returned zero matches; tiers are conveyed by bold labels and card colour. |
| 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 to its minimum permitted form: tier lines are bare ER headings, gate items single clauses, and the at-a-glance is 58 words. Monitoring (10 rows) and Qualitative (6 items) are at the counts mandated by 14.2 and 15.2. |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | Lines 2–14 form a single comment 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 --- at line 3, closing --- at line 13; the descriptive text on line 2 precedes 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. | 🟢 | Contained wholly in an HTML comment; no metadata value is echoed in the header or body except the two required subline variables. |
| 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 so because it contains a colon; all other values are bare and trimmed. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: mycoprotein_2026-0922-0440_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 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-0922-0747, conforming to the 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 only; no context-window or tier qualifier appended. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9 matches the on-disk filename mycoprotein_2026-0922-0440_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: Mycoprotein for Health & Longevity - Quick Reference Sheet, matching ER frontmatter canonical_topic with & 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: Mycoprotein for Health & Longevity. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 09/22/2026, the correct reformatting of 2026-0922-0747. |
| 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 “Also known as” line (ER 32) was correctly omitted. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Leads with the action (“Replacing meat and fish with this fungal food”), then benefits, then offsets, then evidence limits — the ER Conclusion’s own three-paragraph arc (ER 463–467). |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 58 words, counted programmatically. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Cholesterol/insulin/next-meal intake and muscle from ER 463; uric acid, digestive upset, mould-linked allergy from ER 465; small/short trials and absent illness/lifespan data from ER 467. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “LDL”, “postprandial”, and “IgE” are all avoided in favour of “blood cholesterol”, “the insulin rise after a meal”, and “mould-linked allergic reactions”. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, sample sizes, or p-values appear. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numbers of any kind in the span. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All six items trace to “Populations who should avoid Mycoprotein” within that section (ER 305–312). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All six ER avoid-populations are present, none added, none dropped. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Six <li> elements inside the stop_items span (lines 567–577). |
| 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. | 🟢 | Leading “Anyone with” stripped from each; ER’s “that use egg white or milk protein as a binder” (ER 311) trimmed; no dashes introduce trailing clauses. |
| 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). | 🟢 | Gout threshold (360 µmol/L, two or more flares in 12 months) and CKD staging (eGFR below 30 mL/min/1.73 m², stage 4 or 5) both preserved; the formulation scopes (“non-vegan”, “contain wheat gluten”) 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’s contraindication bullets use 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. |
🟢 | The ER identifies six such populations 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 | 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 eight items trace to the ER interaction bullets (ER 289–303). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All eight ER interaction bullets are represented; none of them duplicates a contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Eight <li> elements inside the caution_items span (lines 585–596). |
| 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. | 🟢 | Consequence and mitigation sentences stripped from every bullet; the GLP-1 gloss “a gut hormone that signals fullness” and the “over the counter” tag removed; no dash-led trailing clauses. |
| 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). | 🟢 | All four example-drug lists preserved verbatim, and the aspirin dose window “(75–100 mg daily)” retained. |
| 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 interaction bullets use 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. |
🟢 | The ER identifies eight such 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 | 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 section (ER 336, 338, 346, 350). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | The ER’s best-documented regimen, the acute muscle bolus, and the split-dosing schedule are the three executable decisions; the remaining bullets are attribution, kinetics, and modifier discussion. |
| 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, 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. |
🟢 | Nine spans populated: labels verbatim from ER bold labels, values “240 g daily” / “70 g” / “Split across two meals”, subs carrying the substitution target, the 31.5 g protein and 2.5 g leucine figures, and the fibre/nucleotide rationale with meal timing. |
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 | 🟢 | Cholesterol, muscle adaptation, and satiety/insulin are exactly the three latencies the ER’s “Time to effect” bullet names (ER 393). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Order matches the ER’s High-tier benefit ordering: cholesterol (ER 151), muscle (ER 157), then insulin and next-meal intake (ER 163, 169). |
| 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 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. | 🟢 | Values “2–4 weeks”, “10 weeks”, “First meal” and subs (eight-week completion, lean-mass parity, single-meal chicken comparator) all trace to ER 393, 161, and 165–173. |
| 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 (ER 393), so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All eight entries correspond one-to-one with the ER Expected Benefits sub-headings (ER 149–201). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated (lines 539–557). |
| 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 sub-heading; the ER’s Magnitude lines, mechanism sentences, and evidence-basis sentences are all excluded. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any of the four benefit spans. |
| 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 tiers contain items, so no span needed hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All seven entries correspond one-to-one with the ER Potential Risks & Side Effects sub-headings (ER 223–269). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated (lines 608–622). |
| 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 sub-heading; the registry counts, percentages, and CSPI attribution in the ER body are all excluded. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any of the four risk spans. |
| 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 tiers contain items, so no span needed hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Table rows and cadence both trace to the ER Monitoring Protocol & Defining Success section (ER 419–434). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All ten ER table biomarkers present in ER order, with Optimal Functional Range and “Why Measure It?” reproduced verbatim into the Target and Why columns. |
| 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. |
🟢 | Lines 774–777 reproduce the ER’s ongoing-monitoring schedule (ER 421): urate at 4 weeks, lipids and apolipoprotein B at 8–12 weeks, then 6–12 monthly; vitamin B12 and ferritin at 6 months then annually. |
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 (ER 436–443). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers present in ER order and verbatim: gastrointestinal comfort, allergic-reaction signs, fullness/time to next hunger, joint pain, training recovery, and afternoon energy stability. |
Issues 22/09/2026 07:57
Pass rate 100.00%. No issues found.
Issues 22/09/2026 07:52
- 11.4 — Time-to-effect subs restate values: time_2_sub (line 514) and time_3_sub (lines 525–527) repeat their own label and value verbatim (“Muscle adaptation / 10 weeks / Muscle adaptations took ten weeks of training”), contributing no information.
- 12.3 — Conflicted qualifier in benefits: benefits_high (line 541) keeps “(conflicted)” after “blunted postprandial insulin and glucose response”, a redundant evidence-strength qualifier.
- 13.3 — Conflicted qualifier in risks: risks_low (line 615) keeps “(conflicted)” after “no reliable triglyceride benefit”, a redundant evidence-strength qualifier.
Fixes 22/09/2026 07:52
- 11.4 — Time-to-effect subs restate values: Replaced time_2_sub “Muscle adaptations took ten weeks of training” with “Lean mass gain matched an omnivorous diet over the training block”, and time_3_sub “Satiety and the blunted insulin response appear at the first meal” with “Both measured in single-meal trials, against an equal-energy chicken meal”.
- 12.3 / 13.3 — Conflicted qualifier stripped: Removed the redundant “(conflicted)” qualifier from benefits_high after “blunted postprandial insulin and glucose response” and from risks_low after “no reliable triglyceride benefit”.