Audit: QRS - Vilon for Health & Longevity

Audit conducted on 21/09/2026 06:00 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.	🟢	Spot-checked every populated span against the ER: protocol values (ER 331, 333, 339), gate items (ER 281-307), benefit/risk tiers (ER 141-261), all 12 monitoring rows (ER 412-423) and all 7 qualitative markers (ER 427-433) are literally supported.
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 ER phrasing carried through: “no head-to-head comparison of schedules exists”, “no chronobiology data exist”, “No study reports a time-to-effect for any subjective change”, “No established target”.
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 strengthening or softening. Contraindication windows (five years, 30 days, two weeks, INR >3.0, platelets <50 x 10^9/L) and the “Morning” timing caveat are reproduced at ER 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.	🟢	Categories preserved: ER “Populations who should avoid Vilon” -> Contraindications; ER Key Interactions bullets -> Key Interactions; ER benefit/risk tiers -> Benefits/Risks. No Benefit- or Risk-Modifying Factor is surfaced as 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 identifiers, study citations or expert names appear. Named drugs and bioregulator brand names (Epitalon, Thymalin, Cortexin) all appear in the ER for the same fact (ER 281-297).
1.6	The QRS does not introduce new attributions.	🟢	No attribution of any kind is introduced; the sheet names no investigator, institute or publication.

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.	🟢	Matches the ER’s restrained, evidence-weighing register throughout.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert, objective and data-driven; the negative balance mirrors the ER rather than editorialising.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presents findings and ranges; the prescriptive-sounding phrases (“needs checks”, “warrant stopping”) are verbatim ER carry-overs required by 14.3 and the ER monitoring table.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No advice language in the QRS’s own voice; the footer disclaimer is the unmodified template text.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommend”, “advise” or “guidance” wording anywhere in the sheet.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns; verified by search for you/your across the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language; the remaining technical terms are biomarker names mandated verbatim by 14.2 (e.g. antithrombin III, CD4:CD8 ratio).
2.8	Information is presented in a concise and very compact manner	🟢	Tier lists are collapsed to semicolon-separated key facts; gate items are bare noun phrases; protocol cells are label/value/sub triplets.
2.9	It DOES NOT address the reader directly	🟢	Confirmed - no direct address anywhere.
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.	🟢	Framed for risk-aware self-directed adults: decision gates, dose arithmetic and a 12-marker panel.
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.	🟢	Assumes willingness to run injected courses, obtain specialist flow cytometry and epigenetic age testing.
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 pitched at the general population; no simplification of the safety gates.
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.	🟢	Risk/benefit weighting reflects the audience: the tumour-promotion signal and cancer-screening gate are surfaced prominently against three small unreplicated human reports.
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; framing is longevity/health throughout. Verified by search.
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 register: “Subcutaneous or intramuscular injection”, “insulin-releasing tablets”, “hypoglycaemia”, “analgesics”. The one lay-sounding phrase, “low blood sugar” in marker_8_why, is verbatim ER table text (ER 419).

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 present unmodified: Protocol, Time to effect, Benefits, Risk & Side Effects, Monitoring, Qualitative Assessment, Contraindications, Key Interactions, Marker/Target/Why, and the Medium/Low/Speculative tier labels.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 named template spans plus the repeated marker_#* and qualitative_item# spans are present; set-difference against the template returns nothing missing.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff of lines 1-413 against the template shows only frontmatter values and the title; CSS, comments, the website=”…” spans and the footer are 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 empty benefit/risk tiers are sub-sections and are governed by 12.5 / 13.5, which mandate display:none rather than empty-state phrasing.
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.	🟢	ER bold labels reproduced verbatim: “Standard course as used by the originating group”, “Alternative every-other-day schedule”, “Best time of day”, and all seven qualitative labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No ER label is paraphrased or abbreviated. The three Time-to-effect labels are descriptive cell headers for a single ER bullet that carries no per-item bold labels.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji anywhere in the file; the ER’s tier squares and the two “warning Conflicted” markers are dropped as required.
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 discretionary section is already at bare-phrase density; remaining length is driven by the completeness rules 8.2, 9.2, 14.2 and 15.2, which forbid dropping items.

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.	🟢	Single HTML comment at lines 2-14, immediately after <!doctype html> and before any other content.
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 opened at line 3 and closed at line 13; the preceding comment text is outside the block.
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 an HTML comment, so it does not render; no value is echoed by any visible element.
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.	🟢	All values trimmed and unquoted except duration: “00:03”, which contains a colon and therefore requires quoting.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: vilon_2026-0921-0350_Opus_ER.md.
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: qrs_prompt_version: 26.9.11, matching the QRS.md version badge.
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: qrs_creation_date: 2026-0921-0547, in YYYY-MMDD-HHMM form.
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: 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)	🟢	“Opus” is a single word with no version or qualifier.
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: qrs_creator_ai_fullname: Opus 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)	🟢	“Opus 5” = nickname plus version number, no additional qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: vilon_2026-0921-0350_Opus_QRS.html, matching 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.	🟢	Re-verified: no stray whitespace or unnecessary quoting in any frontmatter value.

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 &)	🟢	Line 22: “Vilon for Health & Longevity - Quick Reference Sheet”, with the ampersand entity-encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	Line 417: “Vilon for Health & Longevity”, matching canonical_topic in the ER frontmatter.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 09/21/2026, the MM/DD/YYYY form of qrs_creation_date 2026-0921-0547.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching qrs_creator_ai_fullname.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	Header carries only title, creation date, the AI4L link and the model name; no badge, AKA line, version stamp or audit date.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses the ER Conclusion (ER 455-461): origin and intent, the internally consistent laboratory/mouse work, the three unreplicated human reports, and the two counter-findings.
7.2	[at_a_glance] is no longer than 60 words	🟢	59 words, counted programmatically.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to a distinct Conclusion passage: ER 455 (origin/intent), 457 (laboratory and mouse work, three reports, not repeated), 459 (breast tumours, cancelled chemotherapy effect).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms or specialist classifications; “two-amino-acid molecule”, “thymus extracts”, “tumour-prone mice” are plain-language.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No study name, year, sample size or p-value.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect size, relative risk or statistical result.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Sourced from the ER “Populations who should avoid Vilon” list inside Key Interactions & Contraindications (ER 299-307).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoidance populations are represented, one <li> each.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <li> elements inside the stop_items span (lines 569-592).
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.	🟢	“Anyone with / Anyone receiving / Carriers of” stems trimmed; no trailing dash clause, rationale or citation survives.
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 preserved: five years post HER2-positive diagnosis, 30 days from the last cycle, prednisone 20 mg daily for two weeks or longer, DAS above 5.1, INR above 3.0, platelets below 50 x 10^9/L, under 18 years.
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 inside parentheses 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.	🟢	Section is populated, and the ER does identify avoidance populations, so the ONLY IF constraint is satisfied.
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 left empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Sourced from the ER Key Interactions & Contraindications bullets (ER 279-297).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Eight of the ten ER interaction bullets appear; alkylating cytotoxic chemotherapy and immunosuppressants are correctly omitted because both already appear as Contraindications.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eight <li> elements inside the caution_items span (lines 599-608).
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.	🟢	Mechanism, consequence and mitigation clauses dropped, and the em-dash glosses (“- blood thinners”, “- drugs that release the immune brakes on tumours”) 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).	🟢	All example drug lists preserved in parentheses, e.g. (glimepiride, gliclazide, repaglinide), (warfarin, apixaban, clopidogrel), (fish oil, nattokinase, ginkgo, high-dose vitamin E).
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 inside parentheses 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.	🟢	Section is populated, and the ER does identify interactions, so the ONLY IF constraint is satisfied.
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 left empty.

