Audit: QRS - Calorie Restriction for Health & Longevity

Audit conducted on 27/07/2026 01:24 using AI4L / Opus 4.8

Summary

Items	Count
Total	91
Passed	81
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.	🟢	All QRS content traces to the ER (Conclusion, Protocol, Expected Benefits, Risks, Monitoring, Key Interactions & Contraindications).
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 mirrors the ER’s “remains genuinely unsettled” as “stays unsettled”; speculative benefits/risks preserved as such.
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”).	🟢	Contraindications preserved as absolute (“Pregnant or breastfeeding women”); no strengthening/softening observed.
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 and Key Interactions both drawn from the ER’s “Key Interactions & Contraindications” section; benefits/risks kept in their own categories.
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.	🟢	The QRS carries no PMIDs, NCT IDs, or expert names; only generic drug/supplement names present in the ER interactions section.
1.6	The QRS does not introduce new attributions.	🟢	No new attributions introduced.

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.	🟢	Expert, measured, evidence-driven tone consistent with the ER.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Balanced presentation of benefits, risks, and monitoring.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents evidence; no prescriptive directives.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Footer disclaimer present; body presents information, not advice.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Content is descriptive throughout.
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	🟢	Technical terms limited and appropriate; at-a-glance is plain.
2.8	Information is presented in a concise and very compact manner	🟢	Cells and bullets are compact.
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 matches the ER’s risk-aware, health-optimizing 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 detail assumes a committed audience.
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.	🟢	At-a-glance notes trade-offs “matter most for already-lean, active people”.
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.	🟢	Explicitly distinguishes lean/active vs. general-population signal.
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.	🟢	Title/voice uses “Longevity”; no “anti-aging” usage.
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.	🟢	No colloquial/consumer-grade substitutions; plain terms in at-a-glance are non-colloquial.

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 fixed headings/labels present and unmodified.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All expected variable spans present (header, at-a-glance, actions, times, benefits, gates, risks, markers 1–11, cadence, qualitative 1–6).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Non-content template spans (page_title, website markers) 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 source ER section mapped to a QRS variable 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/monitoring labels derived faithfully from ER content.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Labels correspond to ER wording.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators used; tiers conveyed via bold labels and CSS.
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 fit the single-page template 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 the first element after the doctype (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 “—” on 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.	🟢	Enclosed in an 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 (contains colon) is quoted.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: calorie_restriction_2026-0727-0002_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.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-0727-0118
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” is a single-word nickname.
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, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: calorie_restriction_2026-0727-0002_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 consistent.

#	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 `&`)	🟢	“Calorie Restriction for Health & Longevity - Quick Reference Sheet” (line 22).
6.2	[header_topic] is set to the [canonical_topic] of the ER `frontmatter`, with HTML entities encoded as needed (e.g., `&` for `&`)	🟢	“Calorie Restriction for Health & Longevity” (line 417).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0727-0118 → 07/27/2026 (line 421).
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“Opus 4.8” (line 425).
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 contains only title and standard subline.

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 ER Conclusion (lines 484–486).
7.2	[at_a_glance] is no longer than 60 words	🟢	53 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Improvements, unsettled longevity, and trade-offs all map to the Conclusion.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Uses “blood-sugar handling”, “calorie-burning rate”, “sex hormones”; no acronyms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names or years.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numeric effect sizes.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER `Key Interactions & Contraindications` section	🟢	Derived from ER line 336 (populations who should avoid it).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER contraindication populations captured.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Each 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; “(who are still growing)” and other explanatory clauses dropped.
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).	🟢	Threshold “(BMI < 18.5)” 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	ER contraindications use no ranking notation inside parens.
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	🟢	Derived from ER lines 326–334.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Prescription, OTC, supplement, additive, and other-intervention interactions captured; no contraindication duplication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Each 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.	🟢	GLP-1 explanatory em-dash clause stripped; items concise.
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).	🟢	Named example drugs preserved (glipizide, glyburide; lisinopril, amlodipine; ibuprofen, naproxen; semaglutide; etc.).
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 inside parens.
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	🟢	Derived from ER Therapeutic Protocol (lines 366–376).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER `Protocol` section	🟢	Deficit/CRON, timing (front-loading), and protein distribution.
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	Three actionable aspects 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 cells filled from the ER.

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	🟢	Blood pressure (1–4 wk), fat loss & lipids (2–6 mo), aging effects (months–years) from ER line 417.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered from near-term high-magnitude effects to speculative aging effects.
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 time-to-effect aspects are present.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All three time cells filled 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	ER provides time-to-effect information (line 417).

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER `Expected Benefits` section	🟢	Derived from ER Expected Benefits (lines 152–224).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four tier variables 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.	🟢	Bare benefit titles only; magnitudes and “Conflicted” qualifier stripped.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content carried through.
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.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER `Potential Risks & Side Effects` section	🟢	Derived from ER Potential Risks & Side Effects (lines 240–308).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four tier variables 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.	🟢	Bare risk titles only; magnitudes and “Conflicted” qualifier stripped.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content carried through.
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.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER `Monitoring` section	🟢	Derived from ER Monitoring Protocol table (lines 441–453).
14.2	All measurable/quantifiable biomarkers from the `Monitoring` section are listed	🟢	All 11 ER biomarkers listed (body composition through albumin/CBC).
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 matches ER line 439.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER `Monitoring` section	🟢	Derived from ER qualitative markers (lines 457–462).
15.2	All subjective/qualitative biomarkers from the `Monitoring` section are listed	🟢	All six qualitative markers listed (energy, sleep, mood, hunger, cognition, cold tolerance).

Issues 27/07/2026 01:24

Pass rate 100.00%. No issues found.