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

Audit conducted on 22/08/2026 05:14 using AI4L / Grok 4.1

Iterations

Summary

Items	Count
Total	93
Passed	85
Failed	0
N/A	8
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)”; “injection” not “shot”; “adverse event” not “bad reaction”). 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”	N/A	N/A — no source ER section 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.	🟢
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] is dense, execution-oriented summary of the ER Conclusion section	🟢
7.2	[at_a_glance] is no longer than 60 words	🟢
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢
7.6	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.	N/A	N/A — ER contraindications do not use ranking notation inside parentheses.
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	N/A — Contraindications is not empty.

---

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.	N/A	N/A — ER key interactions do not use ranking notation inside parentheses.
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	N/A — Key Interactions is not empty.

---

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	N/A — ER Protocol lists more than three actionable implementation aspects; all three action sets are used.
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	N/A — ER provides at least three time-to-effect aspects; all three time sets are used.
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	N/A — ER provides time-to-effect information; the section is present.

---

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 22/08/2026 05:14

Pass rate 100.00%. No issues found.

Issues 22/08/2026 05:03

1. 1.1 / 1.4 — Cadence facts as targets: Monitoring rows 9–11 (QRS lines 687–718) put ER cadence/eligibility sentences in the Target column (“Claudication goals add timed walking distance”; “Claudication goals add ankle–brachial index”; “Bleed-risk histories add a platelet count”). Those strings are not optimal-range targets in the ER.

2. 2.8 / 4.5 — Monitoring table not condensed: The 11-row biomarker table repeats cadence text in Target/Why cells instead of keeping the ER table’s eight quantified markers and leaving conditional tests in the cadence note, so the sheet is not compact for one A4 page.

Fixes 22/08/2026 05:03

1. 1.1 / 1.4 — Cadence facts as targets: Removed monitoring table rows 9–11 (timed walking distance, ankle–brachial index, platelet count) so cadence/eligibility sentences are no longer presented as Target values. Those tests remain named in the cadence note, matching the ER Monitoring prose.

2. 2.8 / 4.5 — Monitoring table not condensed: Cut the biomarker table back to the ER’s eight quantified markers with real optimal ranges, leaving conditional claudication and bleed-risk tests in the cadence paragraph instead of extra rows.

Issues 22/08/2026 04:43

1. 1.1 — Invented monitoring targets: marker_9_target, marker_10_target, and marker_11_target (QRS lines 692, 703, 714) use the invented phrase “No numeric range”. The ER Monitoring section names timed walking distance, ankle–brachial index, and platelet count but does not state that wording or any empty-state equivalent.

Fixes 22/08/2026 04:43

1. 1.1 — Invented monitoring targets: Replaced marker_9_target, marker_10_target, and marker_11_target from the invented phrase “No numeric range” with ER Monitoring wording: “Claudication goals add timed walking distance”, “Claudication goals add ankle–brachial index”, and “Bleed-risk histories add a platelet count”.

Issues 22/08/2026 04:34

1. 1.1 / 2.5 — Invented “Add with” targets: Marker 9–11 Target cells (QRS lines 691, 703, 713) say “Add with ankle–brachial index”, “Add with timed walking distance”, and “Add with bruising diary”. Those strings are not ER Optimal Functional Range values and are imperative pairing instructions rather than presented information.

2. 7.4 — Clinical-register at-a-glance phrasing: At-a-glance (QRS line 433) uses “adverse events” and “authentic Cuban material” instead of plain-language terms a non-specialist would use unprompted.

Fixes 22/08/2026 04:34

1. 1.1 / 2.5 — Invented “Add with” targets: Replaced marker 9–11 Target cells from “Add with …” pairing instructions with “No numeric range”, matching the ER Monitoring table’s lack of an Optimal Functional Range for those tests.

2. 7.4 — Clinical-register at-a-glance phrasing: Replaced “authentic Cuban material” with “the original Cuban product” and “adverse events” with “side effects”; dropped “remaining” to keep the paragraph at 60 words.

Issues 22/08/2026 04:21

