Audit: QRS - Platelet-Rich Plasma for Skin Rejuvenation

Audit conducted on 23/09/2026 03:23 using AI4L / Opus 5.5

Iterations

Summary

Items	Count
Total	94
Passed	89
Failed	0
N/A	5
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.	🟢	All QRS content traces to ER text (Conclusion, Protocol, Practical Considerations, Key Interactions & Contraindications, Expected Benefits, Potential Risks, Monitoring)
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 phrasing kept where carried over, e.g. “No established target; track change from own baseline”, “activation with calcium chloride is optional”
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”).	🟢	Lede keeps “results for aging skin are mixed”; contraindications keep ER thresholds and windows unchanged
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, interactions, benefits and risks each drawn from their matching ER sections
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 PubMed IDs, citations, expert names, NCT IDs or brand names appear in the QRS
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.	🟢	Measured, evidence-weighted 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	🟢
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	🟢	No direct reader address
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Lede and descriptors use plain language; technical terms retained only where they are ER labels or preserved gate qualifiers, some glossed (e.g. “Leukocyte-poor (low white-cell)”)
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.	🟢	Lede frames value as an add-on to scar/laser treatment, matching the ER’s audience-specific weighting
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
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.	🟢	Formal terms used (“Injection-site”, “Oral corticosteroids”, “Oral isotretinoin”); no colloquial route-of-administration phrasing

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 labels, headings, tier labels and column headers match the template
3.2	All <span data-qrs-var="NAME">...</span> from the [qrs_template] are present in the the QRS.	🟢	All template spans present; marker_# and qualitative_item_# expanded to numbered spans (1-7, 1-6)
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff against template shows only addressed variables changed; Medium spans hidden per 12.5/13.5

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”	🟢	Only empty ER sub-sections are the Medium tiers, handled by the tier-specific display:none rule (12.5/13.5); no other mapped ER section is empty
4.2	Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label.	🟢	Interaction and protocol labels use ER bold labels (e.g. “Standard series”, “Preparation”, “Supplements with antiplatelet effects”)
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time labels derived from ER wording (“full results”, “texture changes”, “collagen remodeling”)
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji indicators
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 condensed per section; no second-page structure

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.	🟢	Line 2 comment directly follows 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.	🟢	Lines 3 and 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.	🟢
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.	🟢	duration quoted because it contains a colon
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]”	🟢	26.9.22 matches QRS.md version
5.7	Creation date and time of the document is stated as “qrs_creation_date: [YYYY-MMDD-HHMM]” (e.g., 2026-0501-1430)	🟢	2026-0923-0316
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)	🟢	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]”	🟢
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
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 &)	🟢	“Platelet-Rich Plasma 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]	🟢	09/23/2026
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Opus 5.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.	🟢

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 “Platelet-rich plasma is a procedure that concentrates platelets from a person’s own blood … used for wrinkles, rough texture and acne scars”
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses ER Conclusion: add-on value, mixed stand-alone results, side effects, operator-dependent serious harms
7.3	[at_a_glance] is no longer than 70 words	🟢	Exactly 70 words
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each fact maps to ER Conclusion paragraphs 1-3 or Motivation line 38
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	Uses “add-on”, “depressed acne scars”, “laser treatment”
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 9 ER “Populations who should avoid” items listed
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.	🟢	ER trailing rationales (e.g. “which impair platelet function…”, “for which no safety data exist”) 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).	🟢	Thresholds and windows kept: 100,000 per microliter, 10 g/dL, Child-Pugh Class B or C, INR above 3.0, 2 weeks / 1 month
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.	🟢	No ranking notation in ER
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.	🟢	ER names populations to avoid; section 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. <!-- empty: ER names no population that should avoid the intervention -->	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	🟢	8 of 9 ER interactions listed; systemic corticosteroids omitted as covered by the corticosteroid contraindication
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.	🟢	Text after ER em-dashes stripped; only drug class, examples and severity kept
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 and the isotretinoin microneedling/laser qualifier preserved
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.	🟢	No ranking notation in ER
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.	🟢	ER names interactions; section 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. <!-- empty: ER names no interaction that changes how the intervention is used -->	N/A	Section is not empty

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	From ER Therapeutic Protocol
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Standard series, preparation and microneedling delivery (tied to the High-tier acne-scar benefit)
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.	🟢

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	🟢	Full results (3-4 months), texture changes (4-12 weeks), collagen remodeling (3-6 months) from ER Practical Considerations and Half-life bullet
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Overall results first, then texture (Low tier), then collagen remodeling (Speculative tier)
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 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]	🟢	Medium hidden with display: none
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.	🟢	Items reduced to ER headings; effect sizes and flags removed
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content
12.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	🟢	benefits_medium set to display: none, no empty-state text

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]	🟢	Medium hidden with display: none
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.	🟢	Items reduced to ER headings
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content
13.5	If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing.	🟢	risks_medium set to display: none, no empty-state text

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 7 ER table biomarkers listed with ER targets and reasons
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 reflects ER baseline, per-session, 1-month, 6-monthly and annual CBC schedule

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 6 ER qualitative markers listed verbatim

Issues 23/09/2026 03:23

Pass rate 100.00%. No issues found.

Issues 23/09/2026 03:18

1. 2.7 — Unglossed specialist terms: The headline protocol value “Leukocyte-poor plasma” (line 458) and the contraindication “active herpes labialis” (line 544) are presented without the plain-language glosses the ER provides (“low white-cell”, “recurrent lip blisters”).
2. 9.4 — Trailing em-dash clauses kept: All Key Interactions items (lines 558–565) retain the ER’s content that follows the em-dash (e.g., “caution; more bruising and hematoma”), re-punctuated with a semicolon instead of being stripped.

Fixes 23/09/2026 03:18

1. 2.7 — Unglossed specialist terms: Changed “Leukocyte-poor plasma” to “Leukocyte-poor (low white-cell) plasma” and “active herpes labialis” to “active herpes labialis (recurrent lip blisters)”, using the ER’s own glosses.
2. 9.4 — Trailing em-dash clauses kept: Stripped the post-em-dash effect clauses from all eight Key Interactions items, keeping the label, example drug lists, severity term and the isotretinoin combination qualifier (e.g., “caution; more bruising and hematoma” became “caution”).