Audit: QRS - Hydroxocobalamin for Health & Longevity
Audit conducted on 11/09/2026 02:14 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. | 🟢 | Spot-checked every span against the ER: protocol values vs ER lines 354-358, benefit/risk items vs the ER heading text, gate items vs ER lines 307-332, monitoring rows vs the ER biomarker table (lines 443-452), qualitative items vs ER lines 456-462. All literal. |
| 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’s ⚠️ Conflicted markers on “Survival After Cyanide Exposure” and “Elevated Circulating B12” are carried as “(conflicted)” in benefits_low and risks_low. |
| 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”). | 🟢 | “Absolute avoidance” (nitrous oxide), the eGFR<30 and 160/100 mmHg thresholds, and the gram-scale-only restrictions are all carried at ER strength, neither raised nor relaxed. |
| 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; Key Interactions from the ER interaction bullets; no Benefit- or Risk-Modifying Factor is surfaced as a gate or a side effect. |
| 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 identifiers or citations anywhere in the QRS. Only generic drug names that appear in the ER (omeprazole, esomeprazole, famotidine, hydrochlorothiazide, furosemide, indapamide, metformin, colchicine, chloramphenicol). |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | The ER’s “Cochrane data” attribution in the oral high-dose bullet is dropped in action_3_sub; no attribution is added anywhere. |
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, dose-stratified 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 (thresholds, ranges, cadence) while remaining accessible; the at-a-glance states what is strong and what is unproven without hedging into vagueness. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents gates and ranges as evidence, not as instructions to a patient. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperative directed at a reader; all directive-sounding wording (“absolute avoidance”, “caution”) is the ER’s own classification of the interaction. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No “recommended”, “advised” or “should” constructions in the QRS’s own voice. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns present anywhere in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms are confined to ER-verbatim headings and biomarker names; the at-a-glance renders homocysteine as “the marker that rises when the vitamin is lacking”. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Every item is reduced to a single clause; benefits and risks are collapsed to semicolon-separated tier lines. |
| 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. | 🟢 | Framed for proactive adults: absorption decline after 50, functional rather than conventional biomarker targets, oral vs injected trade-off. |
| 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. | 🟢 | Presents intramuscular injection schedules, a 10-marker panel and a multi-point cadence without softening for convenience. |
| 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. | 🟢 | Functional targets (holotranscobalamin >50 pmol/L, MMA <0.27 µmol/L) are tighter than conventional cut-offs, which is the non-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. | 🟢 | The dose split that matters to this audience — benign milligram replacement vs gram-scale emergency harms — is carried in the at-a-glance and in both gram-scale-only contraindications. |
| 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 “anti-aging” phrasing; the speculative benefit is framed as “attenuation of cellular ageing processes”, matching the ER. |
| 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)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt. | 🟢 | Uses “intramuscularly”, “injection”, “oral or sublingual”, “intravenous dosing” — no lay route-of-administration phrasing on any surface including the lede. |
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 verified verbatim against [qrs_template]: Protocol, Time to effect, Benefits, Risk & Side Effects, Monitoring, Qualitative Assessment, Contraindications, Key Interactions, the four tier labels and Marker/Target/Why. |
| 3.2 | All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. | 🟢 | All 38 template spans present; marker_#* and qualitative_item# are correctly expanded to marker_1..10_* and qualitative_item_1..7. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Diff against [qrs_template] shows changes confined to variable content plus the tooling frontmatter keys; no structural, CSS or non-variable text was altered. |
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 source section has 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. | 🟢 | Bold labels carried verbatim: “Nitrous oxide (anaesthetic and recreational)”, “Metformin”, “Colchicine and aminosalicylic acid”, “Chloramphenicol”, “High-dose vitamin C supplements”, “Folic acid supplements”, “Supplements with additive homocysteine-lowering effects”, “Potassium-lowering agents (hydrochlorothiazide, furosemide, indapamide)”, “Haemodialysis and blood-leak detectors”; protocol labels likewise. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | The only trimmed label is the PPI/H2 gloss, where the example drug list mandated by 9.5 is kept and only the explanatory phrase is dropped. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji codepoints anywhere in the file; the ER’s 🟩/🟥/🟨 tier markers are conveyed by the CSS tier labels. |
| 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 at minimum viable phrasing; the completeness mandated by 9.2, 14.2 and 15.2 is delivered without any elaboration that could be cut further. |
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 is the first element after <!doctype html>, ahead of the “QRS (Quick Reference Sheet)” comment at 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 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. | 🟢 | Entirely inside an HTML comment; no element on the sheet echoes 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. | 🟢 | All values trimmed; only duration: “00:03” is quoted, which its colon requires. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: hydroxocobalamin_2026-0911-0002_Opus_ER.md, matching the source ER. |
| 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 version badge of [qrs_prompt]. |
| 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-0911-0207 — correct 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]” | 🟢 | 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 the session’s “(1M context)” qualifier correctly stripped. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9: qrs_filename: hydroxocobalamin_2026-0911-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 — no stray whitespace or unnecessary quoting in any of the nine keys. |
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: “Hydroxocobalamin for Health & Longevity - Quick Reference Sheet” — canonical_topic with & encoded, plus the required suffix. |
| 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: “Hydroxocobalamin for Health & Longevity”, entity-encoded. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: 09/11/2026, the MM/DD/YYYY rendering of qrs_creation_date 2026-0911-0207. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Line 425: “Opus 5”, 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 title and the template subline; the ER’s “Also known as” line, badges and audit stamps are absent. |
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 four paragraphs of the ER Conclusion — what it is, what the strongest evidence covers, what is unproven, how harms scale with dose. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 55 words, within the 60-word ceiling. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause traces to a distinct Conclusion passage (ER lines 482, 484 and 486). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Homocysteine is rendered as “the marker that rises when the vitamin is lacking”; only “vitamin B12” appears, which is general vocabulary rather than a specialist acronym. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No study names, years or sample sizes. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes, confidence intervals or risk ratios; “Strongest evidence” is a qualitative ranking only. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Sourced from the ER’s “Populations who should avoid hydroxocobalamin” list inside Key Interactions & Contraindications (ER lines 327-332). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All four ER avoid-populations are present and none is invented. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Four discrete <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. | 🟢 | Trailing rationale stripped — e.g. the ER’s “, given the predictable blood-pressure-raising effect” is dropped from the hypertension item. No dash-introduced 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). | 🟢 | Thresholds and scope qualifiers preserved: eGFR below 30 mL/min/1.73 m², above 160/100 mmHg, “until controlled”, and the “gram-scale intravenous dosing only” restriction on both dose-specific items. |
| 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 four avoid-populations, so leaving it non-empty is correct. |
| 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 |
🟢 | Sourced from the ER Key Interactions & Contraindications bullets (ER lines 307-325). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All ten ER interaction bullets are represented, and none duplicates a contraindication. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Ten discrete <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. | 🟢 | Mechanism and mitigation sentences are stripped throughout — e.g. metformin reduces to “caution and monitoring”, folic acid to “caution”. No dash-introduced trailing clauses. |
| 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 and time windows preserved: (anaesthetic and recreational), (omeprazole, esomeprazole, famotidine), (hydrochlorothiazide, furosemide, indapamide), “during the first week of treating severe anaemia”, and the full folate/B6/riboflavin/betaine/creatine list. |
| 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, so leaving it non-empty is correct. |
| 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 |
🟢 | Drawn from the ER Therapeutic Protocol section (ER lines 354-358). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Loading regimen, maintenance interval and the oral high-dose alternative are the three actionable bullets; the remaining ER bullets are background (half-life, who popularised, best time of day) rather than implementation steps. |
| 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, 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 fields carry ER-derived content, e.g. action_1_value “1 mg intramuscularly, three times weekly for two weeks” from ER line 354. |
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 counts, homocysteine and nerve symptoms are the three time-to-effect aspects tied to named ER benefits. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by benefit tier: blood-count correction and homocysteine lowering are both High-tier benefits, nerve recovery sits below them. Fatigue/mood was correctly passed over as it maps to no graded ER benefit. |
| 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 in the ER. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time fields populated from the ER: 6-8 weeks and the 3-7 day reticulocyte rise (ER lines 159, 411); the 12-week duration and >500 µg dose threshold for homocysteine (ER line 165); 3-6 months and the >1 year caveat (ER line 411). |
| 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 eight items map one-to-one onto the ER Expected Benefits headings. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four tier spans 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. | 🟢 | Reduced to the ER heading text alone — no magnitudes, mechanisms or study references carried across. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | The ER’s parenthetical glosses (e.g. “young red blood cell”, “RCTs”) are absent; the only parenthesis is the ER’s own conflicted-evidence marker, which 1.2 requires be preserved. |
| 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 tiers have items in the ER, 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 nine items map one-to-one onto the ER Potential Risks & Side Effects headings. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four tier spans 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. | 🟢 | Reduced to the ER heading text alone — no odds ratios, percentages, dose contexts or mechanisms carried across. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | The ER’s parenthetical glosses (e.g. “red-coloured urine”, “low blood potassium”) are absent; the only parenthesis is the ER’s own conflicted-evidence marker, which 1.2 requires be preserved. |
| 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 tiers have items in the ER, so no span needed hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from the ER Monitoring Protocol & Defining Success section. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All ten rows of the ER biomarker table are present, with names, optimal ranges and rationale 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. |
🟢 | Populated from ER line 439 — baseline before first dose, potassium and CBC at 1 week, MMA/homocysteine/CBC at 8 weeks, full panel every 6-12 months. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from the ER Monitoring Protocol & Defining Success section. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All seven of the ER’s qualitative markers (ER lines 456-462) are present and verbatim. |
Issues 11/09/2026 02:14
Pass rate 100.00%. No issues found.