evipedia.ai
← Back to Review

Audit: QRS - Modified Alginate Complex for Health & Longevity

Audit conducted on 28/08/2026 14:01 using AI4L / Opus 5

Iterations

Summary

Items Count
Total 93
Passed 81
Failed 0
N/A 12
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. 🟢  
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. 🟢  
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”). 🟢  
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. 🟢  
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. 🟢  
1.6 The QRS does not introduce new attributions. 🟢  

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 simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢  
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 🟢  
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 🟢  
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢  
2.8 Information is presented in a concise and very compact manner 🟢  
2.9 It DOES NOT address the reader directly 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  
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. 🟢  

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” 🟢  
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢  
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢  

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 relied upon by the QRS is empty; every mapped ER section (Expected Benefits, Potential Risks & Side Effects, Key Interactions & Contraindications, Therapeutic Protocol, Monitoring Protocol & Defining Success) carries 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. 🟢  
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢  
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold 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. 🟢  

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. 🟢  
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. 🟢  
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢  
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢  
5.7 Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430) 🟢  
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢  
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢  
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢  
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) 🟢  
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢  
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. 🟢  

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 &) 🟢  
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢  
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢  
6.4 [header_subline_model] is set to [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. 🟢  

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢  
7.2 [at_a_glance] is no longer than 60 words 🟢  
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢  
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢  
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢  
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢  

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 🟢  
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. 🟢  
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). 🟢  
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’s Key Interactions & Contraindications section uses no ranking notation (no “>” severity ordering) inside parentheses.
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. N/A The section is not left empty; nine contraindications are populated at lines 542-550.
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not left empty, so no empty-state HTML comment is required.

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 Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢  
9.3 Individual [caution_items] are formatted as <li></li> 🟢  
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. 🟢  
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). 🟢  
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’s Key Interactions & Contraindications section uses no ranking notation (no “>” severity ordering) inside parentheses.
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. N/A The section is not left empty; nine key interactions are populated at lines 558-566.
9.8 If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not left empty, so no empty-state HTML comment is required.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢  
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢  
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 Therapeutic Protocol section names three distinct actionable protocols (Binder, Metabolic, Reflux); all three action sets are used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol 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 🟢  
11.2 The sets are picked and ordered by the magnitude of the related 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 The ER names three distinct time-to-effect aspects; all three time sets are used.
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 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 (Practical Considerations, ER line 408), so the section is correctly retained.

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. 🟢  
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢  
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 benefit tiers (High, Medium, Low, Speculative) 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 🟢  
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. 🟢  
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢  
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 risk tiers (High, Medium, Low, Speculative) 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 🟢  
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢  
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. 🟢  

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢  
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢  

Issues 28/08/2026 14:01

Pass rate 100.00%. No issues found.

Issues 28/08/2026 13:53

  1. 4.5 — Sheet overflows one A4 page: The Monitoring table (lines 596–738) and the Key Interactions gate (lines 557–567) carry their ER text over unabridged — twelve verbatim Target cells (line 621 is 96 characters, line 698 is 66) and nine unabridged parenthetical drug lists (line 563 is 121 characters, line 566 is 151) — so the sheet runs onto a second page instead of being condensed to the per-section budget.

Fixes 28/08/2026 13:53

  1. 4.5 — Key Interactions drug lists trimmed: All nine interaction items kept, but the parenthetical example lists were shortened per item 9.5 — e.g. “Other gastrointestinal binders (modified citrus pectin, chlorella, zeolite, bentonite, activated charcoal, cholestyramine)” became “Other binders (modified citrus pectin, activated charcoal, cholestyramine)”, and the potassium item dropped the duplicate second example from each drug class.

  2. 4.5 — Monitoring “Why” column condensed: Ten of the twelve marker_#_why cells were reduced to their essential clause without losing meaning, e.g. “Guards against added potassium load from potassium alginate” to “Added potassium load from potassium alginate” and “Sentinel for fat-soluble vitamin loss from fecal fat” to “Fat-soluble vitamin loss from fecal fat”, collapsing most rows from two rendered lines to one.

  3. 4.5 — Monitoring targets and cadence tightened: marker_2_target was refactored to carry the “g/dL” unit once instead of twice, and monitoring_cadence merged the separate lipid-panel and metal-panel clauses into “lipid and metal panels at 3 months”. All numeric thresholds were preserved.

  4. 4.5 — Contraindication wording shortened: “estimated glomerular filtration rate below 30 mL/min/1.73 m²” became “filtration rate below 30 mL/min/1.73 m²” and “if whole-kelp rather than purified alginate” became “if whole-kelp alginate”, keeping every staging value and salt-form qualifier required by item 8.5.

