Audit: QRS - Post-Meal Walk for Health & Longevity

Audit conducted on 26/09/2026 14:21 using AI4L / Opus 5.5

Iterations

Summary

Items	Count
Total	94
Passed	89
Failed	0
N/A	5
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)”; “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.	🟢

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”	🟢
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., & for &)	🟢
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & 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] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence	🟢
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢
7.3	[at_a_glance] is no longer than 70 words	🟢
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢
7.7	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.	🟢
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.	🟢
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

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.	🟢
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.	🟢
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

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
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
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

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.	🟢

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.	🟢

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 26/09/2026 14:21

Pass rate 100.00%. No issues found.

Issues 26/09/2026 14:16

1. 2.13 — Audience signal difference omitted: The ER states the glucose benefit is largest in people who already handle sugar poorly and that people with normal glucose tolerance see smaller absolute changes (Conclusion; Benefit-Modifying Factors), but the at_a_glance (line 433) omits this, the main way the signal differs for health-focused adults.

Fixes 26/09/2026 14:16

1. 2.13 — Audience signal difference added: Reworded at_a_glance to state the rises are “largest after big, starchy dinners and with poor sugar control”, which reflects the ER’s point that people with normal glucose tolerance see smaller gains. It was trimmed elsewhere to stay at 70 words.

Issues 26/09/2026 14:13

1. 4.2 / 4.3 — ER interaction labels abbreviated: The combined Key Interactions item at line 562 drops the ER bold label “Other glucose-lowering drugs”, shortens “Glucose-lowering supplements” to “supplements”, and abbreviates “Resistance exercise breaks and standing desks” to “resistance breaks, standing desks”.

Fixes 26/09/2026 14:13

1. 4.2 / 4.3 — ER interaction labels restored: Rewrote the combined Key Interactions item to use the ER bold labels verbatim: “Other glucose-lowering drugs (metformin; SGLT2 inhibitors such as empagliflozin)”, “glucose-lowering supplements”, and “resistance exercise breaks and standing desks” (previously “Metformin, SGLT2 inhibitors”, “supplements”, “resistance breaks, standing desks”).

Issues 26/09/2026 14:09

1. 4.5 — Key Interactions exceed page budget: The Key Interactions gate (lines 553-564) holds 10 items, several running 3-4 rendered lines (line 563 lists six agents), so together with the other sections the sheet exceeds one A4 page; related items such as insulin/sulfonylureas and GLP-1/other glucose-lowering agents were not merged or condensed.

Fixes 26/09/2026 14:09

1. 4.5 — Key Interactions condensed: Merged the separate insulin and sulfonylurea/meglitinide hypoglycemia items into one entry, and shortened the additive glucose-lowering item (“glucose-lowering supplements” to “supplements”, “resistance exercise breaks” to “resistance breaks”), keeping all example agents, cutting the gate from 10 to 9 items.

Issues 26/09/2026 14:07

1. 4.5 — Sheet exceeds one A4 page: The Key Interactions gate (lines 553-564) carries 10 items (~1,580 characters in a half-width column), with the final item (line 563) chaining 13 agents across four categories; combined with the 7-row Monitoring table and 7 qualitative items, the sheet is unlikely to fit one A4 page and Key Interactions was not condensed to budget.

Fixes 26/09/2026 14:07

1. 4.5 — Condensed Key Interactions gate: Trimmed example lists to fit the one-page budget while keeping at least one example per category: dropped glyburide (sulfonylureas), liraglutide (GLP-1), chromium and alpha-lipoic acid (supplements), whey protein preloads (meal-sequencing aids), and shortened “psyllium fiber” to “psyllium” in the combined additive-lowering item.

Issues 26/09/2026 14:04

1. 2.7 — Unexplained insulin regimen jargon: Key Interactions (line 554) uses “basal-bolus regimens” without the plain-language gloss the ER provides (“background plus mealtime insulin”).

Fixes 26/09/2026 14:04

