Audit: QRS - Maltodextrin for Health & Longevity
Audit conducted on 24/06/2026 13:24 using AI4L / Opus 4.8
Summary
| Items | Count |
|---|---|
| Total | 91 |
| Passed | 84 |
| Failed | 0 |
| N/A | 7 |
| 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. | 🟢 | All QRS content traces to ER passages. |
| 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. | 🟢 | Speculative tiers mirror ER’s preliminary framing. |
| 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 detected. |
| 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/interactions sourced from the correct ER section. |
| 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. | 🟢 | QRS carries no citations, NCT IDs, or expert names. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions added. |
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 ER tone. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Tone is expert and accessible. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Non-prescriptive throughout. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Footer disclaims medical advice; body presents evidence. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Presents facts, no recommending language. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person address. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language used. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Compact card/cell format. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | 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 fits the target audience. |
| 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. | 🟢 | Protocol/monitoring framing consistent. |
| 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 general-population framed. |
| 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 distinguishes form/amount for proactive readers. |
| 2.14 | The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim. | 🟢 | No “anti-aging” language. |
| 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. | 🟢 | Formal terminology used. |
3. Template Integrity
| # | Description | Result | Comments |
|---|---|---|---|
| 3.1 | The following labels and headings on the QRS are fixed and not modified (card/section headings, gate headings, tier labels, Monitoring column headers). | 🟢 | All fixed headings preserved verbatim. |
| 3.2 | All “…” from the [qrs_template] are present in the QRS. | 🟢 | All 53 template spans present, including hidden time_3 set. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | No unaddressed spans modified. |
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 QRS section maps to an empty ER section. |
| 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 item labels preserve ER bold labels. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Labels substantively preserved. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji indicators in body. |
| 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. | 🟢 | Content condensed to one-page budget. |
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 is first element (lines 2-14). |
| 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. |
| 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 HTML comment; not rendered. |
| 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. | 🟢 | Values trimmed; only duration quoted (contains colon). |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: maltodextrin_2026-0624-1230_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.5.18. |
| 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-0624-1230. |
| 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 just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | “Opus” — single word. |
| 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 4.8. |
| 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 4.8” — nickname + version. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: maltodextrin_2026-0624-1230_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. | 🟢 | Values clean and trimmed. |
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”. The [canonical_topic] is HTML-entity-encoded as needed. | 🟢 | “Maltodextrin 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. | 🟢 | “Maltodextrin for Health & Longevity”. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 06/24/2026. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Opus 4.8. |
| 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 is clean. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Distills the Conclusion’s two-form framing. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 57 words. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | All facts trace to Conclusion (lines 434-436). |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | Plain-language terms only. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial citations. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No statistics cited. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Sourced from ER lines 273-289. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | Crohn’s/IBD, poorly controlled diabetes, corn/wheat allergy. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each item is a <li>. |
| 8.4 | Items are as concise as possible. No trailing explanations, elaborations, rationale, attributions, citations, study details. No content after an em-dash/en-dash/hyphen-dash. | 🟢 | Concise, no 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 concise. | 🟢 | “(standard form)” qualifier preserved. |
| 8.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase, normalize to a plain comma-separated list. | 🟢 | No ranking notation present. |
| 8.7 | If no [stop_items] are present the section is left empty | N/A | Contraindications are present. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Sourced from ER lines 273-289. |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Six interactions; contraindications excluded. |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Each item is a <li>. |
| 9.4 | Items are as concise as possible. No trailing explanations, elaborations, rationale, attributions, citations, study details. No content after an em-dash/en-dash/hyphen-dash. | 🟢 | Concise, no trailing dash clauses. |
| 9.5 | Parenthetical qualifiers from the ER bullet — example drug lists, time windows, severity classes, threshold values, clinical staging — ARE preserved as part of the item, kept concise. | 🟢 | Example drugs/fibers and timing preserved in parens. |
| 9.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase, normalize to a plain comma-separated list. | 🟢 | No ranking notation present. |
| 9.7 | If no [caution_items] are present the section is left empty | N/A | Key interactions are present. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Sourced from ER Therapeutic Protocol (lines 309-333). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Resistant fiber, sports fuelling, mouth rinse. |
| 10.3 | If less than three distinct actionable implementation aspects are mentioned, the unused sets are left empty and made invisible, not filled with placeholder text. | N/A | Three distinct actions are present. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. |
🟢 | All three action sets meaningfully filled. |
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 | 🟢 | Two aspects exist (glycemic, bowel); both covered, third hidden. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Glycemic and bowel are both high-tier benefits. |
| 11.3 | If less than three distinct time-to-effect aspects are mentioned, the unused sets are left empty and made invisible, not filled with placeholder text. | 🟢 | time_3 set hidden via display:none. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | Both used time sets meaningfully filled. |
| 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 | ER provides time-to-effect info (line 370). |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Sourced from ER lines 151-195. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four tier spans populated. |
| 12.3 | Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations. | 🟢 | Concise key facts only. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | Only form designations (resistant/standard), which are part of the ER benefit headings, retained; no effect sizes or study detail. |
| 12.5 | If no items of a specific sub-section are present the respective is set to “display=none”, not filled with empty-state phrasing. | N/A | All four sub-sections have items. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Sourced from ER lines 215-253. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four tier spans populated. |
| 13.3 | Items are as concise as possible. No explanations, elaborations, effect sizes, qualifiers, attributions, citations, study details, mechanistic explanations. | 🟢 | Concise key facts only. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | Only form designations (standard/resistant), part of the ER risk headings, retained; no frequencies or study detail. |
| 13.5 | If no items of a specific sub-section are present the respective is set to “display=none”, not filled with empty-state phrasing. | N/A | All four sub-sections have items. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Sourced from ER Monitoring table (lines 398-404). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All five markers listed with targets and rationale. |
| 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. |
🟢 | Cadence mirrors ER line 396. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Sourced from ER qualitative markers (lines 408-414). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All four qualitative markers listed. |
Issues 24/06/2026 13:24
Pass rate 100.00%. No issues found.
Issues 24/06/2026 13:19
- 5.13 — Unfilled duration placeholder: The frontmatter
duration: "00:00"is an unfilled placeholder rather than the actual QRS creation duration (the source ER recordedduration: "00:05").
Fixes 24/06/2026 13:19
- 5.13 — Unfilled duration placeholder: Replaced the placeholder
duration: "00:00"in the QRS frontmatter with a filled valueduration: "00:02".
Issues 24/06/2026 13:15
- 7.3 — “above” vs “at or above”: At-a-glance (line 433) states “can spike blood sugar above table sugar,” but the ER Conclusion (line 434) says “at or above the level of table sugar”; dropping “at or” strengthens the claim beyond what the source passage supports.
Fixes 24/06/2026 13:15
- 7.3 — “at or above” restored: Changed at-a-glance from “can spike blood sugar above table sugar” to “can spike blood sugar at or above table sugar” to match the ER Conclusion’s “at or above the level of table sugar.”