Audit: QRS - Maltodextrin for Health & Longevity

Audit conducted on 22/09/2026 06:35 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	83
Failed	0
N/A	10
Pass Rate	100.00%

• Total = Passed + Failed + N/A
• Pass Rate = Passed / (Passed + Failed) × 100
• N/A items are excluded from the pass rate calculation

---

1. General Rules

#	Description	Result	Comments
1.1	Every claim, magnitude, label, recommendation, and statement in the QRS is literally supported by content in the source ER.	🟢	Protocol, time-to-effect, benefit/risk tiers, gates, biomarker table and qualitative list all trace to ER lines 147–226, 245–299, 317–343, 363–375, 424, 452–475.
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 carries the ER’s hedges verbatim in substance (“rest on one research group”, “compared with fasting”).
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”).	🟢	Tier assignments and contraindication severity match the ER exactly.
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.	🟢	Gates draw only from Key Interactions & Contraindications; no Benefit-/Risk-Modifying Factor content appears anywhere.
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 IDs, author names or brand names appear in the QRS at all.
1.6	The QRS does not introduce new attributions.	🟢	No attributions beyond the template’s own AI4L / model subline.

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.	🟢	Measured, two-forms framing mirrors the ER Conclusion.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Functional target ranges and actionable protocol values without exhortation.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Declarative presentation throughout; no imperatives.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Cadence and monitoring text are stated as observed practice, not instruction.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “should”, or “advised” in the QRS’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns present.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are spelled out (e.g., “glycated hemoglobin”, “high-sensitivity C-reactive protein”).
2.8	Information is presented in a concise and very compact manner	🟢	Tier lines are semicolon-joined headings; gate items are stripped to the key fact.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text scan for “you”/”your”.
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.	🟢	Functional (not conventional) biomarker ranges and titration detail address this 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.	🟢	Continuous glucose monitoring and weekly symptom tracking are retained.
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.	🟢	No simplification toward general-population framing.
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 names the narrow use cases and states “a cost otherwise”, the longevity-audience reading.
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.	🟢	“anti-aging” does not occur; title uses “Health & Longevity”.
2.15	The document’s own voice uses formal clinical and scientific terminology, not colloquial or consumer-grade language (e.g., “oral medication” not “pill(s)”; “oral” / “administered orally” not “taken by mouth” / “given by mouth”; “injection” not “shot”; “adverse event” not “bad reaction”). This holds on EVERY surface, including the QRS lede — the stricter plain-language bar (see 2.7) does not license lay phrasing for route of administration. Direct quotes from sources are exempt.	🟢	“Oral medications requiring precise absorption” retained verbatim; no route-of-administration colloquialisms anywhere.

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 headings byte-identical to the template (lines 446, 489, 533, 567, 590, 640, 671, 675–677, 821).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variables present; marker_#/qualitative_item_# correctly expanded to 9 and 6 instances.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff against the template shows the head, CSS block, website="…" spans, footer and disclaimer 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 used by 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.	🟢	Protocol labels and all nine interaction labels carry the ER’s bold labels; only the em-dash glosses inside parens are trimmed, as items 9.4/9.5 require.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No invented labels; time-to-effect cell labels name the ER’s own two forms and the preoperative protocol.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Full-text scan returns no emoji; the ER’s ⚠️ / ⭕️ markers were 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.	🟢	Twelve ER benefit and eight ER risk subsections are condensed to one line per tier; interaction glosses and contraindication rationales stripped.

