Audit: QRS - Magnesium Bisglycinate for Health & Longevity
Audit conducted on 23/08/2026 06:44 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. | 🟢 | Dose range 200–400 mg/day, 10–14% elemental, 250 mg sleep trial, 8–12 weeks, all nine biomarker targets and the cadence all trace to ER lines 376–384, 425 and 453–463. |
| 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. | 🟢 | At-A-Glance keeps the ER’s hedge (“though thinly evidenced”) mirroring ER line 497; Speculative tiers retained for both benefits and risks. |
| 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”). | 🟢 | Contraindications and interactions carry the ER’s severity unchanged; benefit tiers match the ER’s own tier assignment. |
| 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 modifying factors were promoted into either 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, NCT identifiers, author names or brand names appear anywhere in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | Only unattributed references such as “the sleep trials” and “the trial literature”, both present in ER lines 376 and 382. |
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. | 🟢 | Sober, deflationary register matching the ER conclusion, including the diet-versus-capsule distinction. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Quantified targets and ranges throughout, framed neutrally without alarm or promotion. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Descriptive constructions (“where the trial literature clusters”, “As used in the sleep trials”) rather than directives. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No imperatives; protocol cells report what trials used rather than instructing. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No instance of recommend/advise/should in the QRS body. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person pronouns anywhere in the document. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Technical terms retained only where the ER heading requires them (hypermagnesemia, eGFR); no gratuitous jargon added. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate and tier items are noun phrases; monitoring “Why” cells are single clauses. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed: no “you”/”your” in the source. |
| 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. | 🟢 | Optimal functional ranges (serum magnesium 0.85–0.95 mmol/L, HbA1c ≤5.4%) rather than conventional reference cutoffs. |
| 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. | 🟢 | Nine-biomarker panel, home blood pressure baseline and seven qualitative trackers assume a willing, effortful reader. |
| 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. | 🟢 | Red blood cell magnesium and parathyroid hormone testing are beyond general-population expectations. |
| 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. | 🟢 | At-A-Glance states the key differential explicitly: “in adults eating well, the same doses move very little”. |
| 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. | 🟢 | “Longevity” in the title; the phrase “anti-aging” does not occur. |
| 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. | 🟢 | Terms used (“blood sugar”, “capsules”) are the ER’s own register at ER lines 168 and 499. |
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 twelve fixed strings byte-identical to the template, including the template’s own unescaped “Risk & Side Effects” at line 610. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | 68 spans present = 38 template spans with marker_#* expanded to nine rows (+24) and qualitative_item# to seven items (+6). |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | The three non-variable spans (website=”evidence_review”, website=”audit”, website=”full_review”) and the entire head/CSS block are unchanged from the template. |
4. Formatting
| # | Description | Result | Comments |
|---|---|---|---|
| 4.1 | When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied” | N/A | No source ER section that feeds the QRS is empty. |
| 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. | 🟢 | “Standard dose range”, “Reading the label correctly” and “Timing” match the ER Protocol bold labels at ER lines 376, 378 and 382. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | All nine marker names match the ER table verbatim; Time-to-Effect labels are lifted phrases from ER line 425. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji present; the ER’s “⚠️ Conflicted” markers were correctly stripped. |
| 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 to its minimum form — tier lines are single sentences, gate items are noun phrases, monitoring “Why” cells are single clauses, and the cadence is one sentence. |
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; nothing precedes it but the doctype at line 1. |
| 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 “QRS — Metadata” preamble precedes the opener. |
| 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 repeated in the header, footer or body. |
| 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: "00:03" is quoted, correctly so because the value contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | Line 4: er_filename: magnesium_bisglycinate_2026-0823-0441_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]” | 🟢 | Line 5: qrs_prompt_version: 26.7.02, matching 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-0823-0628. |
| 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” — 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) | 🟢 | “Opus 5” — nickname plus version, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | Line 9 matches the file on disk: magnesium_bisglycinate_2026-0823-0441_Opus_QRS.html. |
| 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. | 🟢 | All nine keys carry single-space-delimited, untrimmed-free values; quoting used only where YAML requires it. |
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: “Magnesium Bisglycinate 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 &) |
🟢 | Line 417: “Magnesium Bisglycinate for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | Line 421: “08/23/2026” from qrs_creation_date 2026-0823-0628. |
| 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. | 🟢 | Header contains only the title and the template’s stock subline; the ER’s “Also known as” line was not carried over. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Compresses all three conclusion paragraphs (ER lines 497–499): tolerability rationale, who actually responds, and the diet-versus-capsule signal. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 58 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Glycine binding and bowel tolerance → ER 497; responder profile → ER 499; magnesium-rich food and mortality → ER 499. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms; “blood sugar” used rather than glycaemic control, “living longer” rather than all-cause mortality. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial name, year, sample size or p-value appears. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No numeric effect estimate or confidence interval appears. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Sourced from the “Populations who should avoid Magnesium Bisglycinate” list at ER lines 350–354. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All five ER avoid-list entries are present, in ER order. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Five discrete <li> elements at lines 573–583. |
| 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. | 🟢 | The ER’s mechanistic tail on myasthenia gravis (“where raised magnesium worsens muscle weakness”) is correctly stripped; no dashes carry trailing clauses. |
| 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). | 🟢 | “stage 4 or worse (eGFR below 30 mL/min/1.73 m²)”, “below 50 beats per minute” and “without cardiology oversight” are all retained. |
| 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 its contraindication list. |
| 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 five such populations, and the section is correctly populated rather than 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 |
🟢 | All ten items map one-to-one onto the ER interaction bullets at lines 328–346. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | All ten ER interactions present; none duplicates an entry in the Contraindications gate. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Ten discrete <li> elements at lines 591–600. |
| 9.4 | Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact. | 🟢 | The ER’s Caution/Monitor/Additive labels, mechanisms, mitigations and the Gommers et al. citation are all stripped; no trailing dash clauses remain. |
| 9.5 | Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept as concise as possible (shortened or trimmed where needed to fit the one-page budget, but never dropped entirely). | 🟢 | Every ER bullet carrying a drug list keeps a representative parenthetical (e.g. “(ciprofloxacin, doxycycline)”, “(spironolactone, amiloride)”, “(omeprazole, pantoprazole)”) — trimmed for the page budget, never dropped. |
| 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 its interaction list. |
| 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 ten such interactions, and the section is correctly populated rather than empty. |
| 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 |
🟢 | All three cells trace to the ER Therapeutic Protocol bullets at lines 376, 378 and 382. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Dose range, elemental-versus-compound label reading (the ER’s “most frequent error”, line 427) and timing are the three decision-critical bullets. |
| 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 Protocol section contains ten actionable bullets, well above three. |
| 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 variables carry ER-derived content; no placeholder remains. |
11. Time to Effect
| # | Description | Result | Comments |
|---|---|---|---|
| 11.1 | The three sets of [time] items cover the three most important time-to-effect aspects from the ER | 🟢 | Blood pressure and glucose, sleep, and tissue repletion — exactly the three horizons given at ER line 425. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Blood pressure and glucose (High tier, the ER’s “best-quantified benefit”, line 463) first, sleep (High tier) second, repletion (Medium tier) 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 | The ER supplies three distinct time-to-effect horizons. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time variables populated; subs trace to ER lines 425 and 451. |
| 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 provides time-to-effect information at line 425. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | All fourteen items map to ER benefit headings at lines 158–242. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four spans present and populated at lines 540–563. |
| 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 bare ER headings; no magnitude, mechanism or author name carried over. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any benefits tier. |
| 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 ER benefit tiers contain items, 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 seven items map to ER risk headings at lines 266–308. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four spans present and populated at lines 612–629. |
| 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. | 🟢 | Bare ER headings only; the 11–37% event rates, risk ratio and Epworth figures are all omitted. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheses appear in any risks tier; the ER’s “(dangerously high blood magnesium)” gloss 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 ER risk tiers contain items, so no span needed hiding. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Table and cadence both drawn from the ER Monitoring Protocol & Defining Success section at lines 451–463. |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All nine ER biomarker rows present with matching optimal ranges, in ER order. |
| 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. |
🟢 | Lines 764–768 carry both the 8–12 week / 6–12 month schedule and the earlier-checkpoint exception from ER line 451. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Sourced from the qualitative marker list at ER lines 467–473. |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All seven ER qualitative markers present, in ER order. |
Issues 23/08/2026 06:44
Pass rate 100.00%. No issues found.
Issues 23/08/2026 06:36
- 2.8 — Redundant time-to-effect sub-lines:
time_1_sub“Changes emerged over 8–12 weeks in the trials.” (line 503) andtime_2_sub“Sleep and bowel effects appear within days.” (line 514) merely restatetime_1_value“8–12 weeks” andtime_2_value“Within days”, adding no information while consuming one-page budget.
Fixes 23/08/2026 06:36
- 2.8 — Redundant time-to-effect sub-lines: Replaced
time_1_sub“Changes emerged over 8–12 weeks in the trials.” with “The two outcomes with the clearest quantified response; both need a pre-start baseline.” andtime_2_sub“Sleep and bowel effects appear within days.” with “Bowel effects appear on the same timescale.”, so neither sub-line restates its own value cell.