Audit: QRS - BITC for Health & Longevity
Audit conducted on 07/09/2026 02:23 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 85 |
| Failed | 0 |
| N/A | 8 |
| Pass Rate | 100.00% |
- Total = Passed + Failed + N/A
- Pass Rate = Passed / (Passed + Failed) × 100
- N/A items are excluded from the pass rate calculation
1. General Rules
| # | Description | Result | Comments |
|---|---|---|---|
| 1.1 | Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. | 🟢 | Spot-checked every populated variable: 200 mg nasturtium / 80 mg horseradish (ER 333), 57 mg glucotropaeolin per gram (ER 335), 76.7% vs 16.7% (ER 179), ~90 days / day 3 / 84 days (ER 165, 324, 386), all seven biomarker rows (ER 418–424). |
| 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. | 🟢 | “from observation alone” and “Purified compound: never given to a person” preserve the ER’s hedging (ER 455); “No established target” carried verbatim into marker_2_target. |
| 1.3 | The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”). | 🟢 | Contraindications carried at full strength; “Pregnancy and lactation” remains an absolute stop item, not a caution. |
| 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 from the ER’s “Populations who should avoid BITC” list; interactions from the ER interaction bullets; no Benefit- or Risk-Modifying Factor was migrated into a gate. |
| 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 author names and no brand name (Angocin / Repha are not surfaced). |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attribution of any kind appears outside the fixed template header. |
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 restrained, evidence-limited register (“tested largely by its maker”, “from observation alone”). |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Quantified where the ER quantifies, plain-language where it can be; presents the food-level route as a usable option rather than dismissing the compound. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is declarative and descriptive throughout; no instruction is issued to a reader. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Cadence and gate items are stated as observations of what the trials and the licensed product’s labelling do, not as directions. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No occurrence of “recommend”, “advise”, “should” or equivalent in the QRS’s own voice. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the file; no imperative constructions. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | “dysuria” is glossed as “(pain on urination)”; the remaining technical terms (CYP2E1, eGFR, TSH) are unavoidable biomarker and drug-class names carried from the ER. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every gate item, benefit and risk is a stripped noun phrase; monitoring “Why” cells are single clauses. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by full-text scan for “you” / “your” / “we”: no matches. |
| 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. | 🟢 | The sheet assumes willingness to run baseline urinalysis, urinary iodine and thyroid panels before use. |
| 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. | 🟢 | Retains the 4-tablets-three-times-daily schedule and a seven-marker laboratory panel including a research-laboratory cyclocondensation assay. |
| 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 a mass-market “just eat more cress” framing; the evidence limits are stated bluntly. |
| 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 leads with the sponsorship limitation and the absence of any purified-compound human data — the two facts that matter most to a proactive self-experimenter. |
| 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. | 🟢 | “Longevity” appears only in the title, carried from the ER canonical_topic; “anti-aging” does not appear. |
| 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. | 🟢 | “film-coated tablet”, “mucosal irritation”, “hypersensitivity reactions”, “urothelial carcinoma” — no consumer-grade substitutions. |
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 verified verbatim at lines 446, 492, 542, 570, 591, 617, 642, 646–648, 744; tier labels intact at 545/549/555/559 and 620/623/627/632. |
| 3.2 | All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 template variable names present; the repeatable marker_#* and qualitative_item# spans are instantiated as marker_1–7 and qualitative_item_1–6 (61 spans total). |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Structural diff against the template shows changes confined to variable content, frontmatter values and instantiated repeatable rows; CSS, markup, website= spans and footer disclaimer are byte-identical. |
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; the High benefit and High risk tiers carry explanatory prose in the ER and are governed by items 12.5 / 13.5 instead. |
| 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. | 🟢 | “Licensed fixed-combination approach”, “Whole-food approach” and “Single versus split dosing” are the ER’s bold labels verbatim (ER 333, 335, 345). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Protocol labels verbatim; monitoring row labels match the ER biomarker table names; time-to-effect labels name the ER’s own outcome headings, which the ER supplies no bold label for. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Full-text scan for emoji code points returns no matches; 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 against the ER: 11 interaction bullets reduced to single noun phrases with trimmed drug lists, 7 contraindications stripped of trailing rationale, biomarker “Why” cells cut to one clause each, cadence reduced to two sentences. |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | Comment opens at line 2 immediately after the doctype at line 1 and closes at line 14, ahead of every other comment and all head 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 “—” at line 3, closing “—” at line 13; the preceding “QRS — Metadata (invisible, parsed by audit tooling)” text sits before the opener as permitted. |
| 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 entirely in an HTML comment; none of its values are repeated in the body except header_subline_date/model, which are their own template 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:04" is quoted, and it contains a colon requiring YAML quoting; all other values unquoted and untrimmed of nothing. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: bitc_2026-0907-0010_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-0907-0155, 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” — single word, no version, no qualifier. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | Line 8: qrs_creator_ai_fullname: Opus 5. |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | “Opus 5” — nickname plus version only, no context-window or tier qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: bitc_2026-0907-0010_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; the added git_user and git_issue values are bare and unquoted as required. |
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: “BITC for Health & Longevity - Quick Reference Sheet”; matches ER canonical_topic with the ampersand entity-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: “BITC for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “09/07/2026”, correctly derived from qrs_creation_date 2026-0907-0155. |
| 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 was correctly not carried across. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Tracks the Conclusion’s structure exactly: single reactive property → dual effect → what the human evidence actually is → what has never been tested (ER 453–457). |
| 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. | 🟢 | “reactive plant defense chemical” (ER 453); “cress and nasturtium” (ER 37); “appetite for sulfur groups” / “irritates the surfaces it touches” (ER 453); “tested largely by its maker” (ER 455); “slower spread” from observation (ER 455); “never given to a person” (ER 455). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “isothiocyanate”, “glucotropaeolin”, “urothelial” and “non–muscle-invasive” are all kept out of this section in favour of “sulfur groups”, “bladder”, “airway”. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, author, year or sample size appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No hazard ratios, percentages or confidence intervals; “fewer” and “slower” carry the direction without numbers. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All seven items trace to the “Populations who should avoid BITC” list at ER 303–311. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | Complete 7-of-7 coverage with no additions. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Seven <li> elements inside the stop_items span, lines 573–586. |
| 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. | 🟢 | Trailing rationale correctly stripped: “in whom the licensed preparation is not authorized”, “where no safety data exist for any isothiocyanate preparation” and “given the unresolved rodent bladder findings” all removed; no dashes remain. |
| 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). | 🟢 | “(urinary iodine below 100 µg/L)” preserved; the eGFR threshold “below 30 mL/min/1.73 m²”, the age cut-off “under 6 years” and the staging qualifier “under surveillance without urologist involvement” 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’s contraindication list uses 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 names seven 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. <!– empty: ER names no population that should avoid the intervention –> | 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 eleven items map one-to-one onto the ER interaction bullets at ER 281–301. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Complete 11-of-11 coverage; none duplicates a stop item — “Iodine, kelp and thyroid hormone replacement” is the interaction bullet, distinct from the iodine-deficiency contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Eleven <li> elements inside the caution_items span, lines 594–607. |
| 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. | 🟢 | Every “Caution.”/”Monitor.” verdict and its mechanistic sentence stripped; the Conrad et al. citation on the antibiotics bullet (ER 301) correctly dropped. |
| 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 seven ER parenthetical drug lists retained and trimmed, never dropped: CYP2E1, CYP2A6, antiplatelet, OTC irritant, antacid, isothiocyanate-supplement and urinary-antibacterial lists each keep representative examples. |
| 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 parentheticals are plain comma-separated drug lists with no ranking notation. |
| 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 names eleven interactions, and the section is correctly populated. |
| 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. <!– empty: ER names no interaction that changes how the intervention is used –> | 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 action sets trace to the ER “Therapeutic Protocol” section (ER 331–355). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Licensed dose, whole-food alternative and split-dosing schedule are the three bullets that can actually be acted on; the remaining bullets are framing, pharmacokinetics or 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 well over 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. |
🟢 | All nine variables populated; values “4 tablets, 3× daily”, “Cress, nasturtium or papaya seed” and “Split, without exception in the human record” all trace to ER 333, 335 and 345. |
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 | 🟢 | Recurrent UTI, respiratory tract infection and parasite clearance are the only three outcomes in the ER with a stated time course (ER 165, 179, 324, 386). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered UTI → RTI → parasites, matching the ER’s Medium → Medium → Low benefit tiering; bladder-cancer progression is correctly omitted since the ER gives it no time course. |
| 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, so all three sets are used. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine variables populated; time_1_sub is verbatim from ER 386 and time_3_sub from ER 179. |
| 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 |
🟢 | Tier membership matches the ER’s Medium / Low / Speculative headings exactly (ER 155–197). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present at lines 544, 547, 554, 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. | 🟢 | All Magnitude figures, sponsorship caveats and mechanistic paragraphs dropped; each item is a bare outcome phrase. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses in any benefit item; the “(disease confined to the lining)” gloss from ER 169 correctly dropped. |
| 12.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | The ER has no High-tier benefit (ER 151); benefits_high carries style="display: none" at line 544 with no empty-state text. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Tier membership matches the ER’s Medium / Low / Speculative headings exactly (ER 227–263). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present at lines 619, 622, 625, 630. |
| 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 1.5%-vs-6.8% adverse-event figures (ER 231) and all mechanistic prose stripped; each item is a bare risk phrase. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses in any risk item; the “(thyroid enlargement)” gloss from ER 243 correctly dropped. |
| 13.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | The ER has no High-tier risk (ER 223); risks_high carries style="display: none" at line 619 with no empty-state text. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | All rows trace to the biomarker table in “Monitoring Protocol & Defining Success” (ER 416–424). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | 7 of 7 carried in ER order: urinalysis with microscopy, urinary total isothiocyanates, TSH, free T4, urinary iodine, creatinine/eGFR, ALT/AST. |
| 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 736: “Baseline, 4 weeks, 12 weeks, then every 6 to 12 months on repeated prophylaxis courses. Acute short courses need no interval testing.” — condensed from ER 414. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All six items trace to the qualitative-marker list at ER 428–433. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | 6 of 6 carried in ER order: gastric comfort, mucosal burning, urinary symptoms, respiratory-infection frequency, rash/itch/wheeze, energy and cold intolerance. |
Issues 07/09/2026 02:23
Pass rate 100.00%. No issues found.
Issues 07/09/2026 02:15
- 1.1 / 7.3 — At-a-glance misattributes human evidence: [at_a_glance] (lines 434–438) states that all the human evidence, including “slower spread of treated bladder cancer”, “comes from one licensed herbal product tested largely by its maker”; the ER Conclusion (line 455) sources that finding to blood and urine measurements in people “who were observed rather than assigned”, not to the licensed preparation.
- 1.3 — Split-dosing claim strengthened: [action_3_value] (line 481) reads “Split, without exception”, dropping the ER’s qualifier “in the human record” (ER line 345) and turning a statement about the evidence base into an absolute rule.
Fixes 07/09/2026 02:15
- 1.1 / 7.3 — At-a-glance evidence attribution corrected: Rewrote [at_a_glance] so the licensed herbal product is credited only with the infection findings, and the bladder-cancer progression signal is attributed to observation, changing “Human evidence — fewer repeat bladder and airway infections, slower spread of treated bladder cancer — comes from one licensed herbal product tested largely by its maker” to “Fewer repeat bladder and airway infections come from one licensed herbal product tested largely by its maker; slower spread of treated bladder cancer, from observation alone.”
- 1.3 — Split-dosing qualifier restored: Changed [action_3_value] from “Split, without exception” to “Split, without exception in the human record”, matching the ER wording.
Issues 07/09/2026 02:09
- 4.5 — Exceeds the one A4 page budget: Uncondensed ER prose is carried into the three densest blocks — the seven Monitoring
Whycells keep full ER sentences (e.g.marker_6_why, line 735), all sixqualitative_item_#entries keep their ER trailing clauses (lines 773-807), and all elevencaution_itemscarry four-drug parenthetical lists (lines 593-611) — pushing the estimated rendered height to roughly 1.4-1.8 A4 pages.
Fixes 07/09/2026 02:09
- 4.5 — Monitoring table condensed: Shortened the
Whycells for markers 2, 5, 6 and 7 and theTargetcell for marker 7 (e.g.marker_6_whyfrom “The licensed preparation is contraindicated in acute kidney inflammation and below 30 mL/min/1.73 m²” to “Contraindicated below 30 mL/min/1.73 m²”), removing roughly one wrapped line per row across all seven rows. - 4.5 — Qualitative items trimmed: Stripped the ER explanatory trailing clauses from
qualitative_item_2,_3,_5and_6(e.g. “Skin rash, itching or wheeze, as the earliest signal of sensitization” to “Skin rash, itching or wheeze”), keeping all six items but reducing each to a single line. - 4.5 — Key Interactions parentheticals trimmed: Reduced the example-drug lists in the
caution_itemsgate from four drugs to two or three per item (e.g. “CYP2E1 substrates (acetaminophen, chlorzoxazone, isoflurane, ethanol)” to “CYP2E1 substrates (acetaminophen, ethanol)”), retaining all eleven items and every parenthetical. - 4.5 — Protocol and cadence tightened: Shortened
action_2_sub,action_3_subandmonitoring_cadence(cadence from “Baseline, then repeat at 4 weeks, again at 12 weeks, and thereafter every 6 to 12 months for anyone on repeated prophylaxis courses” to “Baseline, 4 weeks, 12 weeks, then every 6 to 12 months on repeated prophylaxis courses”).
Issues 07/09/2026 02:01
- 11.2 — Time-to-effect order ignores benefit tier: The Time to Effect cells are ordered by ascending duration rather than by benefit magnitude — Clearance of Intestinal Parasites (a Low-tier benefit) sits at
time_1(line 498) ahead of Respiratory Tract Infection and Recurrent Urinary Tract Infection, both Medium-tier.
Fixes 07/09/2026 02:01
- 11.2 — Time-to-effect reordered by benefit tier: Reordered the three Time to Effect cells from ascending-duration order to benefit magnitude —
time_1is now Recurrent Urinary Tract Infection (Medium),time_2Respiratory Tract Infection (Medium), andtime_3Clearance of Intestinal Parasites (Low), matching the ER’s benefit tiering and within-tier order.