Audit: QRS - Botox for Skin Rejuvenation

Audit conducted on 02/10/2026 18:28 using AI4L / Opus 5.5

Iterations

Summary

Items	Count
Total	94
Passed	84
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.	🟢
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.	🟢	All template spans present (page_title through qualitative_item_#)
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	ER sections used are populated; no empty-state phrasing needed
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.	🟢	Metadata comment immediately follows <!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.	🟢
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 &)	🟢	“Botox for Skin Rejuvenation - 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., & for &)	🟢
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-1002-1752 → 10/02/2026
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	🟢	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	🟢	All six ER “Populations who should avoid Botox” items present
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	ER uses no ranking notation in contraindications
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	Section 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	🟢	All eleven ER interaction bullets present; no overlap with 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	ER uses no ranking notation in interactions
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	Section 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	🟢	Standard upper-face doses, microdroplet technique, timing and interval
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 actionable protocol aspects
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	🟢	High-tier lines first, then Medium neck bands and oil/pores
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
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	ER provides time-to-effect information

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.	N/A	All four benefit tiers have items

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.	N/A	All four risk tiers have items

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	🟢	All five ER table biomarkers 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	🟢	All six ER qualitative markers listed

Issues 02/10/2026 18:28

Pass rate 100.00%. No issues found.

Issues 02/10/2026 18:24

1. 2.7 — Missing plain-language glosses in interactions: In Key Interactions (lines 558 and 563), “Anticholinergic drugs” and “Zinc with phytase” appear without the ER’s explanatory glosses (“medicines that block acetylcholine”; “an enzyme that frees zinc from plant phytate”), leaving specialist terms unexplained.

Fixes 02/10/2026 18:24

1. 2.7 — Restored interaction plain-language glosses: Changed “Anticholinergic drugs (oxybutynin, …)” to “Anticholinergic drugs (medicines that block acetylcholine: oxybutynin, …)” and “Zinc with phytase” to “Zinc with phytase (an enzyme that frees zinc from plant phytate)”, using the ER’s own glosses.

Issues 02/10/2026 18:22

1. 2.7 — Jargon replaces ER plain wording: The QRS uses “intradermal” in action_2_sub (line 461), marker_4_name (line 639) and qualitative_item_5 (line 684), where the ER uses the plain terms “in-skin use” (ER lines 416, 425) and “tiny skin blebs” (ER line 359).

Fixes 02/10/2026 18:22

1. 2.7 — Jargon replaced with ER wording: Changed “intradermal microdroplets” to “tiny skin blebs” in action_2_sub, and “for intradermal use” to “for in-skin use” in marker_4_name and qualitative_item_5, matching the ER’s plain wording.

Issues 02/10/2026 18:17

1. 2.15 — Lay route phrasing “in-skin”: The QRS voice uses “in-skin” for the intradermal route in action_2_sub (“100–120 in-skin microdroplets per side”, line 461), marker_4_name (“for in-skin use”, line 639) and qualitative_item_5 (“(for in-skin use)”, line 684).

Fixes 02/10/2026 18:17

1. 2.15 — Lay route phrasing replaced: Changed “in-skin” to “intradermal” in action_2_sub (“100–120 intradermal microdroplets per side”), marker_4_name (“for intradermal use”) and qualitative_item_5 (“(for intradermal use)”).

Issues 02/10/2026 18:14

1. 4.3 — Monitoring marker labels paraphrased: Marker names at QRS lines 606, 617, 628 and 639 deviate from the ER Monitoring table (ER lines 413-416), e.g. “pupil-to-lid distance” replaces “marginal reflex distance”, “Pregnancy test (urine or blood hCG)” reorders “Urine or blood pregnancy test (hCG)”, and “forehead or cheek” is dropped from the sebum marker.
2. 11.4 — Time value states duration: [time_3_value] at line 508 (“Less forehead oiliness for six months at higher doses”) gives a duration rather than a time to effect, while the ER’s only onset information for this benefit (pore benefit at two weeks, ER line 178) sits in [time_3_sub].

Fixes 02/10/2026 18:14

1. 4.3 — Marker labels restored verbatim: Restored the ER’s Monitoring table names: “Eyelid position (marginal reflex distance, MRD1)”, “Urine or blood pregnancy test (hCG)”, “Skin oil (sebum) reading, forehead or cheek, for in-skin use”, and removed the inserted comma from the Facial Wrinkle Scale marker.
2. 11.4 — Time value shows onset: Changed [time_3_value] to “Pore benefit at two weeks only, in one split-face trial” and moved the six-month oiliness duration into [time_3_sub].

Issues 02/10/2026 18:10

1. 2.7 — Jargon replaces plain term: The ER’s plain “in-skin” is replaced by “intradermal” in marker_4_name (line 639), qualitative_item_5 (line 684) and action_2_sub (line 461, ER “tiny skin blebs”).
2. 11.4 — Time cell lacks timing: time_3_value (line 508) “Modest, technique-dependent effect lasting months” is a magnitude verdict rather than a time to effect, and time_3_sub (line 511) “pore benefit at two weeks only in one small trial” can be misread as only one trial showing pore benefit (ER line 178 also cites Sayed et al.).

Fixes 02/10/2026 18:10

