Audit: QRS - Acetate for Health & Longevity

Audit conducted on 18/09/2026 02:09 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.	🟢	Verified item by item against the ER: protocol values, gate items, tier items, all eight monitoring targets and the five qualitative markers trace to ER text.
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.	🟢	Hedges retained, e.g. “modest” and “least dependable” in the lede mirror the ER Conclusion; speculative tiers kept as speculative.
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 claim strengthened or softened; the conflicted weight-loss finding is surfaced in the lede as “Weight loss is least dependable”.
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.	🟢	Benefit-Modifying and Risk-Modifying Factors from the ER are not surfaced in the gates; gate content comes only from Key Interactions & Contraindications.
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, study names, NCT identifiers, expert names or brand names appear anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind are 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.	🟢	Matches the ER’s measured, hedged register.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert and data-driven (thresholds, ranges, cadence) while remaining accessible.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents conditions and markers as facts, not as instructions from a clinician.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives; gates and monitoring are stated as conditions and ranges.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	Content is presented, not recommended or advised.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person forms occur anywhere in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are only those the ER itself uses; no gratuitous jargon added.
2.8	Information is presented in a concise and very compact manner	🟢	All entries are noun phrases or short clauses; no prose padding.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no “you”/”your” in the document.
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 targets proactive, risk-aware adults optimising metabolic markers.
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.	🟢	Presents a per-meal dosing protocol plus baseline, 4-week and 12-week panels and annual dental checks.
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 pitched at the general population; assumes willingness to monitor and adhere.
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.	🟢	The lede states effects “matter most where starting numbers are impaired”, the key audience-differentiating 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.	🟢	The term “anti-aging” does not appear.
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.	🟢	No colloquial route-of-administration or drug terms; “oral” is used in action_1_label.

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, gate headings, tier labels and monitoring column headers match the template exactly.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 38 template variable names are present; marker_#_* expanded to 1-8 and qualitative_item_# to 1-5.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A structural diff against [qrs_template] shows changes confined to checklist-addressed spans; CSS, comments and markup are untouched.

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 is empty; every QRS section has substantive ER content, so no empty-state phrasing is required.
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.	🟢	Standard oral regimen, Timing relative to the meal and Best time of day are the ER’s bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No label is 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.	🟢	No emoji anywhere; the ER’s tier and marker emoji are 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.	🟢	Content is held to the per-section budget; every gate, tier and table entry is a condensed phrase rather than an expanded ER sentence.

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.	🟢	The metadata comment opens on line 2, directly 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.	🟢	Opening --- on line 3, closing --- on line 13; the lead-in text on line 2 sits outside the block.
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 and not echoed by any visible element.
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.	🟢	All values trimmed; only duration is quoted, which is required because the value contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	er_filename: acetate_2026-0918-0010_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.9.11 matches the QRS.md version badge.
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-0918-0148.
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)	🟢	Single word, 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]”	🟢	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)	🟢	Nickname plus version number, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	qrs_filename: acetate_2026-0918-0010_Opus_QRS.html 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.	🟢	Confirmed clean and consistent across all nine keys.

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 &)	🟢	Acetate for Health & Longevity - Quick Reference Sheet, correctly entity-encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	Acetate for Health & Longevity, matching the ER canonical_topic.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	09/18/2026, the MM/DD/YYYY form of 2026-0918-0148.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	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 carries only the title and the template subline; no badge, AKA line or 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	🟢	Condenses the ER Conclusion and leads with the execution-relevant fact that the acid is taken with a starchy meal.
7.2	[at_a_glance] is no longer than 60 words	🟢	55 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause traces to ER Conclusion lines 486-488.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; uses “blood sugar”, “long-term sugar control” and “one blood fat” in place of glucose, HbA1c and triglycerides.
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, relative risks or statistical results.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Derived from the ER’s “Populations who should avoid Acetate” list.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All six ER contraindications are represented.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Six <li> elements inside the stop_items span.
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.	🟢	No trailing clauses; “because of potassium and acid-base handling” is stripped from the kidney-disease item.
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).	🟢	The eGFR threshold (eGFR under 30 mL/min/1.73 m²) and the below 3.5 mmol/L potassium threshold are 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’s contraindication bullets use no 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.	🟢	Correctly not empty; the ER names six populations that should avoid acetate.
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; six contraindications are listed.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Derived from the ER Key Interactions & Contraindications bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All ten ER interactions are represented, none duplicating a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Ten <li> elements inside the caution_items span.
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 verdicts and all mitigation text are stripped; only the agent or exposure 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).	🟢	Example drug lists preserved for secretagogues, diuretics, antacids and laxatives; only the explanatory glosses ahead of the em-dash are dropped.
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’s interaction bullets use no 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.	🟢	Correctly not empty; the ER names ten 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	The section is not empty; ten key interactions are listed.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	Derived from the ER Therapeutic Protocol section.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose/regimen, timing relative to the meal and best time of day are the three load-bearing 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	The ER Therapeutic Protocol section supplies twelve bullets, well over three actionable aspects; all three 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.	🟢	All nine action fields carry ER-derived 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, fasting glucose with HbA1c, and triglycerides are the ER’s three named time-to-effect endpoints.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	All three relate to High-tier benefits, ordered fastest-acting first.
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	The ER supplies three distinct time-to-effect endpoints; all three sets are used.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine time fields carry ER-derived content.
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 under Practical Considerations, so the row is retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Derived from the ER Expected Benefits section.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four tier spans present and 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.	🟢	Each entry is the ER’s benefit heading reduced to its key fact; no magnitudes or mechanisms carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content retained.
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 tiers carry items in the ER (High 2, Medium 2, Low 4, Speculative 2).

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Derived from the ER Potential Risks & Side Effects section.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four tier spans present and 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.	🟢	Each entry is the ER’s risk heading reduced to its key fact; no frequencies or mechanisms carried over.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical 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 tiers carry items in the ER (High 2, Medium 3, Low 2, Speculative 2).

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Derived from the ER Monitoring Protocol & Defining Success section.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All eight biomarkers from the ER table are listed with matching targets and rationales.
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.	🟢	Populated with the full ER cadence: baseline, electrolytes at 4 weeks, full panel at 12 weeks, then every 6-12 months, dental check annually.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Derived from the ER Monitoring Protocol & Defining Success section.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER qualitative markers are listed.