Note: items 8.2, 9.2, 14.2 and 15.2 require every ER contraindication, interaction, biomarker and qualitative marker to be carried over, so no entries were dropped. The condensation above reduces the overflow but does not on its own resolve the one-page budget for a source ER with 9 contraindications, 9 interactions and 12 biomarkers.

Issues 28/08/2026 13:46

  1. 1.3 / 9.5 — Potassium alginate condition dropped: The Key Interactions item at line 566 lists potassium supplements, potassium-sparing diuretics and renin-angiotensin blockers without the ER’s “Caution with potassium alginate” salt-form condition (ER line 323), broadening a conditional caution into an unconditional one; the same condition is preserved in the contraindication list at line 545.

Fixes 28/08/2026 13:46

  1. 1.3 / 9.5 — Potassium alginate condition restored: Appended “, if potassium alginate” to the potassium interaction item in [caution_items], restoring the ER’s salt-form condition and matching how the same condition is carried in the contraindication list.

Issues 28/08/2026 13:40

  1. 10.2 — Reflux protocol missing from Protocol panel: The third action slot repeats timing already stated in action_1_sub and action_2_sub, while the ER’s distinct Reflux protocol (ER line 361, “0.5–1 g with bicarbonate, chewed or sipped after meals and at bedtime, four times daily”) is omitted, so the sheet’s first time-to-effect entry has no corresponding dose.

Fixes 28/08/2026 13:40

  1. 10.2 — Reflux protocol added to Protocol panel: Replaced the third action slot’s redundant “Best time of day / Split by purpose” entry with the ER’s Reflux protocol (ER line 361) — label “Reflux protocol”, value “0.5–1 g four times daily”, subline “Raft-forming alginate with bicarbonate, chewed or sipped after meals and at bedtime” — so the sheet’s leading time-to-effect entry now has a corresponding dose.

Issues 28/08/2026 13:34

  1. 4.5 — Exceeds the one A4 page budget: The sheet renders well beyond the ~1031 px print height (A4 less the 12 mm .sheet padding); the Monitoring card alone runs roughly 740 px and the Key Interactions gate roughly 450 px. The most verbose elements were carried over near-verbatim instead of being condensed — caution_items 2 and 3 (lines 559–560) retain “such as” filler, monitoring_cadence (line 741) runs 360 characters, and action_3_sub (line 472) runs 141 characters.

Fixes 28/08/2026 13:34

  1. 4.5 — Key Interactions condensed: Replaced “such as” filler with the ER’s example drugs in parentheses — “Metal-chelating antibiotics (tetracyclines such as doxycycline; fluoroquinolones such as ciprofloxacin)…” became “Tetracyclines (doxycycline), fluoroquinolones (ciprofloxacin)…”, and the acid-suppression item became “Proton pump inhibitors (omeprazole) and histamine-2 blockers (famotidine)”. Every named drug is retained.

  2. 4.5 — Contraindication wording tightened: Trimmed redundant modifiers in the dysphagia item, from “Dysphagia, known esophageal stricture, or any prior food or oral medication impaction” to “Dysphagia, esophageal stricture, or prior food or oral medication impaction”.

  3. 4.5 — Monitoring cadence shortened: Cut the cadence paragraph from 360 to 285 characters (“then every 6 months while use continues” → “then every 6 months”; “every fortnight during the first 3 months” → “fortnightly for the first 3 months”), preserving every interval and trigger.

  4. 4.5 — Monitoring table cells trimmed: Shortened the seven longest Target and Why cells (blood lead, fasting glucose and HbA1c, 25-hydroxyvitamin D, serum sodium and blood pressure, estimated glomerular filtration rate, urinary iodine, complete blood count) without dropping any numeric range.

  5. 4.5 — Protocol sub-cells condensed: Removed the redundant “Modified alginate” prefix from the binder sub-cell and tightened the timing sub-cell (“again at bedtime” → “at bedtime”; “before the meal” → “before meals”).

Issues 28/08/2026 13:27

  1. 1.2 / 1.3 — Reflux hedge dropped in At-A-Glance: [at_a_glance] (line 433) reads “relieves heartburn”, but the ER Conclusion (line 484) reads “relieves heartburn, though how much is disputed” and the ER Expected Benefits marks the same benefit “⚠️ Conflicted” (line 165); dropping the qualifier strengthens the ER claim.

Fixes 28/08/2026 13:27

  1. 1.2 / 1.3 — Reflux hedge restored in At-A-Glance: Changed “relieves heartburn” to “relieves heartburn, though how much is disputed”, matching the ER Conclusion; “along the way” was dropped and “uptake of radioactive strontium” tightened to “radioactive strontium uptake” to keep [at_a_glance] within the 60-word budget (now 59 words).