Audit: QRS - Olive Extract for Health & Longevity
Audit conducted on 16/08/2026 09:55 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. | 🟢 | Verified item by item against the ER: protocol cells (ER 354, 364, 368), time-to-effect (ER 411), benefit and risk headings (ER 160-224, 248-290), gate items (ER 310-332), monitoring table (ER 443-451) and qualitative markers (ER 455-460) all trace to ER text. |
| 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. | 🟢 | Cautious ER phrasing is carried through: “genuinely conflicted” (ER 482), “where they occur” -> “Applies only where lipid and glucose changes occur at all”, “none compared the two directly” -> “the two were never compared directly”. |
| 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 strengthening or softening detected; contraindications keep their absolute framing and speculative tiers keep their tier label. |
| 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” list, interactions from the ER interaction bullets, risks from Potential Risks & Side Effects; no cross-category migration. |
| 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. | 🟢 | No PMIDs, PubMed links, NCT identifiers, author names, or branded extract names (EFLA 943, Bonolive, Hytolive, OliPhenolia) appear anywhere in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind are present in the QRS. |
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 measured, evidence-first register. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert and data-driven (explicit thresholds and target ranges) while remaining accessible. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents evidence and ER-stated protocol content without issuing instructions to a reader. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperative or advisory constructions; the footer disclaimer is the unmodified template text. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Content is stated descriptively (“Split dosing preferred”, “dosing with food is chosen for tolerability”) rather than as a recommendation to act. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Acronyms are expanded on first use in the monitoring table (HbA1c, LDL-C, hs-CRP, ALT, TSH); at-a-glance uses “blood sugar” and “cholesterol”. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Tiered single-line lists, a three-column marker table, and compact protocol cells; no prose paragraphs beyond the at-a-glance line. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed by full-text scan: no “you”/”your”. |
| 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 readers already tracking blood pressure, lipids, glucose and thyroid markers at home. |
| 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 twice-daily home blood pressure logging, daily fasting glucose for four weeks, and repeat panels at 12 weeks. |
| 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 monitoring burden and standardization detail exceed what a general-population sheet would carry. |
| 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 gates foreground the additive-effect risks that matter to a self-experimenting, already-medicated 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. | 🟢 | The term “anti-aging” does not appear; the speculative tier uses “Cellular Longevity Signaling”. |
| 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 terminology throughout (“orthostatic hypotension”, “hepatic impairment”, “thyroid-stimulating hormone”); the qualitative markers reproduce ER wording verbatim. |
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 headings present unmodified: Protocol, Time to effect, Benefits, Risk & Side Effects, Monitoring, Qualitative Assessment, Contraindications, Key Interactions, High/Medium/Low/Speculative, Marker/Target/Why. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All template spans present: page_title, header_topic, header_subline_date, header_subline_model, at_a_glance, action_1-3 (label/value/sub), time_1-3 (label/value/sub), benefits_, stop_items, caution_items, risks_, marker_1-9_*, monitoring_cadence, qualitative_item_1-6. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The non-variable spans (website=”evidence_review”, website=”audit”, website=”full_review”), the stylesheet link, the CSS block and the footer disclaimer are byte-identical to 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 | N/A — no section of the source ER is empty; every ER section drawn on by the QRS carries content, so no empty-state phrasing applies. |
| 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. | 🟢 | Protocol cell labels reproduce the ER’s bold labels verbatim: “Standard leaf extract protocol”, “Best time of day”, “Single versus split dosing” (ER 354, 364, 368). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Gate labels reproduce the ER’s bold interaction labels; monitoring marker names reproduce the ER biomarker column verbatim. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | Character-level scan confirms no code point above U+2500 in the file; the ER’s tier emoji and the “Conflicted” warning 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. | 🟢 | The unmodified one-page template is used, with each section condensed relative to the ER: mechanisms, magnitudes, citations and modifying factors are all dropped, and gate items are trimmed to the key fact plus the qualifying parenthetical. |
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. | 🟢 | The metadata comment is the first element after “<!doctype html>” at line 2, before the template comment at line 16 and the <html> element. |
| 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. | 🟢 | Opened at line 3 and closed at line 13; the preceding text “QRS - Metadata (invisible, parsed by audit tooling)” sits outside the delimiters. |
| 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 and not echoed by any visible element. |
| 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; only “duration: "00:03"” is quoted, which is required because the value contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | “er_filename: olive_extract_2026-0825-0700_Opus_ER.md” at 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.7.02” at line 5, matching the version stated at the top 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-0816-0943” at 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” at 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” at 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: olive_extract_2026-0825-0700_Opus_QRS.html” at line 9, matching the actual filename. |
| 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 or unnecessary quoting on any key. |
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 &) |
🟢 | “Olive Extract for Health & Longevity - Quick Reference Sheet” at line 22, 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 &) |
🟢 | “Olive Extract for Health & Longevity” at line 417, matching canonical_topic in the ER frontmatter. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | “08/16/2026” at line 421, the MM/DD/YYYY form of qrs_creation_date 2026-0816. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | “Opus 5” at line 425, matching 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 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 (ER 482-486) into preparation, strongest finding, conflicted findings, hazard origin and product variability. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 59 words, verified by word count. |
| 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: ER 482 (preparation, blood pressure, conflicted lipids/glucose), ER 484 (hazards follow the benefit), ER 486 (product strength varies enormously). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Uses “blood pressure”, “cholesterol” and “blood sugar”; no acronyms or evidence-grade classifications. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, sample sizes or p-values. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes, confidence intervals or statistical results. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from the ER’s “Populations who should avoid Olive Extract” list inside Key Interactions & Contraindications (ER 324-332). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All seven ER avoid-list entries are represented, in ER order. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each item is a discrete <li></li> inside the [stop_items] span (lines 546-552). |
| 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 is stripped: “- human safety data are absent…” dropped from pregnancy/lactation, “- given the theoretical antiplatelet effect” dropped from the surgery item, and the “most advanced grade of liver failure” gloss dropped from Child-Pugh Class C. |
| 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 retained: “below 100 mmHg”, “(glucose below 70 mg/dL more than twice weekly)”, “(Child-Pugh Class C)”, “below 0.1 mIU/L”, “within 14 days”. |
| 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. | 🟢 | The ER uses no ranking notation inside parentheses in this list, and none is carried through. |
| 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, and the ER does identify populations that should avoid the intervention, so leaving it empty would have been incorrect. |
| 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 | N/A — the Contraindications gate is populated with seven items, so the empty-section comment requirement does not apply. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from the seven interaction bullets of the ER Key Interactions & Contraindications section (ER 310-322). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All seven ER interaction bullets are represented; none duplicates a contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Each item is a discrete <li></li> inside the [caution_items] span (lines 560-566). |
| 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 “- caution, monitor” / “- caution” suffixes and all mitigation clauses (“Mitigation: home blood pressure logging” etc.) are stripped; only the agent class and its examples 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 example drugs are preserved for every class: lisinopril/ramipril, losartan/valsartan, amlodipine, glipizide/glyburide, ibuprofen/naproxen, pseudoephedrine/phenylephrine. |
| 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. | 🟢 | The ER uses no ranking notation inside parentheses in this list, and none is carried through. |
| 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, and the ER identifies seven interaction classes, so leaving it empty would have been incorrect. |
| 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 | N/A — the Key Interactions gate is populated with seven items, so the empty-section comment requirement does not apply. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Derived from the ER Therapeutic Protocol section (ER 352-378). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Covers dose and standardization (ER 354), timing (ER 364) and dose splitting (ER 368) - the three aspects that determine how the intervention is actually taken. |
| 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 | N/A — three distinct actionable implementation aspects are present (dose/standardization, timing, split dosing), so no set is unused. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All nine protocol cells carry ER-derived content; none is placeholder or empty-state text. |
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 pressure, lipids and glucose, and bone markers are the only three time-to-effect aspects the ER states (ER 411). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by benefit tier: blood pressure (High), lipids and glucose (Medium), bone density (Low). |
| 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 | N/A — three distinct time-to-effect aspects are present (blood pressure, lipids and glucose, bone markers), so no set is unused. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time-to-effect cells carry ER-derived content, including the ER’s own hedges (“where they occur”). |
| 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 | N/A — the ER provides time-to-effect information (Practical Considerations, ER line 411), so the section is correctly retained. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Derived from the ER Expected Benefits section (ER 156-224). |
| 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. | 🟢 | Only the ER’s benefit headings are carried; magnitudes, mechanisms and trial descriptions are dropped. |
| 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 parenthetical detail are stripped from the benefit entries. |
| 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 | N/A — all four benefit tiers (high, medium, low, speculative) carry items, so no span needs hiding. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Derived from the ER Potential Risks & Side Effects section (ER 244-290). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four risk spans are present and populated. |
| 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. | 🟢 | Only the ER’s risk headings are carried; magnitudes, mechanisms and trial descriptions are dropped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical frequencies, severity grades or study notes survive into the risk entries. |
| 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 | N/A — all four risk tiers (high, medium, low, speculative) carry items, so no span needs hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from the ER Monitoring Protocol & Defining Success section (ER 435-451). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All nine ER biomarkers are listed with their optimal ranges and rationale verbatim: blood pressure, fasting glucose, HbA1c, fasting insulin, triglycerides, LDL-C, hs-CRP, ALT, TSH. |
| 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. |
🟢 | Populated with the ER’s ongoing-monitoring cadence (ER 439), covering home blood pressure, fasting glucose, the 12-week panel, TSH at 8-12 weeks and the 6-12 month repeat. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from the ER’s qualitative marker list inside Monitoring Protocol & Defining Success (ER 453-460). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers are listed, in ER order, with their identifying wording intact. |
Issues 16/08/2026 09:55
Pass rate 100.00%. No issues found.
Issues 16/08/2026 09:47
- 11.4 — Dangling time-to-effect caption: [time_2_sub] at line 504 contains only “Where they occur”, a fragment cut out of ER line 411 that loses its antecedent and renders as an uninterpretable caption under the “Lipids and glucose / 6–12 weeks” cell.
Fixes 16/08/2026 09:47
- 11.4 — Dangling time-to-effect caption: Replaced [time_2_sub] “Where they occur” with “Applies only where lipid and glucose changes occur at all”, restoring the antecedent lost when the fragment was cut from ER line 411.