Audit: QRS - Topical Troxerutin for Skin Rejuvenation

Audit conducted on 21/09/2026 14:24 using AI4L / Opus 5

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. 🟢 Every span traces to ER text: protocol cells to ER Therapeutic Protocol, time cells to ER Practical Considerations, benefit/risk items to ER tier headings, markers and cadence to ER Monitoring Protocol & Defining Success.
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. 🟢 “No established target; track change from own baseline” mirrors the ER; the at-a-glance keeps the ER’s “Nothing measured on wrinkles, firmness, pigmentation or collagen”.
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”). 🟢 Contraindication time windows (7 days / 14 days) and the “no facial study compared it against its own base cream” caveat are carried at full strength.
1.4 The QRS does not relabel an ER fact under a different decision category. A “Benefit-Modifying Factor” from ER section is not surfaced as a “Caution”; a “Risk-Modifying Factor” is not surfaced as a “Side Effect”; etc. 🟢 Contraindications come from the ER’s “Populations who should avoid” list, Key Interactions from the ER’s interaction bullets; no modifying factor is promoted into a gate.
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 or author names appear. “Venoruton sachets” and “Baker-Gordon” appear in the ER for the same facts.
1.6 The QRS does not introduce new attributions. 🟢 No attributions present.

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. 🟢 Sober, evidence-bounded register matching the ER.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Measured outcomes and concentrations are given alongside the limits of the evidence.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Statements are descriptive (“Split twice-daily application is standard”), not prescriptive.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperative instruction to the reader anywhere on the sheet.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No “recommend”/”advise”/”should” constructions.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the sheet.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms retained are biomarker names carried from the ER’s monitoring table; the at-a-glance is entirely plain.
2.8 Information is presented in a concise and very compact manner 🟢 All items are single clauses or short semicolon-joined lists.
2.9 It DOES NOT address the reader directly 🟢 Confirmed across all spans.
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. 🟢 Instrument thresholds, concentration ranges and patch-test protocol assume a proactive, measurement-oriented user.
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. 🟢 Twice-daily application and a six-marker monitoring set at four timepoints are presented without hedging on 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. 🟢 No simplification toward a casual consumer.
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 at-a-glance foregrounds the vehicle-control gap, which is the decision-relevant point 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. 🟢 The string “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. 🟢 “Oral anticoagulants”, “topical corticosteroids”, “systemic adverse effects” used; no colloquial route-of-administration 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 present verbatim (lines 446, 492, 541, 567, 584, 611, 632, 636–638, 737); tier labels on used tiers unchanged.
3.2 All “” from the [qrs_template] are present in the the QRS. 🟢 57 spans present; every template variable name is represented, with marker_#* expanded to 1–6 and qualitative_item# to 1–5.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Diff against the template shows head, CSS and all non-variable markup byte-identical.

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; the absent benefit/risk tiers are governed by items 12.5 and 13.5 instead.
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 concentration”, “Application frequency” and “Dermocosmetic approach” are the ER’s bold labels verbatim.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Marker names match the ER biomarker table; time-to-effect cell labels are drawn from the ER’s own wording (“redness on capsaicin challenge”, “sensitivity scores”, “barrier and hydration readings”).
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji in the file; the ER’s ⭕️ and ⚠️ markers 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. 🟢 Every section is condensed to headings or single clauses; no section carries ER elaboration.

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. 🟢 Lines 2–14, immediately after the doctype.
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 --- at line 3, closing --- at line 13.
5.3 The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. 🟢 Enclosed in an HTML comment; no duplicate on the page.
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. 🟢 Only duration: "00:02" is quoted, and it contains a colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 Line 4.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 Line 5, 26.9.11, matching 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) 🟢 Line 6, 2026-0921-1411.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 Line 7.
5.9 The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) 🟢 Opus.
5.10 The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” 🟢 Line 8.
5.11 The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) 🟢 Opus 5.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 Line 9, 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 for all twelve 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., &amp; for &) 🟢 “Topical Troxerutin for Skin Rejuvenation - Quick Reference Sheet”; no entity encoding required.
6.2 [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., &amp; for &) 🟢 Line 417.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 09/21/2026 from 2026-0921-1411.
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 holds only the title and the template subline.

7. At-A-Glance Section

