Audit: QRS - Guduchi for Health & Longevity
Audit conducted on 16/08/2026 16:46 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. | 🟢 | All content traces to the ER: protocol cells to ER lines 349/359/363, time cells to ER line 406 and 441, gates to ER lines 301–325, benefits to ER lines 155–217, risks to ER lines 237–283, monitoring to ER lines 432–444, qualitative to ER lines 448–453. |
| 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. | 🟢 | ER “No trial has tested once-daily administration” is carried as “once-daily administration of the standardised extract is untested”; “A course shorter than 8 weeks tests nothing” is verbatim. |
| 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 absolute framing; “modest blood-sugar lowering” and “small studies of uneven quality” preserve the ER’s hedging. |
| 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 Guduchi”; interactions only from the ER’s interaction bullets; no modifying-factor content is repositioned. |
| 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 identifiers, no author names and no brand names. |
| 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. | 🟢 | Neutral, evidence-weighted register matching the ER, including its explicit benefit-versus-liver-risk framing. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Tiered benefits and risks plus concrete markers and cadence give the reader actionable footing without hype. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated descriptively (“Every positive controlled trial used divided doses”), not as instruction to an individual. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives directed at a reader; the monitoring cadence is reported as the ER reports it. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No occurrence of “recommend”, “advise”, “should” directed at the reader. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are confined to the biomarker table where they are the marker names; explanatory glosses such as “cholestatic (bile-flow)” are retained. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every list item is a stripped-down phrase; mechanisms, effect sizes and citations from the ER are dropped. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by full-text scan for “you”/”your”; 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. | 🟢 | Content assumes a reader running baseline and follow-up laboratory panels and authenticating product species. |
| 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. | 🟢 | Repeat liver panels, ANA/IgG testing and a three-times-daily divided regimen are presented without softening. |
| 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. | 🟢 | The sheet assumes access to laboratory testing and interpretation of functional reference ranges. |
| 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 at-a-glance sets modest, condition-specific benefit against uncommon but severe hepatic harm, the decision this audience faces. |
| 2.14 | The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. | 🟢 | No occurrence of “anti-aging” in any form; 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. | 🟢 | Clinical register throughout (“transaminase elevation”, “hepatocellular”, “cholestatic”); the plain-language terms in the at-a-glance are required by item 7.4 and mirror the ER Conclusion. |
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 headings present verbatim at lines 446, 492, 537, 619, 645, 649–651, 567, 581, 782; tier labels at lines 540, 544, 550, 557, 622, 626, 632, 638. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | 67 data-qrs-var spans present covering every named variable in the checklist, plus the three website="…" template spans at lines 423, 426, 440. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The website="evidence_review", website="audit" and website="full_review" spans are untouched and empty as delivered by 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 ER section drawn on by the QRS is empty; every source section carries content. |
| 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. | 🟢 | “Standardised extract dose”, “Best time of day”, “Single versus split dosing” match ER lines 349, 359, 363; interaction labels match ER lines 301, 305, 307, 309, 311, 313, 315. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Marker names match the ER biomarker table column 1 exactly; no invented labels appear. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Full-text scan finds no emoji; the ER’s “⚠️ Conflicted” markers are 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. | 🟢 | Each section is compressed to the minimum the content-fidelity items allow: mechanisms, effect sizes, citations and glossary parentheticals are stripped throughout, and no section is expanded beyond the ER’s own item count. |
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 immediately follows <!doctype html> on line 1 and precedes all other markup. |
| 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 descriptive text on line 2 sits before 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. | 🟢 | Wholly enclosed in an HTML comment; no element repeats any metadata value on the page. |
| 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:03" is quoted, correctly so because the value 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: guduchi_2026-0825-1458_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-0816-1633, correct format. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | Line 7: qrs_creator_ai_nickname: Opus. |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | “Opus” is a single word with no version or qualifier. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | Line 8: qrs_creator_ai_fullname: Opus 5. |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | “Opus 5” is nickname plus version number with no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: guduchi_2026-0825-1458_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 lines 4–12: values are trimmed and unquoted except the colon-bearing duration. |
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: “Guduchi 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: “Guduchi for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/16/2026”, the correct reformatting of 2026-0816-1633. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”, matching the frontmatter 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 holds only the title and the standard subline; the ER’s “Also known as” line is 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 |
🟢 | Lines 434–438 compress the ER Conclusion (lines 475–479) into the two facts that drive the decision: what is reliably gained and what is risked. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 55 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | “inexpensive, widely available” ← ER 479; “broad but shallow research base” ← ER 475; “modest blood-sugar lowering… hay-fever-type nasal symptoms… small studies of uneven quality” ← ER 475; “uncommon, unpredictable, occasionally severe liver inflammation with immune features” ← ER 477/479. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Uses “blood-sugar lowering” and “hay-fever-type nasal symptoms” rather than glycaemic control and allergic rhinitis; no acronyms appear. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year or sample size appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numeric result is quoted; effect size is conveyed qualitatively as “modest”. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All seven items map to the ER’s “Populations who should avoid Guduchi” list at ER lines 319–325. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All seven ER avoidance populations are present, and the ER’s absolute contraindication for transplant recipients (ER line 303) is captured by the transplant item. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Lines 570–576: seven 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. | 🟢 | The ER’s trailing clause “where liver monitoring is already critical” is stripped from the tuberculosis item; the glossary parentheticals for AST and Child-Pugh are removed. No dash-trailing clauses 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). | 🟢 | Clinical staging “(Child-Pugh Class B or C)”, threshold “above twice the upper limit of normal” and the age cut-off “under 18 years” 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 identifies 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. | 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 to the ER interaction bullets at ER lines 301–315. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Seven of the ER’s eight interaction bullets are carried; “Immunosuppressants” is correctly excluded because the ER grades it “absolute contraindication in transplant recipients” and that population is already in [stop_items]. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Lines 584–609: seven discrete <li> elements inside the span. |
| 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. | 🟢 | The ER’s Severity / Consequence / Mitigation clauses are stripped from every item; only label plus agents remain. |
| 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 exemplars are retained throughout: “(glimepiride, glibenclamide)”, “(ketoconazole, itraconazole, voriconazole)”, “(simvastatin, atorvastatin)”, “(amlodipine, felodipine)”, “(apixaban, rivaroxaban)”, “(ibuprofen, naproxen)”. |
| 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 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 bullets at ER lines 349, 359 and 363. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose, timing and dose-splitting are the three decisions the ER’s protocol section actually resolves; the remaining bullets are attribution, pharmacokinetics or “no difference established” entries. |
| 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 used. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | Lines 450–487: all nine variables carry substantive ER-derived content, none left as placeholder. |
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 | 🟢 | Blood sugar, nasal allergy symptoms and joint outcomes are the only three time-to-effect windows the ER states (ER line 406, with the 12-week qualifier from ER line 441). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Blood sugar is the ER’s sole High-tier benefit and comes first; nasal allergy and knee osteoarthritis are Medium-tier and follow. |
| 11.3 | If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. | N/A | The ER provides three distinct time-to-effect aspects; 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. | 🟢 | Lines 498–529: all nine variables carry ER-derived content (“12–24 weeks”, “Within 15 days”, “A course shorter than 8 weeks tests nothing”). |
| 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 ten items map one-to-one to the ER benefit headings at ER lines 157–217. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present at lines 539, 542, 548, 555 with the correct tier assignments. |
| 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 benefit heading; the ER’s Magnitude lines, CI values and “See …” citations are all dropped. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses remain in any benefit item; the ER’s “⚠️ Conflicted” flag on the anti-tuberculosis item is also stripped as required by item 4.4. |
| 12.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | N/A | All four tiers carry items in the ER, so no span needs hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | All seven items map one-to-one to the ER risk headings at ER lines 239–283. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present at lines 621, 624, 630, 637 with the correct tier assignments. |
| 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 risk heading; the ER’s case counts, median intervals and citations are dropped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses remain in any risk item; the “⚠️ Conflicted” flags on the hepatic and immune-stimulation items are stripped. |
| 13.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | N/A | All four tiers carry items in the ER, so no span needs hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | The table reproduces the ER Monitoring Protocol & Defining Success biomarker table at ER lines 434–444. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All nine ER biomarkers present: ALT, AST, total bilirubin, ALP and GGT, ANA and IgG, HbA1c, fasting glucose, blood eosinophil count, hs-CRP, with targets and rationales carried verbatim. |
| 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 772–776 reproduce the ER cadence paragraph at ER line 432, including the post-stop panel and the 12-week efficacy re-check. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | The six items reproduce the ER’s “Qualitative markers worth tracking” list at ER lines 448–453. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six present: nasal symptom burden, energy and fatigue, appetite/nausea/right-upper-abdominal discomfort, urine colour and yellowing, joint pain and morning stiffness, respiratory infection frequency. |
Issues 16/08/2026 16:46
Pass rate 100.00%. No issues found.
Issues 16/08/2026 16:35
- 2.15 — Colloquial “cheap” in at-a-glance: [at_a_glance] (line 434) opens “A cheap, widely available Indian stem extract”; “cheap” is consumer-grade register where the ER’s own voice uses “inexpensive” (ER lines 414 and 479).
Fixes 16/08/2026 16:35
- 2.15 — Colloquial “cheap” replaced: Changed the [at_a_glance] opening from “A cheap, widely available Indian stem extract” to “An inexpensive, widely available Indian stem extract”, matching the ER’s own register.