10. Protocol

#	Description	Result	Comments
10.1	The section is derived from the ER Protocol section	🟢	Drawn from the ER Therapeutic Protocol section (ER 329-351).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The two dosing regimens and the administration-timing bullet are the actionable implementation aspects; the remaining ER bullets are pharmacology, absent-data and response-predictor notes rather than actions.
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 describes more than three actionable implementation aspects, so no set is unused.
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 cells carry ER-derived content: 10 micrograms daily for 10 days by subcutaneous/intramuscular injection once or twice yearly (ER 331); 10 micrograms every other day across 10-20 days with no head-to-head comparison (ER 333); morning, conventional in the Russian protocols with no chronobiology data (ER 339).

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 three facts in the ER Time to effect bullet (ER 382) are each given a cell: outcome assessment window, course length, and the absence of a subjective-change timescale.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered highest-magnitude first: the human outcome window tied to the Medium-tier colorectal benefit, then course length, then the unknown subjective timescale.
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	The ER supplies three distinct time-to-effect aspects, so no set is unused.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine time cells carry ER-derived content; “Months to 2 years” and “10 to 20 days” both come from ER 382.
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, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Drawn from the ER Expected Benefits section (ER 131-199).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four variables present; benefits_high hidden, medium, low and speculative populated.
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.	🟢	Each tier is a semicolon-separated list of ER benefit headings with no effect sizes, citations or mechanistic explanation. The species/model phrases are part of the ER headings and removing them would overstate the claims.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content anywhere in the benefits lists.
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.	🟢	No High-tier benefit exists in the ER, and benefits_high is set to style=”display: none” with the list item removed (line 537).

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Drawn from the ER Potential Risks & Side Effects section (ER 215-261).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four variables present; risks_high and risks_medium hidden, low and speculative populated.
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.	🟢	Both Low-tier and all five Speculative-tier ER headings appear as bare key facts with no study detail or mechanism.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content anywhere in the risks lists; the ER’s inline glossary parentheses are stripped.
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.	🟢	Neither High nor Medium risks exist in the ER, and both spans carry style=”display: none” with their list items removed (lines 620-621).

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Drawn from the ER Monitoring Protocol & Defining Success section (ER 404-423).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 12 ER biomarker table rows are present; programmatic comparison of marker name, target and why against the ER table returned zero mismatches.
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.	🟢	Populated from ER 406 and 408: baseline before a first course, repeat at end of course and at 4-6 weeks, then 6-12 month intervals, with first-week checks for anyone on insulin or an anticoagulant.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Drawn from the ER qualitative marker list in Monitoring Protocol & Defining Success (ER 427-433).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All seven ER qualitative markers are listed with their ER bold labels verbatim.

Issues 21/09/2026 06:00

Pass rate 100.00%. No issues found.

Issues 21/09/2026 05:53

1. 1.3 / 8.2 — Prednisone contraindication scope narrowed: ER line 303 names “anyone on prednisone at 20 mg daily or more for two weeks or longer” as a population independent of transplant recipients, but QRS lines 576-577 render it as “Solid-organ transplant recipients on immune-suppressing drugs (ciclosporin, tacrolimus), or prednisone at 20 mg daily or more…”, which restricts the prednisone gate to transplant recipients and softens the contraindication.

Fixes 21/09/2026 05:53

1. 1.3 / 8.2 — Prednisone contraindication scope restored: Changed the third contraindication from “…(ciclosporin, tacrolimus), or prednisone at 20 mg daily or more…” to “…(ciclosporin, tacrolimus), and anyone on prednisone at 20 mg daily or more…”, so high-dose prednisone again reads as a population independent of transplant recipients, as in ER line 303.