---

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, immediately after <!doctype html> on 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.
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 duplicate rendering.
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, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: maltodextrin_2026-0922-0416_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.9.11, matching 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)	🟢	Line 6: qrs_creation_date: 2026-0922-0617.
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” is a single word with 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 context-window or other qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the file on disk.
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Re-verified across all nine keys, including git_user and git_issue.

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: “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 (e.g., & for &)	🟢	Line 417: “Maltodextrin for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 09/22/2026, matching 2026-0922.
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 block is identical to the template apart from the two required variables.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Compresses ER lines 497–499 into the two-forms decision.
7.2	[at_a_glance] is no longer than 60 words	🟢	56 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct sentence of the ER Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Uses “fast sugar”, “blood sugar control”, “blood fat” rather than glycemic/lipid terminology; no acronyms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years or sample sizes.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	“modestly improves” carries no numbers.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All five items come from “Populations who should avoid Maltodextrin”, ER lines 339–343.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All five ER avoid-populations are present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Five <li> elements inside the span (lines 570–585).
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.	🟢	“given the mucosal findings in animal and cell models — the digestible form, pending human data” and “which is a concealed rapid glucose load” are stripped; no dash clauses remain.
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).	🟢	“(Montreal L1 or L3)”, “(above 10% gastric retention at 4 hours)”, “breath-test-confirmed”, “unlabeled or uncounted” and “from that source grain” all 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	The ER uses no ranking notation inside parentheses in this section.
8.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no population, condition, or scenario for which the intervention should be avoided, deferred, or used only under specialist supervision.	🟢	The ER does identify such populations and the section is correctly 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	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 nine items come from ER lines 319–335.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All nine ER interaction bullets present; no overlap with the five contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Nine <li> elements inside the span (lines 593–630).
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.	🟢	Every ER rationale sentence is dropped; only the label plus the Caution/Monitor/Additive caution verdict remains.
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).	🟢	All named example drugs retained; only the em-dash definitional glosses inside the parens are trimmed, as 9.4 requires.
9.6	When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol.	N/A	The ER uses no ranking notation inside parentheses in this section.
9.7	The section is left empty ONLY IF the ER’s Key Interactions & Contraindications section identifies no interaction, additive effect, or exposure that changes how the intervention is used.	🟢	The ER identifies nine and the section is correctly populated.
9.8	If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	All three actions come from ER Therapeutic Protocol lines 365, 373, 375.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Endurance fueling, resistant-form metabolic dosing and preoperative loading are the three regimens attached to the ER’s High-tier benefits.
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 lists far more than three actionable aspects.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All nine cells populated; values and subs match the ER doses, concentrations and timings exactly.

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	🟢	Digestible 15–30 minutes and resistant 8–12 weeks from ER line 424; preoperative 2 hours from ER line 161.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Order follows the ER High-tier benefit order: endurance, postoperative insulin resistance, glycemic control.
11.3	If less that three distinct time-to-effect aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	Three distinct time-to-effect aspects are present in the ER.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine cells populated; time_3_sub is the ER sentence verbatim.
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 (line 424).

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All twelve items correspond to the ER subsection headings at lines 153–225.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated (lines 535–560).
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 item is the ER heading alone; no Magnitude text carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s “⚠️ Conflicted” and “⭕️ Not Central to Health & Longevity” markers are stripped; no parentheses remain.
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four tiers have items in the ER.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All eight items correspond to the ER subsection headings at lines 251–299.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present and populated (lines 642–665).
13.3	Items are as concise as possible. No explanations, no elaborations, no effect sizes, no qualifiers, no attributions, no citations, no study details, no mechanistic explanations, etc. Just the key fact.	🟢	Each item is the ER heading alone; no Magnitude or mechanism text carried over.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	The ER’s “⚠️ Conflicted” marker on the microbiota item is stripped; no parentheses remain.
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	N/A	All four tiers have items in the ER.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Drawn from Monitoring Protocol & Defining Success, ER lines 452–466.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All nine ER table rows present, with targets and “Why” text matching the ER.
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.	🟢	Line 810: baseline, weekly bowel symptoms, 12-week panel, then 6–12 months, plus repeat CGM — condensed from ER lines 452–454.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Drawn from the qualitative-markers list, ER lines 470–475.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers present, verbatim and in ER order.

Issues 22/09/2026 06:35

Pass rate 100.00%. No issues found.

Issues 22/09/2026 06:22

1. 4.5 — Cadence paragraph not condensed: [monitoring_cadence] (QRS lines 810-815) reproduces two full ER sentences (ER lines 452/454) at 355 characters in a field the template renders as a single compact “Cadence:” line, pushing the Monitoring card past its per-section one-page budget.

Fixes 22/09/2026 06:22

1. 4.5 — Cadence paragraph condensed: [monitoring_cadence] was cut from 355 to 258 characters, replacing the two near-verbatim ER sentences with a compact form (“Baseline metabolic panel before either form is started. Bowel symptoms weekly during resistant-form titration. Panel and inflammatory marker at 12 weeks, then every 6–12 months. Continuous glucose monitoring repeated at 12 weeks for regular digestible-form use.”) that keeps every cadence fact.