Audit: QRS - Betaine for Health & Longevity

Audit conducted on 11/09/2026 06:46 using AI4L / Opus 5

Iterations

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 populated span against the ER: protocol values (ER 306/316/320), time-to-effect (ER 356), benefits/risks headings (ER 142-242), gates (ER 260-286), monitoring table (ER 384-391), qualitative markers (ER 395-401). 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 over: “No circadian dependence demonstrated” (ER 316), “pairing untested” (ER 274), “No established target” for TMAO (ER 391).
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”). 🟢 Contraindication thresholds preserved unchanged (methionine >1,000 umol/L; LDL >160 mg/dL; 4 g daily or more). Pregnancy and lactation carried as an avoid item, not softened.
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 come only from Expected Benefits, risks only from Potential Risks & Side Effects, gates only from Key Interactions & Contraindications. No Benefit- or Risk-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 PubMed IDs, NCT identifiers, author names, or brand names anywhere in the QRS; the only URL is the template’s AI4L link (line 424).
1.6 The QRS does not introduce new attributions. 🟢 No attributions introduced.

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, trade-off-forward 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 while remaining readable; tiers and targets give the reader something to act on.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Presents findings and ranges; issues no directives.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 Monitoring cadence is stated descriptively (“lipid recheck at 6 to 8 weeks”), not as an instruction to the reader.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommend”, “advise”, or “should” in the document’s own voice.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the file.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Plain language throughout; technical terms appear only where they are the decision gate itself (e.g. cystathionine beta-synthase deficiency, trimethylaminuria).
2.8 Information is presented in a concise and very compact manner 🟢 Every gate, benefit, and risk item is a single condensed clause.
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 assumes a proactive reader weighing the homocysteine benefit against the lipid cost.
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 a monitoring panel of eight markers and a multi-visit cadence without hedging on the effort involved.
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 pitched at the general population.
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 lipid trade-off is surfaced in the lede, the Risks card, the contraindications and the monitoring table — the weighting a risk-aware reader needs.
2.14 The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. 🟢 No occurrence of “anti-aging”; the sheet uses “longevity” (title, at-a-glance).
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. 🟢 No colloquial or consumer-grade terms. “harmful cholesterol” in the at-a-glance is the ER Conclusion’s own wording (ER 419) and is required there by 7.4, which bars the acronym LDL.

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 and unmodified: Protocol (446), Time to effect (490), Benefits (537), Risk & Side Effects (615), Monitoring (640), Qualitative Assessment (768), Contraindications (563), Key Interactions (580), tier labels High/Medium/Low/Speculative, and Marker/Target/Why (644-646).
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 template spans present; marker_#* and qualitative_item# are expanded to 8 and 4 concrete rows respectively.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Structural diff against [qrs_template] shows only span-content substitutions — no markup, CSS, footer, or comment outside a span 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, so no empty-state phrasing is required.
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. 🟢 ER bold labels reused verbatim: “Standard supplemental dose”, “Split versus single dose”, “Best time of day” (ER 306/320/316); “Training performance”, “Digestive tolerance”, “Body odor”, “Energy and recovery” (ER 395-401); all nine interaction labels (ER 260-276).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 No invented labels. Time-to-effect labels (“Strength”, “Homocysteine”, “Lipid increase”) are the ER’s own terms from the Time to effect bullet (ER 356). Interaction parentheticals are trimmed only as 9.4/9.5 require.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No tier emoji in the file; tiers are carried by bold labels and CSS palette.
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: gate and tier items are single clauses, the at-a-glance is at its 60-word budget, and the Monitoring table carries only the ER’s own eight rows with shortened Why text.

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. 🟢 HTML comment opens at line 2, immediately after <!doctype html>, before head and body.
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 delimited by — at lines 3 and 13; the preceding title text is outside the block.
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. 🟢 Inside an HTML comment; 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 is quoted, and “00:02” contains a colon, which YAML requires be quoted.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4: er_filename: betaine_2026-0911-0304_Opus_ER.md — matches 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 — matches 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-0911-0614 — 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) 🟢 Single word, no version.
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) 🟢 Nickname plus version number, no qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9: qrs_filename: betaine_2026-0911-0304_Opus_QRS.html — matches 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. 🟢 Confirmed again against the full block: no stray whitespace or unnecessary quoting.

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., &amp; for &) 🟢 Line 22: “Betaine for Health & Longevity - Quick Reference Sheet” — canonical_topic entity-encoded plus the fixed suffix.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Line 417: “Betaine for Health & Longevity”.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 Line 421: 09/11/2026 — qrs_creation_date 2026-0911-0614 in MM/DD/YYYY.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 Line 425: Opus 5.
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Subline carries only the template’s date, source-ER link, AI4L link and model. No AKA line, despite the ER carrying six alternate names.

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’s first two paragraphs (ER 419-421) into the methyl-donor job, the lipid consequence, the two narrow benefit signals, and the animal basis of the longevity claim.
7.2 [at_a_glance] is no longer than 60 words 🟢 58 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 maps to a distinct Conclusion passage: methyl groups and the cholesterol trade-off to ER 419; strength and liver fat to ER 421; aged mice to ER 421.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 No acronyms. “methyl groups” is glossed as “small chemical tags”, homocysteine as “the blood marker”, and LDL is rendered as “harmful cholesterol”.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, or sample sizes.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes or statistics; “consistently” is qualitative.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Drawn from the ER’s “Populations who should avoid Betaine” list (ER 278-286) inside Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 All four ER avoid-populations represented, none added.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Four <li> elements inside the [stop_items] span (lines 566-575).
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 explanations stripped: the em-dash clause “— the setting in which brain swelling has occurred” (ER 280) and “in which any added trimethylamine load worsens symptoms” (ER 284) are gone.
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 dose qualifiers preserved: methionine above 1,000 µmol/L, LDL above 160 mg/dL, 4 g daily or more, and the “(fish-odor syndrome from FMO3 deficiency)” parenthetical.
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 ER names four avoid-populations, so 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. 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 🟢 Drawn from the ER’s nine interaction bullets (ER 260-276).
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All nine interactions carried; none duplicates a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Nine <li> elements inside the [caution_items] span (lines 583-605).
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. 🟢 Each item reduced to label plus the key consequence (“additive and intended”, “opposed in outcome”, “pairing untested”); severity ratings and mechanistic sentences dropped.
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 preserved in every case — atorvastatin, ezetimibe, methotrexate, trimethoprim, omeprazole, nicotinic acid, nicotinamide mononucleotide and riboside, folic acid, B12, B6 — with only the mechanistic gloss trimmed, as 9.4 requires and 9.5 permits.
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 ER names nine interactions, so the section is correctly populated.
9.8 If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Derived from the ER Therapeutic Protocol section (ER 304-330).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose, dose splitting, and timing — the three aspects a reader must settle before starting, and the three the ER treats as primary.
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 names thirteen protocol 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 populated from ER 306, 320 and 316; values and subs match the ER’s figures (2–3 g daily, 1.25–3 g twice daily, no circadian dependence).

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 🟢 Strength, homocysteine, and the lipid increase — the only three time-to-effect aspects the ER quantifies (ER 356).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered Strength (High-tier benefit) then Homocysteine (Low-tier benefit), with the lipid increase — which has no associated benefit — last.
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, 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 fields populated; the plateau note in time_2_sub is supported by ER 318.
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 🟢 Derived from the ER Expected Benefits section (ER 136-186).
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four tier spans present and populated (lines 539-556).
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 reduced to the ER’s own benefit headings; magnitudes, mechanisms and trial counts dropped.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical content carried; the ER’s ⚠️ Conflicted markers on liver fat, body fat and cognition are also dropped, as the tier already encodes evidence strength.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four tiers carry items in the ER, so no span needs hiding.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Derived from the ER Potential Risks & Side Effects section (ER 204-242).
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four tier spans present and populated (lines 617-634).
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 reduced to the ER’s own risk headings; the 35 percent GI rate, the TMAO figures and the case-report counts are all dropped.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 The “(Brain Swelling)” parenthetical from the ER’s cerebral edema heading (ER 232) is stripped.
13.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. N/A All four tiers carry items in the ER, so no span needs hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Derived from the ER Monitoring Protocol & Defining Success section (ER 376-391).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All eight ER biomarker rows present in order: homocysteine, LDL, total cholesterol and triglycerides, ALT, plasma methionine, eGFR, B12 and folate, TMAO.
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 380: baseline panel, lipid recheck at 6 to 8 weeks, homocysteine at 12 weeks, then annual, returning to 8 weeks after a dose change.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Derived from the qualitative-marker list at the end of the ER Monitoring section (ER 393-401).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All four present: training performance, digestive tolerance, body odor, energy and recovery.

