Audit: QRS - ATX-304 for Health & Longevity
Audit conducted on 27/08/2026 16:21 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 span against the ER: at-a-glance vs ER Conclusion (l.491-493), protocol cells vs ER Therapeutic Protocol (l.353-359), time cells vs ER Practical Considerations (l.412), all 15 monitoring rows vs ER table (l.444-458). All literally supported. |
| 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 carried through, e.g. “Nothing meaningful should be expected inside two weeks” (time_1_sub) and “has never been tested” (action_3_sub) match ER l.412 and l.359. |
| 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; contraindication thresholds (SBP below 100 mmHg, eGFR below 45, Child-Pugh B or C, MI within 90 days) reproduced at ER strength. |
| 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. | 🟢 | Benefits from ER Expected Benefits, risks from Potential Risks & Side Effects, gates from Key Interactions & Contraindications; no modifying factor is surfaced as 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. | 🟢 | No PMIDs, author names, NCT IDs or brand names appear. Generic drug names in the interaction gate (glipizide, semaglutide, etc.) are taken from the same ER bullets (l.296-310). |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions of any kind appear 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-limited register; the ER’s own “thin record” framing is preserved in at_a_glance. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert and data-driven (targets, thresholds, timing) while remaining accessible; frames what is knowable rather than alarming. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents trial-derived facts and target ranges; no prescriptive instruction to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No advice language; the monitoring cadence is stated as a schedule of measurements, not a directive. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “recommend”, “advise” or “should you” constructions anywhere in the body. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document body (verified over the whole <body>). |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language throughout; retained abbreviations (HOMA-IR, HbA1c, ALT, eGFR) are the ER’s own biomarker names and are necessary for the monitoring table. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Benefits and risks collapsed to one line per tier; interaction and contraindication bullets stripped to the key fact. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed — no direct address. |
| 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. | 🟢 | Framing (studied exposures, home monitoring, gray-market sourcing caveat) targets the proactive, risk-aware self-optimizer. |
| 2.11 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | Assumes willingness to run a two-week baseline, daily home blood-pressure logging and imaging-based body composition. |
| 2.12 | The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort. | 🟢 | Not written for the general population; effort-heavy monitoring and investigational-compound framing throughout. |
| 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 closes on the audience-relevant signal — no repeated result, four-month maximum exposure, company-funded data, no verifiable retail source. |
| 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; “slowed kidney aging” mirrors the ER’s own benefit heading. |
| 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. | 🟢 | “Oral medication”, “hypotension”, “treatment-emergent adverse events”, “orthostatic” used in the document’s own voice; the plainer wording in at_a_glance is the ER Conclusion’s own register 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” |
🟢 | “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, tier labels and “Marker / Target / Why” all byte-identical to the template. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All 38 template span names present; marker_#* and qualitative_item# expanded to 15 and 6 numbered instances respectively. No span missing. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Structural diff against the template shows changes only inside data-qrs-var regions and the metadata block; the website=”evidence_review”, website=”audit” and website=”full_review” spans and all CSS are untouched. |
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 ER’s High benefit and High risk tiers are handled under items 12.5/13.5 rather than by empty-state phrasing. |
| 4.2 | Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. | 🟢 | Protocol labels “Studied doses”, “Time of day”, “Single versus split dosing” are the ER’s bold labels verbatim (ER l.353-359); interaction row labels reproduce the ER’s bold labels (ER l.294-312). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | All 15 monitoring marker names and all three protocol labels are verbatim ER strings; no invented labels. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji characters anywhere in the file (verified over the full document); the ER’s ⚠️ Conflicted marker was 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: four benefit tiers reduced to three one-line entries, five risk tiers to three, contraindication and interaction bullets stripped of glosses and rationale. |
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> (l.2-14), before the template comment at l.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. | 🟢 | YAML opened at l.3 and closed at l.13; the descriptive text at l.2 precedes the opening marker. |
| 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 metadata value is echoed by any rendered 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 and unquoted except duration: “00:03”, which contains a colon and therefore requires quoting. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: atx_304_2026-0827-1322_Opus_ER.md (l.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 (l.5), matching the version badge of QRS.md. |
| 5.7 | Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) | 🟢 | qrs_creation_date: 2026-0827-1614 (l.6), correct YYYY-MMDD-HHMM format. |
| 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 (l.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 (l.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” = nickname plus version number, no additional qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: atx_304_2026-0827-1322_Opus_QRS.html (l.9), matching the file on disk. |
| 5.13 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | Re-verified: no stray whitespace or unnecessary quoting in any frontmatter value. |
6. Page Title & Header
| # | Description | Result | Comments |
|---|---|---|---|
| 6.1 | [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &) |
🟢 | |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | header_topic = “ATX-304 for Health & Longevity” (l.417), matching the ER canonical_topic with & encoded. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | header_subline_date = 08/27/2026 (l.421), the MM/DD/YYYY form of qrs_creation_date 2026-0827. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | header_subline_model = Opus 5 (l.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. | 🟢 | Header carries only the template’s date, source-review and AI4L line; no badge, version stamp, AKA line (ER alternate names O304/O-304/ATX304 are not surfaced) or audit date. |
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 (l.491-493): what the compound is, what the two studies moved, and the four limits that govern any decision. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 59 words (counted programmatically), within the 60-word limit. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a distinct ER Conclusion passage — mechanism (l.491), the measured changes (l.491), no repeated result / four months / company funding / unverifiable supply (l.493). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms or technical classifications; “the enzyme cells use to sense low fuel” replaces AMPK, “resting energy burn” replaces resting metabolic rate. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | “Two short studies” — no trial name (TELLUS is not used), no year, no sample size, no p-value. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes, relative risks or statistics; “lowered”, “reduced”, “raised” carry direction only. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from the ER’s Key Interactions & Contraindications section, populations list at l.314-325 plus the absolute-contraindication interaction at l.310. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All 10 ER “Populations who should avoid ATX-304” bullets are present, plus the concomitant agent the ER itself grades “Severity: absolute contraindication” (ER l.310). |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | All 11 items are <li></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 rationale after the colon (e.g. “the compound is investigational and holds no marketing authorisation”) is stripped; no trailing dash 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). | 🟢 | Every qualifier preserved: “below 100 mmHg”, “Class III–IV”, “Child-Pugh Class B or C”, “eGFR below 45 mL/min/1.73 m²”, “within 90 days”, “without dose adjustment”. Only plain-language glosses were dropped. |
| 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 uses no ranking notation inside parentheses in this section. |
| 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 compound (l.314-325). |
| 8.8 | If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. | N/A | The section is not left empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from the ER’s Key Interactions & Contraindications bullets at l.294-312. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All 10 ER interaction bullets are represented except the mitochondrial-uncoupler bullet, which is correctly carried in Contraindications instead — 9 items, no duplication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | All 9 items are <li></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. | 🟢 | Severity, consequence and mitigation text stripped from every bullet; the em-dash gloss on the GLP-1 entry (“— drugs mimicking a gut hormone…”) is removed. |
| 9.5 | Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Example drug lists preserved verbatim for insulin/sulfonylureas, antihypertensives, GLP-1 agonists, diuretics, NSAIDs, AMPK-activating and blood-pressure-lowering supplements. |
| 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 uses no ranking notation inside parentheses in this section. |
| 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 ten interactions that change how the compound is used. |
| 9.8 | If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. | N/A | The section is not left empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Derived from the ER Therapeutic Protocol section (l.349-377). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Studied doses, time of day and single-versus-split dosing are the three actionable implementation bullets; the remaining ER bullets are half-life, competing approaches and 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 three or more distinct actionable implementation aspects, 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 action cells carry ER-derived content; action_1_sub reproduces both dosing arms including the 8-week open-label extension. |
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 | 🟢 | Fasting glucose (days 21–28), blood pressure (day 28) and the 8-week fat/lipid/metabolic-rate readouts are the only time-anchored effects the ER reports. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered as the ER orders the corresponding Medium-tier benefits: glucose and insulin sensitivity first, blood pressure second, fat/lipid/metabolic-rate third. |
| 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 exist, 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 cells carry ER-derived content; time_1_sub reproduces the ER’s 14-day steady-state caveat verbatim. |
| 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 (l.412), 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 (l.126-198). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four benefit spans present and correctly named. |
| 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 tier is a semicolon-separated list of the ER’s benefit headings only — no magnitudes, p-values or mechanisms. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | Parentheticals stripped, e.g. “Reduced Formation of Abdominal Aortic Aneurysm (a bulge in the body’s main artery)” → “reduced formation of abdominal aortic aneurysm”. |
| 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. | 🟢 | benefits_high is set to style=”display: none” and left empty, matching the ER’s “No benefit reaches High” (l.132); no empty-state phrasing was inserted. |
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 (l.218-274). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four risk spans present and correctly named. |
| 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 tier lists the ER’s risk headings only; the five speculative risks are reduced to their bare headings. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | Parentheticals stripped, e.g. “Hypoglycemia (low blood sugar) in Combination with Glucose-Lowering Drugs” → “Hypoglycemia in combination with glucose-lowering drugs”. |
| 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. | 🟢 | risks_high is set to style=”display: none” and left empty, matching the ER’s “No risk reaches High” (l.224). |
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 (l.438-458). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All 15 ER biomarkers are listed in ER order, with target ranges and rationale reproduced 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. |
🟢 | monitoring_cadence condenses the ER’s baseline, daily/weekly, 4-/12-week, 3-6-month and 6-/12-month schedule plus the day-14 rule (ER l.440). |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from the qualitative markers list in the ER Monitoring Protocol & Defining Success section (l.462-467). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers are present and verbatim. |
Issues 27/08/2026 16:21
Pass rate 100.00%. No issues found.