Audit: QRS - RLX-201 for Skin Rejuvenation
Audit conducted on 12/10/2026 03:34 using AI4L / Opus 5.5
Summary
| Items | Count |
|---|---|
| Total | 94 |
| Passed | 87 |
| Failed | 0 |
| N/A | 7 |
| 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. | 🟢 | Lede, protocol, time-to-effect, tiers, gates and monitoring all trace to ER text (e.g., Conclusion L397-399, Therapeutic Protocol L309-311, Practical Considerations L344, Monitoring L362-380). |
| 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. | 🟢 | ER cautious qualifiers kept: “(theoretical)” on every gate item, “No established target”, “long-term safety remains unknown”, “may be premature”. |
| 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; benefits stay Low/Speculative, gate severities (caution/monitor) match ER. |
| 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. | 🟢 | Each item sits in the category of its ER section; no modifying factor surfaced as a gate or side effect. |
| 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, NCT IDs, study names, expert names or brand names appear in the QRS. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | “run by its maker” matches ER “developer-run trial” (L131); no 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. | 🟢 | Measured, evidence-first tone mirrors the ER Conclusion. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert yet accessible and data-driven; no alarmism. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents regimens as labelled source options (manufacturer, trial, procedure-priming), not orders. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No language implying medical advice. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | Information is presented, not recommended. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No direct address of the reader. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language; technical terms limited to ER labels and glossed where needed (vehicle, around-the-eye). |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Items are compact; gates carry no rationale or mitigations. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | No “you”/”your” anywhere in the sheet. |
| 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. | 🟢 | Content (regimens, procedure timing, monitoring) suits proactive, risk-aware adults. |
| 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. | 🟢 | Includes effortful elements (baseline photography, elastometry, 3-6 month reassessment). |
| 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 framed for a general population. |
| 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. | 🟢 | Framing weighs thin, single-source evidence against an audience seeking optimization, as the ER does. |
| 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. | 🟢 | No “anti-aging” wording; “aimed at aging skin” is descriptive. |
| 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 or event terms; “side effects” mirrors ER Conclusion wording. |
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 heads, tier labels and table headers unchanged. |
| 3.2 | All “…” from the [qrs_template] are present in the the QRS. | 🟢 | All template data-qrs-var spans present, including page_title, all action/time sets, four tier spans in both cards and marker/qualitative rows. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Non-variable spans (website=evidence_review/audit/full_review), footer and styles unchanged versus template. |
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” | 🟢 | No QRS section uses empty-state text; empty High/Medium tiers are hidden as 12.5/13.5 require. |
| 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 labels (Manufacturer regimen, Trial regimen, Procedure-priming approach) and gate labels reuse ER bold labels. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | Labels are ER-derived; no invented labels. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji indicators in the QRS. |
| 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. | 🟢 | Sections are condensed (gates stripped of rationale/mitigations, tiers compressed to single lines). |
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 <!doctype html> (L2-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 — lines (L3, L13). |
| 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. | 🟢 | Inside HTML comment; not surfaced elsewhere. |
| 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 quoted (contains colon). |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: rlx_201_skin_2026-1012-0007_Opus_ER.md (L4). |
| 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.10.8 matches 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) | 🟢 | qrs_creation_date: 2026-1012-0315. |
| 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. |
| 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. |
| 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, no qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename matches the file name. |
| 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. | 🟢 | All values trimmed and correctly quoted. |
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 &) |
🟢 | “RLX-201 for Skin Rejuvenation - Quick Reference Sheet” (L22). |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | header_topic = canonical_topic (L417). |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 10/12/2026 from 2026-1012-0315 (L421). |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Opus 5.5 (L425). |
| 6.5 | No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. | 🟢 | No extra header content. |
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 | 🟢 | Opens with what it is (lab-made relative of rapamycin used as a skincare ingredient in a face serum) and its use (aging skin) before the verdict. |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses the ER Conclusion’s evidence, benefit and safety points. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | 69 words. |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each fact maps to ER Motivation L38 and Conclusion L397-399. |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms or specialist terms; rapamycin is glossed. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, sample sizes or p-values. |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes or statistics. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Derived from ER “Populations who should avoid RLX-201” (L283-289). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All five ER populations listed. |
| 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. | 🟢 | No rationale, attributions or dash clauses. |
| 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). | 🟢 | Qualifiers kept: “within the past 3 months”, disease examples, “(theoretical)”. |
| 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 these items. |
| 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. |
🟢 | Section populated; ER names populations to avoid. |
| 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 |
🟢 | Derived from ER Key Interactions & Contraindications (L260-281). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Ten ER interactions listed; systemic immunosuppressants omitted as already covered by the contraindication “Systemic immunosuppressive medications within the past 3 months”. |
| 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. | 🟢 | Only label, example list and severity; mitigations and rationale stripped. |
| 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 and supplement lists preserved with severity class. |
| 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 these items. |
| 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. |
🟢 | Section populated; ER names 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 | Section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Derived from ER Therapeutic Protocol (L309-311). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | Manufacturer regimen, trial regimen and procedure-priming are the three main dosing/timing 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 | ER provides more than three actionable aspects. |
| 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 filled from ER text. |
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 | 🟢 | Covers the three ER time points: firmness wk 2, radiance wk 4, sagging/orbital elasticity wk 8-12 (L344). |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by ER benefit order: firmness/elasticity (first Low benefit) before radiance. |
| 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 three distinct time-to-effect aspects. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time fields filled with 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 | ER provides time-to-effect information. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Derived from ER Expected Benefits (L129-177). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four tier variables present. |
| 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. | 🟢 | Headline benefits only. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheticals. |
| 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. | 🟢 | High and Medium spans set to display: none. |
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 (L195-241). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four tier variables present. |
| 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. | 🟢 | Headline risks only; Conflicted markers and magnitudes stripped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parentheticals. |
| 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. | 🟢 | High and Medium spans set to display: none. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from ER Monitoring Protocol & Defining Success (L362-371). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All four ER 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. |
🟢 | Cadence from ER L362-364. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Derived from ER Monitoring qualitative markers (L373-380). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All six ER qualitative markers listed verbatim. |
Issues 12/10/2026 03:34
Pass rate 100.00%. No issues found.
Issues 12/10/2026 03:31
- 2.7 — Unexplained collagen biostimulators jargon: The Key Interactions item “Fillers and collagen biostimulators: monitor (theoretical)” (QRS line 563) leaves “collagen biostimulators” unexplained and without examples; the ER’s plain-language gloss “(injectables that prompt the skin to make collagen)” (ER line 281) was dropped.
Fixes 12/10/2026 03:31
- 2.7 — Collagen biostimulators gloss restored: Changed “Fillers and collagen biostimulators: monitor (theoretical)” to “Fillers and collagen biostimulators (injectables that prompt the skin to make collagen): monitor (theoretical)”, restoring the ER’s plain-language explanation.
Issues 12/10/2026 03:29
- 2.8 — Dangling source reference in protocol: action_3_sub (QRS line 472) reads “same source elsewhere suggests 2–3 months of use”, referring to a source never named on the sheet, and is the least compact protocol sub.
Fixes 12/10/2026 03:29
- 2.8 — Dangling source reference removed: Changed action_3_sub from “…; same source elsewhere suggests 2–3 months of use, stopping at least 2 weeks before” to “Stopping 2 days before, restarting after healing; alternatively 2–3 months of use, stopping at least 2 weeks before”.
Issues 12/10/2026 03:23
- 1.3 — Procedure timing conflict omitted: Protocol action_3 (lines 469-472) gives only “2–4 weeks before peels or lasers” and “Stopping 2 days before”, while the ER notes the same source elsewhere suggests 2–3 months of use, stopping at least 2 weeks before, presenting conflicting guidance as settled.
Fixes 12/10/2026 03:23
- 1.3 — Procedure timing conflict restored: Changed action_3_value to “2–4 weeks of use before peels or lasers” and added to action_3_sub that the same source elsewhere suggests 2–3 months of use, stopping at least 2 weeks before.
Issues 12/10/2026 03:22
- 1.3 — Pregnancy test scope broadened: The Monitoring row “Pregnancy test (urine hCG)” (lines 604–610) omits the ER’s restriction “only for women who could become pregnant” (ER Monitoring table and baseline paragraph), implying the test applies to every user.
- 9.5 — EGCG example list garbled: Line 560 renders the ER’s “EGCG (epigallocatechin gallate, a green tea compound)” as “EGCG, a green tea compound”, so “a green tea compound” reads as a fifth separate supplement in the example list.
Fixes 12/10/2026 03:22
- 1.3 — Pregnancy test scope restored: Changed marker_1_name from “Pregnancy test (urine hCG)” to “Pregnancy test (urine hCG), only for women who could become pregnant”, matching the ER’s restriction.
- 9.5 — EGCG example list clarified: Changed “EGCG, a green tea compound” to “EGCG (a green tea compound)” so the descriptor attaches to EGCG instead of reading as a separate list item.
Issues 12/10/2026 03:17
- 2.7 — Unexpanded acronym EGCG: The Key Interactions item at line 560 lists “EGCG” without the plain-language explanation the ER gives (“epigallocatechin gallate, a green tea compound”).
Fixes 12/10/2026 03:17
- 2.7 — Unexpanded acronym EGCG: Changed “(resveratrol, curcumin, berberine, EGCG)” to “(resveratrol, curcumin, berberine, EGCG, a green tea compound)” in the Key Interactions supplements item, following the ER’s own explanation.