Issues 18/09/2026 02:09

Pass rate 100.00%. No issues found.

Issues 18/09/2026 02:01

1. 2.5 — Imperative in protocol sub-line: [action_3_sub] (line 484) reads “split across lunch and dinner where one dose causes night reflux”, an instruction to the reader, whereas the ER Therapeutic Protocol states it descriptively as “splitting across lunch and dinner is used where a single dose causes reflux at night”.

Fixes 18/09/2026 02:01

1. 2.5 — Imperative in protocol sub-line: Rewrote [action_3_sub] from “split across lunch and dinner where one dose causes night reflux” to “splitting across lunch and dinner is used where one dose causes night reflux”, restoring the ER’s descriptive framing.

Issues 18/09/2026 01:56

1. 4.5 — Protocol panel not condensed: action_2_sub (lines 469–472) and action_3_sub (483–486) reproduce the ER’s Protocol sentences almost verbatim (ER 364, 366), time_2_sub and time_3_sub (514–529) repeat the same eight-week fact twice, and monitoring_cadence (738–741) carries a full ER sentence — pushing the sheet past the one-A4-page budget.

Fixes 18/09/2026 01:56

1. 4.5 — Protocol sub-cells condensed: Rewrote action_1_sub, action_2_sub and action_3_sub so they no longer reproduce the ER’s Protocol sentences verbatim (e.g. “so intake more than 30 minutes ahead misses the window” → “more than 30 minutes ahead misses the window”), keeping the dose, vehicle, split and timing facts intact.
2. 4.5 — Duplicate time-to-effect text removed: Replaced time_2_sub and time_3_sub, which both restated the eight-week trial-duration fact already carried by the “8–12 weeks” values, with the single point they add: “Sustained intake required.”
3. 4.5 — Monitoring cadence tightened: Shortened monitoring_cadence from the full ER sentence to “Baseline panel, electrolytes at 4 weeks, full panel at 12 weeks, then every 6–12 months; dental check annually.”
4. 4.5 — At-a-glance trimmed: Cut at_a_glance from 59 to 55 words by removing redundant wording (“taken with”, “the least dependable result”, “Drawbacks come from”) without dropping any of the five ER Conclusion facts it carries.