Issues 11/09/2026 06:46

Pass rate 100.00%. No issues found.

Issues 11/09/2026 06:39

  1. 1.2 — Circadian hedge dropped: [action_3_value] at line 480 reads “No circadian dependence”, while the ER (line 316) states “no circadian dependence has been demonstrated”; the QRS turns an absence of evidence into a positive negative claim.

Fixes 11/09/2026 06:39

  1. 1.2 — Circadian hedge restored: [action_3_value] changed from “No circadian dependence” to “No circadian dependence demonstrated”, matching the ER’s hedged phrasing “no circadian dependence has been demonstrated”.

Issues 11/09/2026 06:33

  1. 1.3 — Methionine monitoring condition dropped: marker_5_why (QRS line 709) reads “needed only above 6 g daily”, while the ER Monitoring table (ER line 388) states “Needed only above 6 g daily or in inherited metabolic disease”; dropping the second condition strengthens the exclusion and removes the inherited-disease case the ER flags.

Fixes 11/09/2026 06:33

  1. 1.3 — Methionine monitoring condition restored: marker_5_why now reads “Accumulation precedes brain swelling; needed only above 6 g daily or in inherited metabolic disease”, restoring the second condition from the ER Monitoring table.

Issues 11/09/2026 06:26

  1. 2.6 / 2.9 — Dangling possessor in TMAO target: [marker_8_target] at line 743 reads “track the change from own baseline”, whereas the ER writes “track the change from the individual’s own baseline”; the truncation leaves “own” without a possessor and reads as an implied second-person “your own baseline”.

Fixes 11/09/2026 06:26

  1. 2.6 / 2.9 — Dangling possessor in TMAO target: [marker_8_target] changed from “track the change from own baseline” to “track the change from the individual’s own baseline”, restoring the ER’s third-person phrasing and removing the implied second-person address.

Issues 11/09/2026 06:19

  1. 1.1 — Plateau misattributed to homocysteine: time_2_sub (QRS line 516) states “plasma concentrations plateau after about a week” under the “Homocysteine” label, but the ER attributes that one-week plateau to betaine plasma concentrations (ER line 318), not to homocysteine.

Fixes 11/09/2026 06:19

  1. 1.1 — Plateau misattributed to homocysteine: Changed time_2_sub from “plasma concentrations plateau after about a week” to “betaine plasma concentrations plateau after about a week”, so the one-week plateau is attributed to betaine as in the ER rather than to homocysteine.