Audit: QRS - L-Lysinate for Health & Longevity
Audit conducted on 11/07/2026 22:55 using AI4L + evidence-mcp / Opus 5.5
Summary
| Items | Count |
|---|---|
| Total | 97 |
| Passed | 86 |
| Failed | 0 |
| N/A | 11 |
| Pass Rate | 100.00% |
- Total = Passed + Failed + N/A
- Pass Rate = Passed / (Passed + Failed) × 100
- N/A items are excluded from the pass rate calculation
1. General Rules
| # | Description | Result | Comments |
|---|---|---|---|
| 1.1 | Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER. | 🟢 | Every QRS statement traces to the ER: lede to Motivation/Conclusion, Protocol to Therapeutic Protocol, Time to effect to Practical Considerations/Discontinuation, tiers and gates to their ER sections, Monitoring to the ER table and cadence 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 phrasing kept: lede “appears well tolerated”, “main open safety question”; action_2_sub “Proposed”; cadence “follow common practice rather than trial protocols”; time_2_sub “appears tied to ongoing use”. |
| 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 found; contraindications and interactions keep ER scope qualifiers (e.g., “(aspirin lysinate)”). |
| 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 only from “Populations who should avoid L-Lysinate”; interactions from the two interaction groups; modifying factors are not surfaced. |
| 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, citations, expert names, NCT IDs or brand names (e.g., NeoProfen, Kardégic) 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. | 🟢 | |
| 2.2 | The tone of the QRS is expert, accessible, objective, and data-driven | 🟢 | |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | “Safety check: a rise stops use” carries the ER table’s own wording impersonally. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | |
| 2.6 | The QRS never addresses the reader directly — it presents evidence, not guidance | 🟢 | No second-person address found. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms appear only inside ER labels/headings carried verbatim (e.g., “Pyridoxine-dependent epilepsy (ALDH7A1 deficiency)”). |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Long Low-risk tier is required content (17 ER items). |
| 2.9 | 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. | 🟢 | |
| 2.10 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | |
| 2.11 | 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. | 🟢 | |
| 2.12 | 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. | 🟢 | Lede closes with “for health-focused adults, expected gains are modest and uncertain”, per ER Conclusion. |
| 2.13 | 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” wording. |
| 2.14 | 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 terms (pill, shot, taken by mouth) found. |
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, gate headings, tier labels and Marker/Target/Why headers match the template. |
| 3.2 | Every element carrying a data-qrs-var attribute in [qrs_template] is present in the QRS with the same name | 🟢 | All template data-qrs-var names present; marker_# and qualitative_item_# expanded to 1..7 and 1..4 per 14.2/15.2. |
| 3.3 | Everything outside the data-qrs-var spans — markup, text, styles, comments — is as in the template; spans that no checklist item addresses are left unchanged as well | 🟢 | Diff against template shows changes only inside data-qrs-var spans, the sanctioned style=”display:none” on benefits_medium, and filled metadata (plus pipeline keys duration/git_user/git_issue). |
4. Formatting
| # | Description | Result | Comments |
|---|---|---|---|
| 4.1 | An empty ER section never produces visible empty-state text in the QRS: the corresponding region is hidden or left empty. Phrases such as “None documented in human trials to date” or “Not formally studied” appear only where the ER uses them for a fact the QRS carries over. | 🟢 | No empty-state phrasing; empty Medium benefits tier hidden; “Not specified in the ER” used only as 14.3 requires. |
| 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. | 🟢 | Gate and Protocol labels use the ER bold labels verbatim (glosses dropped, example lists trimmed). |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Example-list trims keep at least one ER example in ER wording (e.g., “(calcium carbonate)”, “(gentamicin, amikacin)”). |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji in the QRS. |
| 4.5 | The QRS is designed to render on one A4 page. It fails this item only for one of four things: a trailing clause after a dash, an optional gloss, an example list left untrimmed, or a repetition. Nothing else is cut to fit. | 🟢 | No trailing dash clauses, optional glosses, untrimmed example lists or repetitions found. |
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. | 🟢 | Metadata comment on line 2, directly after <!doctype html>. |
| 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. | 🟢 | |
| 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. | 🟢 | |
| 5.4 | All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting. | 🟢 | Only duration is quoted (“00:02”, contains a colon). |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: l_lysinate_2026-1107-1143_Opus_ER.md |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | qrs_prompt_version: 26.11.7 matches 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-1107-2233 |
| 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 |
| 5.9 | The nickname of the AI is the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT); when the full name has no version number or is “Unknown”, the nickname equals the full name | 🟢 | |
| 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.5 |
| 5.11 | The full name of the AI consists of the model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y), the model name alone when the system prompt or developer instructions name a model without a version number (e.g., Grok), or “Unknown” when neither the system prompt nor the developer instructions of the creating model name a model | 🟢 | |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename matches the file name. |
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 &) |
🟢 | “L-Lysinate for Health & Longevity - Quick Reference Sheet” |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | “L-Lysinate for Health & Longevity” |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 11/07/2026 matches qrs_creation_date 2026-1107-2233. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Opus 5.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. | 🟢 | Header holds only template elements. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence | 🟢 | Opens “L-lysinate is a salt of lysine … found in mineral supplements and some pain relievers, of interest for cold sores, stress and calcium uptake” before any verdict. |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses the ER Conclusion’s four paragraphs. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | 70 words (script count). |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each fact maps to an ER Motivation or Conclusion passage. |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms or specialist terms. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | “Up to about six grams daily” is a dose, not a statistical result. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All 7 ER “Populations who should avoid” items present. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | |
| 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. | 🟢 | Items reduced to ER labels; rationale and attributions stripped; item 7 keeps its qualifier list. |
| 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). | 🟢 | “(ALDH7A1 deficiency)”, “(aspirin lysinate)”, “below 30 mL/min”, “beyond 24 weeks at doses above 100 mg/day” preserved. |
| 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 | ER uses no ranking notation in the contraindications. |
| 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. |
🟢 | ER names populations to avoid; section is populated. |
| 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 | Section is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | |
| 9.2 | [caution_items] represent the ER’s documented interactions — the items under its “Documented interactions:” label — excluding any that are already listed as Contraindications and any entry phrased as no interaction found | 🟢 | 8 documented items; the two “No interaction found” entries (levodopa; oral anticoagulants with ibuprofen lysinate or lysine clonixinate) correctly excluded. |
| 9.3 | [caution_theoretical_items] represent the ER’s theoretical interactions — the items under its “Theoretical interactions (inferred from mechanism, not studied in humans):” label | 🟢 | All 7 ER theoretical items present. |
| 9.4 | The ER placeholder “None identified” is never an item: it means that group is empty | 🟢 | |
| 9.5 | Individual [caution_items] and [caution_theoretical_items] are formatted as <li></li>. The template’s bold “Theoretical (inferred from mechanism)” sub-heading is the only marker of the second list’s status: no item carries “(theoretical)”, “inferred from” or a mechanism clause | 🟢 | No item carries “(theoretical)”, “inferred from” or a mechanism clause. |
| 9.6 | 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. | 🟢 | Items carry label plus the ER Consequence only. |
| 9.7 | 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 trimmed but kept (e.g., “(warfarin; methotrexate above 20 mg/week)”, “(clopidogrel; enoxaparin; sertraline)”). |
| 9.8 | 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 | ER uses no ranking notation in the interactions. |
| 9.9 | If the ER’s theoretical group is empty, the whole Theoretical block — the caution_theoretical span with its sub-heading and list — is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | ER theoretical group is not empty. |
| 9.10 | 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. |
🟢 | ER documents interactions; section is populated. |
| 9.11 | 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, and the Theoretical block is hidden per 9.9. E.g. | N/A | Section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Therapeutic Protocol section |
🟢 | |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from that section | 🟢 | Cold-sore prevention dose, Upper bound, Mineral and drug lysinates. |
| 10.3 | If fewer than three distinct actionable implementation aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | ER has more than three actionable aspects. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from that section. | 🟢 |
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 | 🟢 | Pain relief, cold sores, anxiety from ER Practical Considerations “Time to effect”. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Pain relief (High benefit) first, then cold sores and anxiety (Low, in ER order). |
| 11.3 | If fewer than three distinct time-to-effect aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | ER gives three time-to-effect aspects. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | |
| 11.5 | If the ER provides no information on time to effect at all, the whole Time to effect block (its subhead and all three sets) is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | ER provides time-to-effect information. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | |
| 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. | 🟢 | Items are the ER headings, lower-cased, without flags or qualifiers. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical content; “lipoprotein(a)” is a name. |
| 12.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
🟢 | Empty Medium tier hidden with style=”display:none”. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | |
| 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. | 🟢 | Items are the ER headings, lower-cased; all 1/2/17/3 ER items per tier present. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | |
| 13.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
N/A | Every risk tier has items. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | |
| 14.2 | All measurable/quantifiable biomarkers from that section are listed, one table row per marker; the template’s # row is the pattern, repeated with # replaced by 1, 2, 3 … in the data-qrs-var names |
🟢 | Four ER table markers plus eGFR, albumin and fasting glucose named in the section, rows numbered 1-7. |
| 14.3 | [marker_#name] is the marker, [marker#target] its target value or range as given in the ER, [marker#_why] its purpose in a few words; a target the ER does not give is written “Not specified in the ER” | 🟢 | Targets from the ER table; “Not specified in the ER” for eGFR, albumin, fasting glucose. |
| 14.4 | [monitoring_cadence] is populated with the monitoring cadence/frequency derived from that section. It is not left with placeholder text or empty. | 🟢 | Cadence condensed from the ER baseline and ongoing-monitoring paragraphs. |
| 14.5 | If the ER names no measurable biomarker, the table is hidden with style="display:none" and the single # row is left as in the template |
N/A | ER names measurable biomarkers. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | |
| 15.2 | All subjective/qualitative markers from that section are listed, one <li> per marker; the template’s # item is the pattern, repeated with # replaced by 1, 2, 3 … |
🟢 | All 4 ER qualitative markers, verbatim, numbered 1-4. |
| 15.3 | If the ER names no qualitative marker, the card’s list is hidden with style="display:none" and the single # item is left as in the template |
N/A | ER names qualitative markers. |
Issues 11/07/2026 22:55
Pass rate 100.00%. No issues found.
Issues 11/07/2026 22:50
- 1.1 / 7.4 — Lede overstates lysine uses: At a Glance (line 439) says L-lysinate is “used for cold sores, stress and calcium uptake”, while the ER Motivation says lysine has only “drawn interest for stress and anxiety and for calcium uptake”.
- 14.2 — Monitoring biomarkers missing: The Monitoring table (lines 625-668) omits estimated glomerular filtration rate, serum albumin and fasting glucose, all named as measurements in the ER Monitoring Protocol section.
Fixes 11/07/2026 22:50
- 1.1 / 7.4 — Lede overstates lysine uses: Changed “some fast-acting pain relievers, used for cold sores, stress and calcium uptake” to “some pain relievers, of interest for cold sores, stress and calcium uptake”, matching the ER Motivation; the lede stays at 70 words.
- 14.2 — Monitoring biomarkers missing: Added Monitoring rows 5-7 for estimated glomerular filtration rate (eGFR), serum albumin and fasting glucose, each with target “Not specified in the ER” and its ER pairing as the purpose.
Issues 11/07/2026 22:48
- 4.5 — Example lists left untrimmed: The sheet exceeds one A4 page, yet the documented-interaction labels at line 562 “(calcium carbonate, calcium citrate)” and line 569 “(ibuprofen, naproxen; calcium carbonate)” keep the ER’s full example lists instead of one example per class.
Fixes 11/07/2026 22:48
- 4.5 — Trimmed interaction example lists: Shortened “(calcium carbonate, calcium citrate)” to “(calcium carbonate)” at line 562 and “(ibuprofen, naproxen; calcium carbonate)” to “(ibuprofen; calcium carbonate)” at line 569, keeping one ER example per class.
Issues 11/07/2026 22:42
- 2.12 — Lede drops audience scope: The at-a-glance takeaway at line 439, “expected gains are modest and uncertain”, omits the ER Conclusion’s qualifier “for a well-nourished, health-focused adult”, generalizing an audience-specific weighting.
Fixes 11/07/2026 22:42
- 2.12 — Lede audience scope restored: Changed “expected gains are modest and uncertain” to “for health-focused adults, expected gains are modest and uncertain”; trimmed “form”, “mainly” and “the body” → “humans” to stay at 70 words.
Issues 11/07/2026 22:39
- 4.5 — Optional gloss, untrimmed list: action_2_sub (line 467) keeps the optional gloss “(highest dose without observed harm)”, and the theoretical mineral-supplement item (line 585) keeps the untrimmed example list “(zinc, magnesium, calcium)”, whose “calcium” repeats the documented calcium interaction at line 562.
Fixes 11/07/2026 22:39
- 4.5 — Optional gloss, untrimmed list: Replaced action_2_sub “Proposed no-observed-adverse-effect level (highest dose without observed harm), industry-linked” with “Proposed highest dose without observed harm, industry-linked”; trimmed the theoretical mineral-supplement examples from “(zinc, magnesium, calcium)” to “(zinc, magnesium)”.
Issues 11/07/2026 22:35
- 1.1 / 7.4 — Overgeneralized lede evidence claim: At a Glance (line 439) says “other signals come from small, indirect studies”, but the ER Conclusion names only the stress, calcium-uptake and blood-sugar signals; the High-tier drug-lysinate pain relief rests on placebo-controlled lysinate trials.
- 1.2 / 1.3 — Cautious qualifiers dropped: The lede turns the ER’s “often indirect” into “indirect” (line 439), and action_2_sub (line 467) drops “proposed” from the industry-linked 6.0 g/day no-observed-adverse-effect level.
- 2.5 — Imperative protocol phrasing: action_1_sub (line 456) opens with “Split two to three times daily”, while the ER says splitting two to three times daily “is common”.
- 4.5 — Repetition and untrimmed lists: time_1_sub (line 495) restates time_1_value “Within 2 hours”; Theoretical interaction labels (lines 579-582) keep full three- and four-example lists while the documented labels were trimmed.
Fixes 11/07/2026 22:35
- 1.1 / 7.4 — Overgeneralized lede evidence claim: Replaced “other signals come from small, indirect studies” with “stress, calcium and blood-sugar signals rest on small, often indirect studies”, matching the signals the ER Conclusion names; tightened wording to keep the lede at 70 words.
- 1.2 / 1.3 — Cautious qualifiers dropped: Restored “often” in the lede and changed action_2_sub to “Proposed no-observed-adverse-effect level (highest dose without observed harm), industry-linked”.
- 2.5 — Imperative protocol phrasing: Changed action_1_sub from “Split two to three times daily” to “Commonly split two to three times daily”.
- 4.5 — Repetition and untrimmed lists: Replaced time_1_sub with “Blood levels peak in about 30 minutes when fasting”; trimmed Theoretical example lists to “gentamicin, amikacin”, “ibuprofen, naproxen”, “metformin, insulin” and “L-arginine, nuts”.