# Description Result Comments
7.1 [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section 🟢 Compresses all four Conclusion paragraphs into what was measured, what was not, and the structural weakness.
7.2 [at_a_glance] is no longer than 60 words 🟢 59 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct Conclusion sentence (ER lines 424, 426, 430).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 “leaky small blood vessels”, “firmer barrier”, “higher surface water” — no acronyms or clinical-register terms.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial identifiers.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 Direction-only wording throughout.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Sourced from the “Populations who should avoid Topical Troxerutin” list (ER lines 273–281).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All four ER populations are present.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Four <li> elements (lines 570–579).
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. 🟢 ER trailing clauses (“a positive patch test to…”, “while the barrier is absent”, “in whom the surface-area-to-weight ratio…”) are all stripped.
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). 🟢 7-day and 14-day windows, “(Baker-Gordon type)” and “under 3 years” all retained.
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 uses no ranking notation in this section.
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. 🟢 The ER names four such populations and the section is correctly populated.
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.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Sourced from ER lines 259–271.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All seven ER interaction bullets present; the skin-procedures item is the ER’s general interaction bullet, distinct from the time-windowed contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Seven <li> elements (lines 587–601).
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. 🟢 The ER’s caution/monitor verdicts and mechanistic sentences are stripped; only the agent class and examples remain.
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). 🟢 Every named drug list is retained (tretinoin/adapalene/tazarotene; brimonidine/oxymetazoline; warfarin/apixaban/aspirin; etc.); only the explanatory glosses 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 uses no ranking notation in this section.
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. 🟢 The ER names seven interactions and the section is correctly populated.
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.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells trace to ER Therapeutic Protocol bullets (ER lines 299–315).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Concentration, frequency and vehicle are the three decisions that must be made before use.
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 supplies more than three; 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. 🟢 Nine spans populated (lines 450–487), each traceable to an ER protocol bullet.

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 🟢 The ER’s time-to-effect bullet names exactly three: redness on challenge, barrier/hydration, sensitivity score — all three are carried.
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Redness and sensitivity (Medium-tier benefit) precede barrier and hydration (Low-tier 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 Three distinct aspects exist and 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. 🟢 Nine spans populated (lines 498–533), wording drawn from ER line 359.
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 does provide time-to-effect information.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 Items are the ER’s benefit sub-headings.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present (lines 543–560).
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. 🟢 Headings only, semicolon-joined; no magnitudes or evidence notes carried.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals remain; the ER’s “Not Central to Skin Rejuvenation” markers are dropped.
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. 🟢 The ER states “No benefit reaches High”; benefits_high carries style="display: none" with no empty-state text (line 543).

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 Items are the ER’s risk sub-headings.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present (lines 613–626).
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. 🟢 The risk ratio 1.14 and the injection-cohort details stay in the ER and are not carried over.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheticals remain; the “Conflicted” marker is dropped.
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. 🟢 The ER states no risk reaches High or Medium; both spans carry style="display: none" with no empty-state text (lines 613–614).

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows mirror the ER biomarker table (ER lines 389–396).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All six ER biomarkers present, with targets and rationale carried across.
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. 🟢 “Full set at baseline, then repeated at 2 weeks, 4 weeks and 8 weeks, then every 3 months while use continues.” matches ER line 387.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Items taken from the ER’s “Qualitative markers worth tracking” list (ER lines 400–404).
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All five ER qualitative markers present, verbatim (lines 740–765).

Issues 21/09/2026 14:24

Pass rate 100.00%. No issues found.

Issues 21/09/2026 14:21

  1. 1.1 — Standard concentration value unsupported: [action_1_value] on line 453 gives “1–10%” for the ER label “Standard concentration”, but the ER states the pharmaceutical gel is standardized at 2% with a tested facial range of 0.0095–10%; “1–10%” is the ER’s dermocosmetic-emulsion figure and contradicts the QRS’s own sub-text on lines 457–458.

Fixes 21/09/2026 14:21

  1. 1.1 — Standard concentration value corrected: Changed [action_1_value] from “1–10%” to “2%”, the ER’s stated pharmaceutical standard for the label “Standard concentration”, and reworded the opening of [action_1_sub] from “Pharmaceutical gel is standardized at 2%.” to “The pharmaceutical gel standard.” so the cell no longer contradicts itself.

Issues 21/09/2026 14:16

  1. 3.3 — Unclosed sub-cell divs in protocol panel: The closing </div> of every <div class="sub"> was dropped in all six protocol-panel cells (lines 460, 473, 486, 504, 517, 529), leaving 44 opening against 38 closing <div> tags in the body and nesting each .pcell inside the previous cell’s sub text; the template is balanced at 44/44.

Fixes 21/09/2026 14:16

  1. 3.3 — Restored protocol sub-cell closing divs: Added the missing closing </div> for each <div class="sub"> in all six protocol-panel cells (three action cells, three time-to-effect cells), restoring the template’s 44/44 <div> balance and un-nesting the .pcell blocks.