evipedia.aidev
← Back to Review

Audit: QRS - Allulose for Health & Longevity of the ER frontmatter

Audit conducted on 11/08/2026 20:14 using AI4L / Grok 4

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 doses, benefits, risks, gates, monitoring, and at-a-glance claims track ER Protocol, Expected Benefits, Risks, Key Interactions & Contraindications, Monitoring, and Conclusion.
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 framing retained (speculative tiers; pregnancy without clinician input; no over-claiming of body-composition or longevity effects).
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 vs ER (e.g., pregnancy remains avoid-without-clinician under stop items).
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 from populations-to-avoid; interactions from interaction bullets; risk-modifying factors (e.g., IBS) not relabeled as stop/caution.
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, expert names, or brand names introduced; drug examples match ER interaction lists.
1.6 The QRS does not introduce new attributions. 🟢 No 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. 🟢 Measured, evidence-first tone matches ER Conclusion and protocol language.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Expert, accessible, objective, data-driven; execution framing without hype.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Guide-style presentation, not prescriptive doctor voice.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No directive medical-advice language in variable content; footer disclaimer present.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 Presents doses, risks, and markers as information distilled from the ER.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No direct address of the reader in variable content.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 At-a-glance uses plain language; clinical terms elsewhere mirror ER protocol/interaction labels.
2.8 Information is presented in a concise and very compact manner 🟢 Compact single-page condensation of multi-section ER content.
2.9 It DOES NOT address the reader directly 🟢 No second-person 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. 🟢 Longevity-oriented metabolic framing throughout.
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. 🟢 Assumes willingness to dose, monitor, and substitute sweeteners.
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 written for low-effort general-population use.
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. 🟢 Emphasizes postprandial signal and dose-limited GI trade-off relevant to optimizers.
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. 🟢 Uses “longevity”; no anti-aging framing.
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 clinical wording (e.g., postprandial, GLP-1 receptor agonists, α-glucosidase inhibitors).

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” 🟢 Fixed headings and tier/table labels unchanged.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All template data-qrs-var regions present (marker_#/qualitative_item_# expanded to numbered instances).
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Non-addressed template structure/CSS/footer left intact.

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 audited ER source section for QRS variables is empty requiring empty-state phrasing.
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 action labels match ER bold labels (Glycemic-oriented dosing, Upper bounds, Timing).
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Benefit/risk labels track ER headings; protocol labels not invented.
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 QRS content.
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 single-sheet 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 HTML comment immediately 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. 🟢 YAML delimited by — open/close lines.
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. 🟢 Metadata only in HTML comment; not rendered in 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. 🟢 Values trimmed; duration quoted for colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: allulose_2026-0811-1857_Grok_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.7.02
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-0811-2003
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: Grok
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 Nickname is single word Grok.
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: Grok 4
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) 🟢 Full name is nickname plus version only.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename matches document name.
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. 🟢 Frontmatter values trimmed; quotes only where needed.

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 &) 🟢 Title: Allulose 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., &amp; for &) 🟢 header_topic matches canonical_topic with & encoding.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 08/11/2026 from qrs_creation_date 2026-0811-2003.
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 header_subline_model: Grok 4
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Only standard template header/subline elements; no badge/AKA/audit stamp.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Dense distillation of ER Conclusion (taste/energy, post-meal glucose/insulin, GI risk, not a longevity drug).
7.2 [at_a_glance] is no longer than 60 words 🟢 55 words (≤60).
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each sentence maps to Conclusion/Practical Considerations content.
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Plain language (blood sugar, gut intolerance, sugar alcohols); no specialist acronyms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial names, years, sample sizes, or p-values.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No effect sizes, RRs, or statistics.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Stop items from Populations who should avoid allulose under Key Interactions & Contraindications.
8.2 [stop_items] represent the Contraindications from the ER 🟢 Four stop items match the four ER avoid-populations.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Each stop item is an <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. 🟢 Concise facts only; rationale and dash-trailers stripped.
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). 🟢 Relevant qualifiers retained (e.g., (regulatory)); no required clinical thresholds dropped.
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 contraindications use no ranking notation such as >.
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. 🟢 Section populated; ER identifies avoid populations.
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 🟢 Caution items from ER Key Interactions & Contraindications interaction bullets.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 Seven interaction lines; none duplicated as stop items.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Each caution item is an <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. 🟢 Caution/Monitor trailers and mechanistic notes stripped; key fact + parentheticals only.
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). 🟢 Example drug lists and product classes preserved in parentheses.
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 ER interactions use no ranking notation such as >.
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. 🟢 Section populated; ER identifies interactions.
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 Section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 Actions drawn from Therapeutic Protocol (dosing, upper bounds, timing/form).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Glycemic-oriented dosing, upper bounds, and timing are the three primary implementation aspects.
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 ER provides at least three distinct actionable aspects; all three action sets used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All action label/value/sub fields filled from Protocol content.

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 🟢 Post-meal glucose, post-meal insulin, and body composition cover ER time-to-effect statements.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Ordered by related benefit magnitude: high-tier glucose first, then medium insulin, then body composition.
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 ER provides at least three time-to-effect aspects; all three sets used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 All used time label/value/sub fields filled from ER Practical Considerations/Conclusion.
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 information; section retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Benefits mirror ER Expected Benefits tiers and headings.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 benefits_high/medium/low/speculative all populated.
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. 🟢 Concise key facts only; no effect sizes, citations, or mechanistic elaborations.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 Parentheticals such as (acute) and (GLP-1, PYY, CCK) stripped.
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 sub-sections have items; display=none path not applicable.

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Risks mirror ER Potential Risks & Side Effects tiers and headings.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 risks_high/medium/low/speculative all populated.
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. 🟢 Concise key facts matching ER risk headings; no frequencies or study detail.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parenthetical frequency/severity/study content retained.
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 sub-sections have items; display=none path not applicable.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Monitoring table and cadence derived from ER Monitoring Protocol & Defining Success.
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All six quantifiable biomarkers from the ER table 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. 🟢 Cadence reflects baseline then 1–2 week meal-level feedback and 3–6 month labs.

15. Qualitative Assessment

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

Issues 11/08/2026 20:14

Pass rate 100.00%. No issues found.

Issues 11/08/2026 20:10

  1. 4.2 — Protocol label not verbatim: action_1_label is “Glycemic dosing” rather than the ER Protocol bold label “Glycemic-oriented dosing”.

  2. 4.3 — Protocol label paraphrased: Same action_1_label abbreviates “Glycemic-oriented dosing” to “Glycemic dosing”.

  3. 10.4 — Non-Protocol start dose: action_2_sub includes “start 2–5 g and split across meals”; the 2–5 g start comes from ER Risk Mitigation Strategies, not Therapeutic Protocol.

Fixes 11/08/2026 20:11

  1. 4.2 / 4.3 — Protocol label restored: Changed action_1_label from “Glycemic dosing” to the ER Protocol bold label “Glycemic-oriented dosing”.

  2. 10.4 — Protocol-only upper-bound sub: Replaced action_2_sub “start 2–5 g and split across meals” (Risk Mitigation) with “≤0.9 g/kg total daily; split if daily grams are high” from Therapeutic Protocol.