Audit: QRS - Cordyceps for Health & Longevity
Audit conducted on 12/09/2026 02:19 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 84 |
| Failed | 0 |
| N/A | 9 |
| 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 cells vs ER Therapeutic Protocol (1,000-3,000 mg, 3-6 g disease dosing, 333 mg three times daily, cordycepin 0.3-1.0%), benefit/risk tiers vs the ER headings, all nine monitoring rows vs the ER biomarker table. No unsupported claim. |
| 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 carried over: “No established target” (marker_8/9_target), “theoretical antiplatelet effects” (marker_5_why), “one narrow measure, not a general cognitive effect” (time_3_sub), “Neither form is the default” (action_2_sub). |
| 1.3 | The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”). | 🟢 | No claim strengthened or softened. The conditional in the ER’s last contraindication is kept (“if using wild material”), and “outside specialist supervision” is kept on the immunosuppressant gate rather than made unconditional. |
| 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. | 🟢 | Gate items come only from the ER Key Interactions & Contraindications section; benefits from Expected Benefits; risks from Potential Risks & Side Effects. No Benefit- or Risk-Modifying Factor is surfaced as a gate or side effect. |
| 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. | 🟢 | Only brand names Cs-4, Bailing, Jinshuibao appear (action_2_sub), all present in the ER for the same fact. No PMIDs, no NCT identifiers, no expert names, no study citations. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attribution of any kind is introduced. |
2. Focus, Tone & Audience
| # | Description | Result | Comments |
|---|---|---|---|
| 2.1 | The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing. | 🟢 | Matches the ER’s sober, conflict-flagging register (industry funding, wide adulteration, absent placebo arms). |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert and data-driven (thresholds, ranges, timeframes) while remaining readable; framing stays neutral rather than promotional. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents evidence and ranges; no prescriptive instruction to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No clinical advice phrasing; the fixed “Contraindications” / “Key Interactions” headings are template-owned and the items are stated as facts. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “recommend”, “advise”, “advised”, “guidance” or “should” anywhere in the document (verified by search). |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns (“you”, “your”) anywhere in the document (verified by search). |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language throughout; “chronic obstructive pulmonary disease” is written out in benefits_high rather than abbreviated. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every span is a single clause or short phrase; gate items and qualitative items are one line each. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | No direct address; marker targets use “own baseline” rather than “your baseline”. |
| 2.10 | The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review. | 🟢 | Content is pitched at proactive self-optimisers: functional ranges tighter than lab reference ranges, sourcing and assay detail, arsenic exposure tracking. |
| 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. | 🟢 | Assumes willingness to run a metabolic-cart or standardised field test, split dosing, and repeat blood panels. |
| 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. | 🟢 | Not general-population framing: it assumes baseline testing, certificate-of-analysis literacy and threshold tracking. |
| 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 healthy-population signal is separated from the disease-population signal in at_a_glance and in the Protocol subs, which is the distinction that matters to this audience. |
| 2.14 | The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. | 🟢 | “anti-aging”/”anti-ageing” appear nowhere in the document (verified by search). |
| 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. | 🟢 | Formal register throughout (“gastrointestinal discomfort”, “hypersensitivity reaction”, “antithrombotic drugs”); no “pill”, “shot” or “by mouth”. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” | 🟢 | All fixed strings intact: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, the four tier labels, and “Marker” / “Target” / “Why”. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template span names are present; marker_#* and qualitative_item# are expanded to nine and seven instances respectively (68 spans total, none missing). |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Diff against the template with text nodes stripped shows no structural edit: CSS, comments and the three website=”…” spans are untouched. risks_high / risks_medium are the only altered non-content spans and they are governed by item 13.5. |
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 is empty: every ER section the QRS draws on has content, and the two empty risk tiers are handled under item 13.5 (display:none), which explicitly forbids 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. | 🟢 | action_1label “Standard dose” and action_3_label “Split versus single dose” are the ER’s bold labels verbatim; all nine marker#_name row labels are the ER biomarker-table entries verbatim (eGFR, Serum creatinine, Haemoglobin and haematocrit, Ferritin, White cell and platelet count, ALT, Fasting glucose and HbA1c, Urinary total arsenic, Ventilatory threshold or time to exhaustion). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No invented label. action_2_label “Form” is the shared verbatim stem of the ER’s two “Form - …” bullets, which the cell merges under the one-page budget. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No tier emoji anywhere: searches for the three indicators return nothing; tiering is carried by labels and CSS. |
| 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 at its condensed minimum: gate items one clause each, benefit tiers collapsed to semicolon lists, monitoring “Why” cells reduced to a single phrase, lede at 59 words. No section carries ER prose that could be cut without losing content other items mandate. |
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: the metadata comment is the first element after <!doctype html> and precedes all other comment, head and body content. |
| 5.2 | Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML. | 🟢 | Opening “—” on line 3, closing “—” on line 13; the “QRS - Metadata” text on line 2 precedes the block and is not parsed. |
| 5.3 | The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. | 🟢 | The block sits inside an HTML comment and is not echoed by any element on the sheet. |
| 5.4 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | All values trimmed; the only quoted value is duration: “00:05”, which contains a colon and therefore requires YAML quoting. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: cordyceps_2026-0912-0008_Opus_ER.md (line 4). |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | qrs_prompt_version: 26.9.11 (line 5), matching the version badge of QRS.md. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | qrs_creation_date: 2026-0912-0206 (line 6), in YYYY-MMDD-HHMM form. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | qrs_creator_ai_nickname: Opus (line 7). |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | “Opus” is a single word with no version or qualifier. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | qrs_creator_ai_fullname: Opus 5 (line 8). |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | “Opus 5” is nickname plus version number with no additional qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: cordyceps_2026-0912-0008_Opus_QRS.html (line 9), 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: no stray whitespace and no unnecessary quoting in any value. |
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 &) |
🟢 | |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | header_topic is “Cordyceps for Health & Longevity” (line 417), the ER canonical_topic with & encoded. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | header_subline_date is 09/12/2026, i.e. qrs_creation_date 2026-0912-0206 in MM/DD/YYYY form. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | header_subline_model is “Opus 5”, equal to qrs_creator_ai_fullname. |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | The header carries only the title and the template’s created-on subline; no badge, version stamp, alternate-names line, audit date or variant marker. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses the ER Conclusion: the not-one-product framing, the adjunctive disease benefits, the healthy-population threshold shift, and the adulteration problem. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 59 words (counted programmatically), within the 60-word limit. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a distinct Conclusion passage: “Cordyceps is not one product”; “The wild caterpillar fungus, the powders grown in fermentation tanks … differ in chemistry and in the evidence”; “Cultivated preparations, added to conventional treatment, appear to help kidney function … ease breathing … reduce the side effects of cancer treatment”; “a modest rise in the workload that can be sustained before breathing becomes laboured - larger in untrained and older people, absent in trained cyclists”; “the market is full of products that contain little or no cordyceps”. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms and no specialist classifications; “adjunct” is rendered as “add-on” and the threshold concept as “workload held before breathing becomes laboured”. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year, sample size or p-value. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect size, risk ratio or statistical result. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All nine items trace to the ER’s “Populations who should avoid Cordyceps” list plus the immunosuppressant bullet’s absolute-contraindication clause, both inside Key Interactions & Contraindications. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | Complete: transplant recipients, immunosuppressants outside specialist supervision, active autoimmune disease, haematological malignancy/myeloproliferative disease, pre-surgical window, pregnancy and breastfeeding, under-18s, mould or mushroom allergy, severe CKD on wild material. Nothing from the ER list is missing. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Nine <li> elements inside the stop_items span (counted programmatically). |
| 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. | 🟢 | All post-em-dash clauses stripped: “- systemic lupus erythematosus, rheumatoid arthritis, multiple sclerosis”, “- no human safety data of any kind exist”, “- no controlled paediatric data”, and “because of arsenic retention”. |
| 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). | 🟢 | Qualifiers preserved: “maintenance immunosuppression”, “outside specialist supervision”, “haematocrit above 52% (men) or 48% (women)”, “Within 14 days of planned surgery”, “eGFR below 30 mL/min/1.73 m2”, “if using wild material”. |
| 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, so there is nothing to normalise. |
| 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, which is correct: the ER names eight avoid-populations plus one specialist-supervision-only scenario. |
| 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 left empty, so no empty-basis HTML comment is required. |
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 bulleted interaction list in the ER Key Interactions & Contraindications section. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All nine ER interaction bullets are represented except the immunosuppressant bullet, which is correctly carried in Contraindications instead and therefore excluded here. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Eight <li> elements inside the caution_items span (counted programmatically). |
| 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. | 🟢 | No mechanism, consequence or mitigation text is carried over; the ER’s “Other interventions -“ stem is dropped in favour of the substantive item. |
| 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). | 🟢 | Example drug lists preserved on every item that has one: (warfarin, apixaban, clopidogrel, aspirin), (ibuprofen, naproxen), (fish oil, ginkgo, garlic extract, high-dose vitamin E, nattokinase), (metformin, sulfonylureas, SGLT2 inhibitors), (berberine, chromium, bitter melon, Gymnema sylvestre), (reishi, maitake, turkey tail, Astragalus). |
| 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, so there is nothing to normalise. |
| 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, which is correct: the ER names nine interactions that change how the intervention is used. |
| 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 left empty, so no empty-basis HTML comment is required. |
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 section. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose, preparation form and dose splitting/timing are the three decision-relevant levers in the ER protocol; the remaining bullets are pharmacokinetic or modifier detail. |
| 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 protocol names well over three distinct actionable aspects, so no set had to be left empty. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine action spans carry ER-derived content (1,000-3,000 mg with the 3-6 g disease range; the two standardisation markers plus “Neither form is the default”; split dosing with the 333 mg three-times-daily trial and the evening-meal placement). |
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 | 🟢 | Aerobic capacity at 12 weeks, recovery/iron status at 4-16 weeks and post-exercise reaction time at 30 minutes are the three time-anchored effects in the ER. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered High tier (aerobic capacity) then the two Medium-tier effects in the ER’s own order (recovery and iron status, then post-exercise reaction time). |
| 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 at least three distinct time-to-effect aspects, so no set had to be left empty. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time spans carry ER-derived content, including the ER’s own “ferritin at 4 and 8 weeks … creatine kinase at 16 weeks, in runners under heavy training load” and the 1 g dose 30 minutes before exhaustive cycling. |
| 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 does provide 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 four tiers derive from the ER Expected Benefits headings. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four benefit spans are present and populated. |
| 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. | 🟢 | Items are the bare benefit names; no effect sizes, magnitudes, trial counts or mechanisms carried over. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | The ER’s ⚠️ Conflicted markers and all magnitude figures are dropped; no parenthetical content survives. |
| 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 benefit tiers have items in the ER, so no span needed display:none. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Both populated tiers derive from the ER Potential Risks & Side Effects headings. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four risk spans are present. |
| 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. | 🟢 | risks_low is the bare “Gastrointestinal discomfort”; the seven speculative items are bare names with no severity grades, mechanisms or trial detail. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content preserved; the ER’s ⚠️ Conflicted marker on the arsenic item and the “Not quantified in available studies” magnitude note are both dropped. |
| 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. | 🟢 | The ER states “No risk reaches High” and “No risk reaches Medium either”, and both spans are set to style=”display: none” rather than filled with empty-state phrasing. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | All rows derive from the biomarker table in the ER Monitoring Protocol & Defining Success section. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All nine ER biomarkers are listed in ER order, with the functional ranges carried across (eGFR, serum creatinine, haemoglobin/haematocrit, ferritin, white cell and platelet count, ALT, fasting glucose and HbA1c, urinary total arsenic, ventilatory threshold or time to exhaustion). |
| 14.3 | [monitoring_cadence] is populated with the monitoring cadence/frequency derived from the ER Monitoring section. It is not left with placeholder text or empty. |
🟢 | monitoring_cadence reproduces the ER cadence: “Full blood count and kidney panel at 8-12 weeks, then every 6-12 months for continuous use; functional test again at 12 weeks”. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All seven items derive from the qualitative-marker list in the ER Monitoring Protocol & Defining Success section. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All seven ER qualitative markers are listed in ER order: perceived exertion, recovery time and soreness, breathlessness on a fixed climb, daytime energy, sleep onset and night waking, upper respiratory infections, gastrointestinal comfort. |
Issues 12/09/2026 02:19
Pass rate 100.00%. No issues found.