1. 1.3 — Walking claim overbroad: At-a-glance (line 433) reports “longer pain-free walking” without the ER Conclusion qualifier “in people with poor leg circulation”, which broadens a claudication-specific claim.

2. 2.7 — Chronopharmacology jargon: action_2_sub (line 461) uses “chronopharmacology”, specialist jargon a non-specialist would not use unprompted.

3. 7.4 — Lipid not plain language: at_a_glance (line 433) uses “lipid”, a clinical-register term; the ER Conclusion’s plain-language equivalent is “blood fats”.

Fixes 22/08/2026 04:21

1. 1.3 — Walking claim overbroad: At-a-glance now includes the ER Conclusion qualifier “in people with poor leg circulation” on the pain-free walking claim; “some” and “Western” were dropped so the paragraph stays at 60 words.

2. 2.7 — Chronopharmacology jargon: Replaced “chronopharmacology study” with “timing study” in action_2_sub (line 461).

3. 7.4 — Lipid not plain language: Replaced at-a-glance “lipid change” with “blood-fat change”, matching the ER Conclusion’s plain “blood fats” wording.

Issues 22/08/2026 04:03

1. 1.1 — Unsupported QRS statements: action_2_sub (line 461) says “no human study shows a morning advantage,” which the ER does not state; Protocol says “no human chronopharmacology study.” marker_9_target (line 692) uses the ABI definition as a target, and marker_10_target (line 703) invents “Bleed-risk baseline,” neither of which is an ER optimal range.

2. 1.3 — Strengthened timing claim: action_2_sub (line 461) strengthens the ER’s “no human chronopharmacology study shows a morning advantage” into “no human study shows a morning advantage.”

3. 14.2 — Missing timed walking distance: ER Monitoring lists timed walking distance as a measurable claudication add-on alongside ankle–brachial index, but the QRS biomarker table has no timed-walking-distance row.

Fixes 22/08/2026 04:03

1. 1.1 / 1.3 — Chronopharmacology phrasing: Restored the ER Protocol wording in action_2_sub: “no human study shows a morning advantage” is now “no human chronopharmacology study shows a morning advantage.”

2. 1.1 — Invented marker targets: Replaced the ABI definition-as-target and the invented platelet target “Bleed-risk baseline” with Monitoring-narrative actions (“Add with timed walking distance”; “Add with bruising diary”) and moved the ankle-to-arm pressure-ratio gloss into Why.

3. 14.2 — Timed walking distance: Added a timed walking distance biomarker row so the claudication add-ons from the ER Monitoring paragraph are all listed.

Issues 22/08/2026 03:58

1. 4.3 — Time-to-effect labels abbreviated: Time-to-effect labels use invented/abbreviated names (“Lipids”, “Blood pressure”, “Walking distance”) instead of the ER benefit labels LDL Cholesterol Reduction, Blood Pressure Reduction, and Walking Distance in Intermittent Claudication.

2. 9.4 — Statin trailing elaboration: The Key Interactions statin line keeps a trailing explanation after a colon: “Statins (atorvastatin, simvastatin, rosuvastatin): generally compatible”. 9.4 requires only the interacting agents.

3. 14.2 — Missing measurable biomarkers: ER Monitoring prose names ankle–brachial index (claudication goals) and platelet count (bleed-risk histories) as measurable add-ons; the QRS table lists only the eight tabulated biomarkers.

Fixes 22/08/2026 03:58

1. 4.3 — Time-to-effect labels abbreviated: Replaced time-to-effect labels “Lipids”, “Blood pressure”, and “Walking distance” with the ER benefit names LDL Cholesterol Reduction, Blood Pressure Reduction, and Walking Distance in Intermittent Claudication.

2. 9.4 — Statin trailing elaboration: Removed the trailing “: generally compatible” from the Key Interactions statin line, leaving “Statins (atorvastatin, simvastatin, rosuvastatin)”.

3. 14.2 — Missing measurable biomarkers: Added Monitoring rows for ankle–brachial index and platelet count, and named both in the cadence sentence as claudication-goal and bleed-risk add-ons.