Audit: QRS - sh-Polypeptide-59 for Hair Regrowth
Audit conducted on 11/09/2026 00:00 using AI4L + evidence-mcp / GPT 6
Summary
| Items | Count |
|---|---|
| Total | 97 |
| Passed | 90 |
| 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. | 🟢 | Every populated claim is traceable to the named ER; quantities and categories match. |
| 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. | 🟢 | Cautious qualifiers remain in the lede, inferred avoidance gates, unvalidated dose, unavailable time estimate and illustrative monitoring. |
| 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 certainty, efficacy, safety or clinical instruction exceeds the ER wording. |
| 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. | 🟢 | No benefit/risk modifier is promoted into an interaction, contraindication 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 unsupported identifier or attribution occurs. |
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. | 🟢 | The sheet retains the ER cautious, evidence-centered tone. |
| 2.2 | The tone of the QRS is expert, accessible, objective, and data-driven | 🟢 | Content is factual, accessible and objective. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | No personalized prescription or authoritative treatment plan appears. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | Populated text reports evidence and illustrative monitoring; the fixed disclaimer remains intact. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No recommending or advising language is introduced. |
| 2.6 | The QRS never addresses the reader directly — it presents evidence, not guidance | 🟢 | No direct address in variable content; the template disclaimer is unchanged. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language predominates, with technical condition labels retained as required. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Cards contain compact summaries without study narratives. |
| 2.9 | 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. | 🟢 | Objective tracking and uncertainty suit proactive, risk-aware adults. |
| 2.10 | The target audience is willing to employ lifestyle and behavioral changes as well as follow protocols that may be inconvenient, costly, or require effort. | 🟢 | Sustained photographic tracking acknowledges willingness to invest effort. |
| 2.11 | 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 assumption that readers reject effortful protocols shapes the content. |
| 2.12 | 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. | 🟢 | Willingness to act does not distort the speculative benefit or indirect safety evidence. |
| 2.13 | 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 framing appears. |
| 2.14 | 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. | 🟢 | Uses topical cosmetic use and injection terminology, without colloquial route language. |
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 card, gate, tier and column headings match the template. |
| 3.2 | Every element carrying a data-qrs-var attribute in [qrs_template] is present in the QRS with the same name | 🟢 | All required named spans remain; marker and qualitative patterns are numbered under their specific rules. |
| 3.3 | Everything outside the data-qrs-var spans — markup, text, styles, comments — is as in the template; spans that no checklist item addresses are left unchanged as well | 🟢 | Styles, fixed text and surrounding structure match; changes are metadata population, required repeats and permitted hiding. |
4. Formatting
| # | Description | Result | Comments |
|---|---|---|---|
| 4.1 | An empty ER section never produces visible empty-state text in the QRS: the corresponding region is hidden or left empty. Phrases such as “None documented in human trials to date” or “Not formally studied” appear only where the ER uses them for a fact the QRS carries over. | 🟢 | Empty tiers are hidden and the documented interaction list is empty; unavailable protocol facts are explicitly present in the ER. |
| 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. | 🟢 | Bold ER labels carry verbatim into gates, action labels, time label and qualitative entries. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No source label has been invented, shortened or paraphrased. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No QRS emoji indicator appears. |
| 4.5 | The QRS is designed to render on one A4 page. It fails this item only for one of four things: a trailing clause after a dash, an optional gloss, an example list left untrimmed, or a repetition. Nothing else is cut to fit. | 🟢 | No removable trailing dash clause, optional gloss or repetition; interaction exposures are distinct decision-relevant categories with one drug example. |
5. Metadata
| # | Description | Result | Comments |
|---|---|---|---|
| 5.1 | The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. | 🟢 | The metadata comment follows the doctype directly. |
| 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. | 🟢 | Two standalone YAML delimiters enclose the fields. |
| 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. | 🟢 | YAML remains invisible inside the comment; only prescribed header variables render. |
| 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 are trimmed; quoted duration contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | The named ER basename matches the staging source supplied for this audit. |
| 5.6 | Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” | 🟢 | 26.11.8 matches the QRS prompt 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-1108-2356 follows the required date pattern. |
| 5.8 | The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” | 🟢 | Creator nickname field is GPT. |
| 5.9 | The nickname of the AI is the full name without the version number, with all remaining words joined by hyphens (e.g., Opus, Sonnet, Grok, Gemini-Flash, GPT); when the full name has no version number or is “Unknown”, the nickname equals the full name | 🟢 | GPT equals the fullname with version removed. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | Creator fullname field is GPT 6. |
| 5.11 | The full name of the AI consists of the model name (the word or words directly before the version number, leaving out the first if there is more than one, e.g., Claude Opus 5.5 → Opus 5.5), the model version number and the variant (if any) as stated in the system prompt or developer instructions of the creating model, with every word capitalized and without product, effort or pricing names (e.g., Opus X.Y, Sonnet X.Y, Grok X.Y, Gemini X.Y Flash, GPT X.Y), the model name alone when the system prompt or developer instructions name a model without a version number (e.g., Grok), or “Unknown” when neither the system prompt nor the developer instructions of the creating model name a model | 🟢 | GPT 6 conforms to the model identity explicitly provided in instructions. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | The metadata filename equals the audit target basename. |
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 &) |
🟢 | Title equals canonical_topic plus the required Quick Reference Sheet suffix. |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | Header equals the canonical topic in ER frontmatter. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 11/08/2026 corresponds to the QRS creation date. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | Header GPT 6 equals creator 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. | 🟢 | Header contains only template content and prescribed variables. |
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 | 🟢 | The first sentence identifies a cosmetic protein ingredient and its hair-regrowth use. |
| 7.2 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses the conclusion into speculative benefit, indirect safety and unvalidated concentrations. |
| 7.3 | [at_a_glance] is no longer than 70 words | 🟢 | Lede is below the 70-word limit. |
| 7.4 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Ingredient identity/use comes from Motivation; remaining facts map to the three Conclusion paragraphs. |
| 7.5 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No specialist acronym or classification appears; animal/cell experiments and wound gel are understandable terms. |
| 7.6 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No specific trial details appear. |
| 7.7 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect size or statistical result appears. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Both entries derive directly from Key Interactions & Contraindications. |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | Both avoidance populations are represented. |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each entry is a separate li element. |
| 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. | 🟢 | Only exact condition labels and the essential inferred-avoidance qualification remain. |
| 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). | 🟢 | Application-site and formulation-specific qualifiers are preserved. |
| 8.6 | When the ER uses ranking notation inside parens (e.g., “>” for severity ordering) that depends on an explanatory phrase to interpret, normalize the items to a plain comma-separated list rather than carrying through the bare symbol. | 🟢 | No ranking notation requires normalization. |
| 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 gate is populated because the ER identifies avoidance populations. |
| 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 | Gate is not empty. |
9. Key Interactions
| # | Description | Result | Comments |
|---|---|---|---|
| 9.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | The interaction list derives from the named ER gate section. |
| 9.2 | [caution_items] represent the ER’s documented interactions — the items under its “Documented interactions:” label — excluding any that are already listed as Contraindications and any entry phrased as no interaction found | 🟢 | Documented interactions is empty, matching the ER None identified entry. |
| 9.3 | [caution_theoretical_items] represent the ER’s theoretical interactions — the items under its “Theoretical interactions (inferred from mechanism, not studied in humans):” label | 🟢 | The theoretical barrier-disruption interaction is represented. |
| 9.4 | The ER placeholder “None identified” is never an item: it means that group is empty | 🟢 | None identified occurs only in a nonvisible explanatory comment. |
| 9.5 | Individual [caution_items] and [caution_theoretical_items] are formatted as <li></li>. The template’s bold “Theoretical (inferred from mechanism)” sub-heading is the only marker of the second list’s status: no item carries “(theoretical)”, “inferred from” or a mechanism clause | 🟢 | li markup is used; the template heading alone marks theoretical status. |
| 9.6 | 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 the treatment categories and drug example remain, without mechanism or study elaboration. |
| 9.7 | 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). | 🟢 | Microneedling, ablative lasers, irritating topicals and tretinoin preserve exposure applicability. |
| 9.8 | 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 requires normalization. |
| 9.9 | If the ER’s theoretical group is empty, the whole Theoretical block — the caution_theoretical span with its sub-heading and list — is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | The ER theoretical group is populated. |
| 9.10 | 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 interaction section is populated for the identified exposure. |
| 9.11 | 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, and the Theoretical block is hidden per 9.9. E.g. | N/A | The entire interaction section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Therapeutic Protocol section |
🟢 | All three cells derive from Therapeutic Protocol. |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from that section | 🟢 | Dose, route and timing are core implementation aspects. |
| 10.3 | If fewer than three distinct actionable implementation aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
N/A | Three distinct implementation aspects are available. |
| 10.4 | All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from that section. | 🟢 | All used labels, values and subtexts contain meaningful ER-derived information. |
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 sole ER time-to-effect aspect is represented. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | The single aspect concerns the sole speculative hair benefit. |
| 11.3 | If fewer than three distinct time-to-effect aspects are mentioned in the ER, the unused sets are left empty and hidden with style="display:none", not filled with placeholder text or empty-state phrasing. |
🟢 | Two unused time cells are empty and hidden. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | Used cell preserves the lack of reliable human timing and the animal extrapolation limitation. |
| 11.5 | If the ER provides no information on time to effect at all, the whole Time to effect block (its subhead and all three sets) is hidden with style="display:none", not removed: its spans stay in place, empty. |
N/A | The ER explicitly discusses time to effect. |
12. Benefits
| # | Description | Result | Comments |
|---|---|---|---|
| 12.1 | The section is derived from the ER Expected Benefits section |
🟢 | Speculative Hair Regrowth matches Expected Benefits. |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four benefit variables are retained. |
| 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. | 🟢 | Only the benefit name appears within its tier. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical benefit detail remains. |
| 12.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
🟢 | High, Medium and Low benefit spans are hidden. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Two Low risks and one Speculative risk match Potential Risks & Side Effects. |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four risk variables remain. |
| 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. | 🟢 | Risk entries contain only key names; tiers carry evidence strength. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No parenthetical risk detail remains. |
| 13.5 | If a tier (high, medium, low, speculative) has no items, its span is hidden with style="display:none", not filled with “None documented in human trials to date” or similar empty-state phrasing. |
🟢 | Empty High and Medium risk spans are hidden. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | Both markers and cadence derive from Monitoring Protocol & Defining Success. |
| 14.2 | All measurable/quantifiable biomarkers from that section are listed, one table row per marker; the template’s # row is the pattern, repeated with # replaced by 1, 2, 3 … in the data-qrs-var names |
🟢 | Both ER table markers are present in separate numbered rows. |
| 14.3 | [marker_#name] is the marker, [marker#target] its target value or range as given in the ER, [marker#_why] its purpose in a few words; a target the ER does not give is written “Not specified in the ER” | 🟢 | Names, stated tracking targets and purposes match the source table. |
| 14.4 | [monitoring_cadence] is populated with the monitoring cadence/frequency derived from that section. It is not left with placeholder text or empty. | 🟢 | Baseline/monthly photographs and three/six-month review retain the illustrative, unvalidated status. |
| 14.5 | If the ER names no measurable biomarker, the table is hidden with style="display:none" and the single # row is left as in the template |
N/A | The ER supplies two measurable markers. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring Protocol & Defining Success section |
🟢 | All three entries derive from the monitoring section. |
| 15.2 | All subjective/qualitative markers from that section are listed, one <li> per marker; the template’s # item is the pattern, repeated with # replaced by 1, 2, 3 … |
🟢 | Appearance, Tolerability and Attribution each have their own li and numbered variable. |
| 15.3 | If the ER names no qualitative marker, the card’s list is hidden with style="display:none" and the single # item is left as in the template |
N/A | The ER supplies qualitative markers. |
Issues 11/09/2026 00:00
Pass rate 100.00%. No issues found.
Issues 11/08/2026 23:58
- 8.4 — Contraindication explanations retained: The Contraindications span retains absence-of-harm-study and allergy-threshold/testing explanations after the inferred-avoidance qualification. These elaborations exceed the required concise decision gate.
Fixes 11/08/2026 23:58
- 8.4 — Contraindication explanations removed: Removed the harm-study and allergy-threshold/testing explanations from both contraindications. Preserved both exact condition labels and the qualification that avoidance is inferred.