1. 2.7 — Unexplained insulin regimen jargon: Replaced “basal-bolus regimens” with “background plus mealtime regimens” in the Insulin item of Key Interactions, using the ER gloss.

Issues 26/09/2026 14:01

1. 2.7 — Contraindication jargon left unglossed: The Contraindications gate (lines 543–546) drops the ER’s plain-language glosses for “aortic stenosis”, “arrhythmias”, “postprandial hypotension” and “Hypoglycemia unawareness”, while line 542 keeps “(heart attack)”, leaving specialist terms unexplained for a lay reader.

Fixes 26/09/2026 14:01

1. 2.7 — Glossed contraindication jargon: Added the ER’s plain-language glosses to the Contraindications gate: “aortic stenosis (a narrowed heart valve)”, “arrhythmias (irregular heart rhythms)”, “Hypoglycemia unawareness (loss of the warning symptoms of low glucose)”, and “post-meal” before “systolic fall” for postprandial hypotension.

Issues 26/09/2026 13:59

1. 2.7 — Unnecessary jargon in protocol/monitoring: action_1_sub (line 450) uses the unexplained term “3 METs” where the ER offers “a comfortable strolling pace”, and marker_6_why (line 665) reads “Detects postprandial hypotension” instead of plain wording.

Fixes 26/09/2026 13:59

1. 2.7 — Unnecessary jargon replaced: Changed action_1_sub from “3 METs (4–5 km/h)” to “Comfortable strolling pace (4–5 km/h)” and marker_6_why from “Detects postprandial hypotension” to “Detects post-meal blood pressure drops”, both using ER wording.

Issues 26/09/2026 13:55

1. 1.1 / 10.4 — Walk duration rendered as delay: Line 458 action_2_value “30–45 min after the main meal” reads as a start delay; the ER Therapeutic Protocol describes “A single 30–45-minute walk after the main meal”.
2. 1.2 — Cautious “linked to” dropped: Line 557 SSRIs/antipsychotics item states “low post-meal systolic pressure, falls” as a direct effect, whereas the ER says “Linked to low post-meal systolic pressure and falls”.
3. 7.2 — Risk groups narrowed in summary: Line 433 “Risks center on insulin users and people with heart-related chest pain” omits the ER Conclusion’s “drugs that force insulin release” from the low-blood-sugar risk group.

Fixes 26/09/2026 13:55

1. 1.1 / 10.4 — Walk duration rendered as delay: Changed action_2_value from “30–45 min after the main meal” to “One 30–45-min walk after the main meal”, matching the ER’s single 30–45-minute walk.
2. 1.2 — Cautious “linked to” dropped: Restored the ER’s cautious phrasing in the SSRIs/antipsychotics item: “linked to low post-meal systolic pressure and falls”.
3. 7.2 — Risk groups narrowed in summary: Rewrote the At-A-Glance risk sentence to “users of insulin or insulin-releasing drugs and people with heart-related chest pain” and tightened the opening sentence to stay within 70 words.

Issues 26/09/2026 13:52

1. 1.2 / 1.3 — Interaction hedges dropped: The Key Interactions items remove the ER’s “may”: vasodilators read “deeper post-meal and standing blood pressure falls” (line 558; ER: “May deepen”), and GLP-1 receptor agonists read “fullness or nausea while walking” (line 562; ER: “may cause fullness or nausea”).
2. 1.3 — Blood pressure benefit overstated: The At-a-Glance (line 433) says walking gives “a softer blood pressure drop after meals in some older adults” but leaves out the ER Conclusion’s limit “at least during the walk”.

Fixes 26/09/2026 13:52

1. 1.2 / 1.3 — Interaction hedges restored: Vasodilators now read “may deepen post-meal and standing blood pressure falls”, and GLP-1 receptor agonists now read “may cause fullness or nausea while walking”, matching the ER’s hedged wording.
2. 1.3 — Blood pressure qualifier restored: At-a-Glance now reads “a softer after-meal blood pressure drop in some older adults, at least while walking”, which keeps the ER Conclusion’s limit and stays within 70 words (69).