1. 2.7 — Plain term restored: Replaced “intradermal” with the ER’s “in-skin” in marker_4_name, qualitative_item_5 and action_2_sub (“100–120 in-skin microdroplets per side”).
2. 11.4 — Time cell given timing: Set time_3_value to “Less forehead oiliness for six months at higher doses” and time_3_sub to “Pore benefit at two weeks only in one split-face trial; modest, technique-dependent effect”.

Issues 02/10/2026 18:05

1. 2.15 — Lay route-of-administration phrasing: The sheet’s own voice uses “tiny droplets in the skin” (action_2_sub, line 461) and “for in-skin use” (marker_4_name line 639, qualitative_item_5 line 684) instead of the formal term “intradermal”.
2. 4.2 — Interaction label not verbatim: Line 559 inserts “within months” into the ER bold label “Other botulinum toxin products (abobotulinumtoxinA, incobotulinumtoxinA, rimabotulinumtoxinB)” instead of carrying the time window as a qualifier.
3. 4.3 — Time labels abbreviated or merged: Time-to-effect labels shorten ER benefit headings (“Frown, crow’s feet and forehead lines”, line 483; “Neck bands and jawline”, line 494) and merge two headings into the invented “Oiliness, pores and texture” (line 505).

Fixes 02/10/2026 18:05

1. 2.15 — Formal intradermal route wording: Replaced “tiny droplets in the skin” with “intradermal microdroplets” (action_2_sub) and “for in-skin use” with “for intradermal use” (marker_4_name, qualitative_item_5).
2. 4.2 — Verbatim interaction label restored: Changed “Other botulinum toxin products within months (…)” to “Other botulinum toxin products (abobotulinumtoxinA, incobotulinumtoxinA, rimabotulinumtoxinB; within months)”.
3. 4.3 — Time labels use ER headings: Set time labels to the ER benefit headings “Smoother frown, crow’s feet and forehead lines”, “Smoother neck bands and jawline” and “Less oily skin and smaller-looking pores”; time_3 value/sub now follow that ER item (“Modest, technique-dependent effect lasting months”; texture clause removed).

Issues 02/10/2026 18:02

1. 1.1 — Single-trial pore result generalized: time_3_value (line 508) “Pore benefit at two weeks only” presents one 18-person split-face trial (Shin et al.) as the general pore finding, while the ER also reports pore benefit from Sayed et al. and pooled data and summarizes the effect as “a modest, technique-dependent effect lasting months” (ER line 178).
2. 2.7 — Unexplained ASA classification: stop_items (line 546) “Significant systemic disease (ASA class 3 or higher)” uses the specialist acronym “ASA” without the plain-language explanation the ER gives (American Society of Anesthesiologists physical status, ER line 333).

Fixes 02/10/2026 18:02

1. 1.1 — Pore result no longer generalized: Changed time_3_value from “Pore benefit at two weeks only” to the ER’s net reading “Modest effect lasting months”, and moved the two-week pore result into time_3_sub, attributed to “one small trial”.
2. 2.7 — ASA classification explained: Changed the contraindication qualifier from “(ASA class 3 or higher)” to “(anesthesiologists’ ASA physical status class 3 or higher)”, keeping the threshold.

Issues 02/10/2026 17:58

1. 4.2 / 4.3 — Interaction labels not verbatim: In Key Interactions, the ER bold label “Aminoglycosides” is paraphrased as “Aminoglycoside antibiotics” (QRS line 555), and “Over-the-counter nonsteroidal anti-inflammatory drugs” is abbreviated to “Over-the-counter NSAIDs” (QRS line 561).

Fixes 02/10/2026 17:58

1. 4.2 / 4.3 — Interaction labels restored verbatim: Changed “Aminoglycoside antibiotics (gentamicin, tobramycin, amikacin)” to “Aminoglycosides (injectable antibiotics: gentamicin, tobramycin, amikacin)” and “Over-the-counter NSAIDs (ibuprofen, naproxen; theoretical)” to “Over-the-counter nonsteroidal anti-inflammatory drugs (ibuprofen, naproxen; theoretical)”, matching the ER bold labels.

Issues 02/10/2026 17:54

1. 1.1 / 11.4 — Time-to-effect value unsupported: time_3_value “Weeks to months” (line 508) is not an onset time stated in the ER; the sub-line mixes the only timepoint (“Pore benefit at two weeks only”) with durations (“texture improved for eight weeks”, “less forehead oiliness for six months”).
2. 2.7 — Unnecessary medical jargon: “ptosis” in marker_2_why (line 623) and “blebs” in action_2_sub (line 461) where plain equivalents (“drooping”, “droplets in the skin”) are available in the ER.

Fixes 02/10/2026 17:54

1. 1.1 / 11.4 — Time-to-effect value corrected: Changed time_3_value from “Weeks to months” to “Pore benefit at two weeks only” (the ER’s only timepoint) and moved the durations into time_3_sub (“Texture improved for eight weeks; less forehead oiliness for six months at higher doses”).
2. 2.7 — Jargon replaced with plain terms: Changed “tiny skin blebs” to “tiny droplets in the skin” in action_2_sub, and “Detects ptosis” to “Detects eyelid or brow drooping” in marker_2_why.