Audit: QRS - Amla for Health & Longevity
Audit conducted on 29/08/2026 04:29 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. | 🟢 | Every populated span traces to ER text: at-a-glance to Conclusion, protocol cells to Therapeutic Protocol, time cells to Practical Considerations and Expected Benefits, tier lists to the ER benefit/risk headings, gates to Key Interactions & Contraindications, markers and qualitative items to Monitoring Protocol & Defining Success. |
| 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. | 🟢 | marker_10_target retains “No established target for supplement users; track change from the individual’s own baseline”; risks_speculative retains “unknown safety in pregnancy and lactation”. |
| 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”). | 🟢 | ER “Absolute contraindication in practice” for anticoagulants appears in stop_items, not in caution_items; ER “Monitor” items (metformin, antihypertensives, antacids, iron) appear in caution_items. |
| 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. | 🟢 | Nothing from ER Benefit-Modifying Factors or Risk-Modifying Factors appears in the gates or risk tiers; all risk-tier entries map to ER Potential Risks & Side Effects headings. |
| 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, author names, NCT identifiers or brand names at all. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attribution appears; the ER’s Examine and Natreon/Arjuna/Sami-Sabinsa attributions were correctly dropped rather than reassigned. |
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. | 🟢 | Measured, evidence-first register carried over from the ER, including the ER’s own hedges (“results conflict”, “signals are mixed”). |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Quantified targets and time windows paired with plain-language explanations of why each marker matters. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Content is stated descriptively (“What the trials used”, “Measured at 12 weeks in most trials”) rather than as instruction. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperative or directive constructions; the cadence text is phrased passively (“panel repeated at 12 weeks”). |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No instance of “recommend”, “advise”, “should”, or “you should” anywhere in the rendered text. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronoun occurs in the document; third-person constructions used throughout (“the individual’s own baseline”, “anyone on glucose-lowering medication”). |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are used only where they are the marker name; elsewhere plain glosses are used (“raised blood lipid”, “blood-vessel lining function”). |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Tier lists are bare semicolon-separated phrases; gate items are single facts; sub-cells are at most two short sentences. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no “you”/”your”/”we”/”our” in the body text. |
| 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. | 🟢 | Optimal functional ranges (LDL under 70 mg/dL, hs-CRP under 0.5 mg/L) rather than conventional clinical cut-offs. |
| 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. | 🟢 | Full baseline panel, specialist platelet aggregation testing and blood lead assume 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. | 🟢 | Assumes twelve-marker baseline testing and 12-week reassessment, well beyond 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. | 🟢 | At-a-glance leads with the two consistent benefits and flags the antiplatelet effect and product-quality problem as the decision-relevant issues for supplement users. |
| 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 in the title; “anti-aging” appears nowhere in the document. |
| 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. | 🟢 | Formal terms used throughout (“antiplatelet”, “hypoglycaemia”, “apolipoprotein B”); the at-a-glance plain-language phrasing mirrors the ER Conclusion verbatim and is required by item 7.4. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why” | 🟢 | All present unmodified at lines 446, 493, 544, 628, 653, 835 (headings), 577 and 598 (gates), 548/554/561/566 and 631/635/640/644 (tiers), 657–659 (column headers). |
| 3.2 | All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 named template spans are present, plus twelve marker_#_* triplets and six qualitative_item_# spans expanded from the template’s repeatable rows. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The three non-variable spans website="evidence_review", website="audit" and website="full_review" are byte-identical to the template (lines 423, 426, 440). |
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; every benefit tier, risk tier, gate list and monitoring row has source 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. | 🟢 | action_1_label “Standard extract protocol”, action_2_label “Whole-fruit protocol” and action_3_label “Best time of day” reproduce the ER Therapeutic Protocol bold labels verbatim. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Marker names match the ER biomarker table verbatim; tier labels are template-fixed; time-to-effect labels reuse ER phrases (“Reflux symptom relief”, “Improved endothelial function”). |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji in the file; the ER’s 🟩/🟥/🟨 tier markers and ⚠️ conflict flags were correctly dropped. |
| 4.5 | The QRS is designed to render on one A4 page. Any section that has more content in the ER than fits the per-section budget is condensed by the LLM, not extended onto a second page. | 🟢 | Every section is condensed rather than extended: tier lists are reduced to bare ER headings, gate items to single facts with trimmed parentheticals, marker rationales to one clause. Remaining length is driven by the completeness mandates in items 8.5, 9.5, 14.2 and 15.2, not by elaboration. |
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 the template comment on line 16. |
| 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 “QRS — Metadata” caption sits above 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. | 🟢 | Enclosed in an HTML comment; no element in the body repeats any metadata value. |
| 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, 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: amla_2026-0829-0002_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-0829-0411, 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 with no trailing qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: amla_2026-0829-0002_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, including the workflow-added duration, git_user and git_issue. |
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: Amla 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: Amla for Health & Longevity. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 08/29/2026, the correct reformatting of 2026-0829-0411. |
| 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. | 🟢 | The header contains only the title and the template subline; the ER’s “Also known as” list was not carried over. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses all three Conclusion paragraphs into the consistent benefits, the mixed blood pressure signal, the antiplatelet concern and the product-quality problem. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 58 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a distinct Conclusion sentence (lines 519 and 521 of the ER). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; uses “harmful cholesterol”, “blood sugar”, “platelet stickiness”, “blood thinners” in place of LDL, glycaemia, platelet aggregation and anticoagulants. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No author, year, sample size or p-value appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | Only directional statements (“lower”, “mixed”, “reduced”); no numeric effect appears. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | All six items map to the ER’s “Populations who should avoid Amla” list inside that section. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All six ER avoid-populations are represented, none added. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Lines 580–593: six discrete <li> elements inside the stop_items span. |
| 8.4 | Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. | 🟢 | ER trailing clauses removed: “on absence of any safety data” and “both of which are untested with amla” are gone; no dash-introduced clause remains in any item. |
| 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). | 🟢 | “platelet count below 100 × 10⁹/L”, “Within 10 days”, “filtration rate below 30 mL/min/1.73 m²” and “Child-Pugh Class C” all preserved, with the ER’s eGFR gloss trimmed. |
| 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 avoid-populations 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 six such populations and the section is correctly populated rather than left 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 nine items map to bullets in that ER section. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | The ER’s eleven interaction bullets minus “Anticoagulants” and “Other interventions — surgery, dental extraction and colonoscopy with biopsy”, both already in stop_items, gives exactly the nine items listed. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Lines 601–618: nine discrete <li> elements inside the caution_items 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. | 🟢 | All “Caution/Monitor” verdicts, mechanisms and mitigations stripped; the ER’s em-dash gloss “— drugs that reduce stomach acid” removed from the antacid 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). | 🟢 | Every ER example-drug list is preserved verbatim across the antiplatelet, insulin/sulfonylurea, antihypertensive, NSAID, acid-suppressant and both supplement-stacking items. |
| 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 names eleven interactions and the section is correctly populated rather than left 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. <!– 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 cells derive from the ER Therapeutic Protocol bullets. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose/form (“Standard extract protocol”), the whole-fruit alternative, and timing are the three implementable bullets; the remaining ER bullets are attributional or non-actionable (genetics, sex, age, competing approaches). |
| 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 at least three distinct actionable aspects and 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 spans populated: “500 mg twice daily”, “1–3 g daily” and “Split morning and evening, with meals” with ER-derived supporting text in each sub-cell. |
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 | 🟢 | Lipid/glucose/inflammation at 12 weeks and reflux at 2–4 weeks come from the ER Practical Considerations “Time to effect” bullet; endothelial function at 12 weeks comes from the ER Expected Benefits endothelial entry. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered High-tier benefits first (lipids, glucose, inflammation), then the two Medium-tier benefits in the ER’s own order (endothelial function, then reflux). |
| 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 | Three distinct time-to-effect aspects are available in the ER and 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 spans populated with ER-derived values (“12 weeks”, “12 weeks”, “2–4 weeks”) and supporting detail including the ER’s “Nothing is detectable in days”. |
| 11.5 | If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel |
N/A | The ER provides time-to-effect information, so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All sixteen entries correspond one-to-one with the ER’s benefit headings across its four tiers. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated (lines 546, 552, 559, 564). |
| 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. | 🟢 | Entries are bare heading phrases; no magnitude, confidence interval, p-value, trial name or mechanism from the ER body text was carried over. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content appears in any tier; the ER’s “⚠️ Conflicted” flags on the lipid and blood pressure headings were also 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. | N/A | All four ER benefit 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’s risk headings across its four tiers. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated (lines 630, 633, 639, 642). |
| 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. | 🟢 | Entries are bare heading phrases; the ER’s event counts, crossover-study detail and “Not quantified in available studies” notes were all excluded. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content appears in any tier; the “⚠️ Conflicted” flag on the gastrointestinal heading was 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. | N/A | All four ER risk tiers contain items, so no span needed hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Rows reproduce the ER Monitoring Protocol & Defining Success biomarker table, mapping “Optimal Functional Range” to Target and “Why Measure It?” to Why. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All twelve ER biomarkers present, in ER order: LDL cholesterol, apolipoprotein B, triglycerides, HDL cholesterol, glycated haemoglobin, fasting glucose, fasting insulin, hs-CRP, platelet count, platelet aggregation response, alanine aminotransferase, blood lead. |
| 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 824 carries the baseline panel, the 12-week and 6–12-month recheck interval, annual platelet and liver enzymes, and the first-four-weeks self-monitoring window, all from the ER’s cadence paragraph. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | All six items reproduce the ER’s “Qualitative markers worth tracking alongside the labs” list. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers present and in ER order: digestive comfort, bruising and gum bleeding, reflux frequency, energy and post-meal alertness, hair shedding volume, low blood sugar symptoms. |
Issues 29/08/2026 04:29
Pass rate 100.00%. No issues found.
Issues 29/08/2026 04:26
- 2.15 — Consumer-grade term for dyslipidaemia: [action_1_sub] (line 458) reads “the raised blood fat, diabetes and endothelial-function trials”, where the ER’s Therapeutic Protocol writes “the dyslipidaemia, diabetes and endothelial-function trials”; the QRS uses the formal register “lipid” elsewhere ([time_1_label], [benefits_high]), so its own voice is inconsistent.
Fixes 29/08/2026 04:26
- 2.15 — Consumer-grade term for dyslipidaemia: Changed [action_1_sub] from “the raised blood fat, diabetes and endothelial-function trials” to “the raised blood lipid, diabetes and endothelial-function trials”, aligning the register with the “lipid” wording used elsewhere in the QRS.
Issues 29/08/2026 04:18
- 2.7 — Unglossed jargon in protocol sub: [action_1_sub] (line 458) reads “The dose used in the dyslipidaemia, diabetes and endothelial-function trials”, carrying “dyslipidaemia” without the plain-language gloss the ER supplies (“abnormally high blood fats”) and that the QRS applies to comparable terms elsewhere.
Fixes 29/08/2026 04:18
- 2.7 — Unglossed jargon in protocol sub: Replaced “dyslipidaemia” with the ER’s own plain-language equivalent in [action_1_sub], so the cell now reads “The dose used in the raised blood fat, diabetes and endothelial-function trials”.