Audit: QRS - Epithalamin for Health & Longevity

Audit conducted on 01/09/2026 00:57 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	84
Failed	0
N/A	9
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 span traces to ER text: protocol cells to ER lines 323/325/333, time-to-effect to line 380, benefit/risk items to the ER heading text, monitoring rows to the ER table (lines 414–423), qualitative items to lines 427–432.
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.	🟢	Hedges carried through: “no trial has compared timings” (action_3_sub), “claimed to fall” (marker_5_why), “No established target” (marker_10_target), “side effects were never systematically collected” (at_a_glance).
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”).	🟢	Contraindications remain absolute stops; benefits keep their ER tier; “Nearly all evidence comes from one group that also sells the preparation” matches the ER Conclusion’s force.
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 and Key Interactions both come from the ER Key Interactions & Contraindications section; no Benefit-Modifying or Risk-Modifying Factor bullet is surfaced in either gate or in the Risks card.
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, links, years or sample sizes anywhere. Named products (Thymalin, Cortexin, Vilon, TA-65, cycloastragenol) and drug names all appear in the same ER interaction bullets (lines 276–292).
1.6	The QRS does not introduce new attributions.	🟢	The only proper noun is “Khavinson-type”, used exactly as the ER labels that interaction bullet (line 292); no investigator, institute or study is credited with a finding.

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 QRS mirrors the ER’s measured-but-sceptical register: real endpoints stated plainly, single-source and unmeasured-safety caveats carried into At-A-Glance.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Numeric targets, a measurable response predictor and a monitoring cadence give the reader actionable levers without overselling the evidence.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Cells state what the trials used (“Standard course used in the trials”, “Common practice”), not what to do.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperative or prescriptive verbs in the QRS’s own voice; the only clinician-referral wording is the unmodified template footer disclaimer.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No occurrence of “recommend”, “advise”, “should” or “must” anywhere in the document body (lines 412–842).
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronoun (“you”, “your”) appears anywhere in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to biomarker names and ER heading text; At-A-Glance renders “pineal” as “a gland in the brain” and “acute respiratory infections” as “chest infections”.
2.8	Information is presented in a concise and very compact manner	🟢	Every monitoring “Why” cell is 4–8 words; benefit and risk tiers are single semicolon-separated lines; gate items are label-only.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text scan: no direct address anywhere in the sheet.
2.10	The target audience is health- and longevity-oriented adults who are risk-aware, proactive, and actively seeking to optimize health or apply the intervention under review.	🟢	Content assumes a reader who will obtain a 02:00–04:00 melatonin draw, an ApoB and a 24-hour ambulatory blood-pressure study before and during courses.
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.	🟢	A 10-day daily intramuscular course twice yearly plus a 10-marker panel is presented without hedging about burden.
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 simplified “ask your doctor” framing; optimal functional ranges are given rather than conventional laboratory cut-offs.
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 baseline-dependence signal is surfaced where it matters for this audience: melatonin suppression is listed as a Low risk for people with an intact rhythm, and marker_1_why names the only measured predictor of response.
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.	🟢	“anti-aging” does not occur; the title uses the ER’s canonical “Health & Longevity”.
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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	“intramuscular”, “injections”, “lyophilized powder”, “hypersensitivity” used throughout; no “pill”, “shot” or similar consumer-grade term appears.

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 verified verbatim at lines 446, 491, 539, 572, 588, 615, 637, 641–643, 794; visible tier labels “High: “, “Medium: “, “Low: “, “Speculative: “ intact in Benefits and Risks.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variables present; the two indexed patterns are correctly expanded to marker_1…marker_10 and qualitative_item_1…qualitative_item_6.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three website= spans (evidence_review, audit, full_review) and the page_title wrapper are byte-identical to the template; the entire head/CSS block diffs clean against [qrs_template].

4. Formatting

#	Description	Result	Comments
4.1	When the source ER section is empty, the QRS uses the ER’s own empty-state phrasing verbatim. Typical phrasings are “None documented in human trials to date” and “Not formally studied”	N/A	No source ER section is empty. The ER’s High and Medium risk tiers carry explanatory prose rather than an empty state, and their QRS handling is governed by the more specific item 13.5.
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.	🟢	action_1_label “Standard course used in the trials”, action_2_label “Course frequency”, action_3_label “Best time of day” all match the ER Protocol bold labels verbatim (lines 323, 325, 333).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Monitoring marker names reproduce the ER Biomarker column verbatim, including “Luteinizing hormone (LH) and follicle-stimulating hormone (FSH)” and “High-sensitivity C-reactive protein (hs-CRP)”.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Full-file scan for emoji code points returns nothing; tiering is carried by the template’s CSS classes and bold tier labels.
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 the tightest form its governing item allows — one-line benefit/risk tiers, label-only gate items, 4–8-word monitoring rationales — and no content beyond what items 9.2, 12.1–12.2, 13.1–13.2 and 14.2 mandate is carried over.

---

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 comment at lines 2–14, immediately after <!doctype html> on line 1.
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; the preamble text sits on line 2 before the opener.
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; none of its values are repeated in the header, footer or body.
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:03" is quoted, correctly so because the value contains a colon; all other values are bare and trimmed.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: epithalamin_2026-0831-2216_Opus_ER.md, matching the ER’s own filename frontmatter field.
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.7.02, 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-0901-0036, correct format.
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” is nickname plus version number with no trailing qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: epithalamin_2026-0831-2216_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 across all nine keys; no stray whitespace and no unnecessary 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 &)	🟢	Line 22: Epithalamin for Health & Longevity - Quick Reference Sheet, with the ampersand correctly 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: Epithalamin for Health & Longevity, matching the ER canonical_topic exactly.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 09/01/2026, the correct MM/DD/YYYY rendering of 2026-0901-0036.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: Opus 5, matching the qrs_creator_ai_fullname frontmatter value.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	The header block (lines 415–428) is structurally identical to the template; the ER’s “Also known as” line was correctly not carried over.

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 three Conclusion paragraphs: what the substance is, the reported endpoints, and the two limitations that govern any decision to use it.
7.2	[at_a_glance] is no longer than 60 words	🟢	58 words, verified by script.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	“fewer deaths, preserved physical capacity, fewer chest infections and lower blood pressure” ← line 454; “one group that also sells” ← line 456; “no independent group has repeated the survival findings” ← line 456; “side effects were never systematically collected” ← line 458.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “pineal gland” is rendered as “a gland in the brain of cattle” and “acute respiratory infections” as “chest infections”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	Refers only to “Long-running trials in older adults with heart disease”; no investigator, year, cohort size or identifier.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	Direction-only wording throughout; the ER’s “28% lower” and “1.6–1.8-fold” figures are not carried in.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All six items map one-to-one to the “Populations who should avoid Epithalamin” list at ER lines 298–303.
8.2	[stop_items] represent the Contraindications from the ER	🟢	Complete: all six ER populations are present, none added and none dropped.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Six discrete <li> elements at lines 575–583 inside the stop_items span.
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.	🟢	The ER’s trailing rationales are all stripped: “given the unresolved telomerase and alternative-lengthening signal”, “— no reproductive toxicology of any kind exists” and “, in whom the pineal axis is at peak output” do not appear.
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).	🟢	“remission of less than 5 years”, “Active, uncontrolled” with the lupus-flare example, and “under 18” are 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’s contraindication list uses no ranking notation or comparison symbols in parentheses.
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 six such populations, so populating the gate is correct; the section is not empty.
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, so no absence comment is required.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All ten items map one-to-one to the ER interaction bullets at lines 276–294.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All ten ER interaction bullets are carried; none duplicates a contraindication — the immunosuppressant drug interaction is broader than the transplant-recipient population listed as a stop.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Ten discrete <li> elements at lines 591–605 inside the caution_items span.
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.	🟢	Every ER “Caution./Monitor.” severity word and its consequence sentence is stripped; no item contains a dash-led trailing clause.
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 eight ER example-drug lists are retained in parentheses (ramelteon/tasimelteon, propranolol/atenolol/metoprolol, zolpidem/eszopiclone/temazepam, diphenhydramine/doxylamine, aspirin/ibuprofen/naproxen, 5-HTP/valerian/magnesium glycinate/tart cherry, cycloastragenol/TA-65, tacrolimus/ciclosporin/mycophenolate, Thymalin/Cortexin/Vilon).
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’s interaction parentheses contain plain comma-separated drug names only, with no ranking or comparison symbols.
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 ten such interactions, so populating the gate is correct; the section is not empty.
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, so no absence comment is required.

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 at lines 323, 325 and 333.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose/course, course frequency and time of day — the three parameters a reader must fix to execute; the ER’s competing-approach and attribution bullets are correctly not promoted into the panel.
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’s Protocol section supplies well over three actionable aspects and all three sets are populated, so no set needed hiding.
10.4	All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section.	🟢	All nine spans carry substantive ER-derived content: “10 mg daily × 10 days” with route and diluent, “Two courses per year” with the six-courses-over-three-years detail, and “Evening” with the mechanism-not-data caveat.

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	🟢	Mortality, physical work capacity and melatonin/hormone changes — the exact three aspects distinguished in the ER’s “Time to effect” bullet at line 380.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered Mortality (ER High tier) → Physical work capacity (Medium) → Melatonin and hormone changes (Low), matching the ER’s benefit tiering.
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 distinguishes three time-to-effect aspects and all three sets are populated, so no set needed hiding.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	All nine spans populated; “One 10-day course” for the endocrine changes and “Years” for both the mortality and function endpoints reproduce ER line 380, with baseline-dependence added from line 166.
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 provides explicit 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	🟢	All nine benefit statements correspond to the nine ER Expected Benefits sub-headings, each placed in its ER tier.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present and populated at lines 541–565; two High, two Medium, four Low and three Speculative items, matching the ER’s distribution.
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 are ER sub-headings reduced to semicolon-separated phrases; the ER’s Magnitude paragraphs, cohort sizes and follow-up durations are all omitted.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any of the four benefit spans.
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.	N/A	All four ER benefit tiers contain items, so no benefit span needed hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	The two Low and four Speculative statements correspond exactly to the ER sub-headings at lines 230, 236, 244, 248, 252 and 256.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present at lines 617–631, in template order.
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.	🟢	Reduced to ER heading phrases; the ER’s Magnitude paragraphs and the “no case has been linked to the preparation” elaboration are omitted.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses in either populated risk span; the ER’s “(a fatal prion brain disease)” gloss is correctly 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.	🟢	The ER states no risk reaches High or Medium; both spans carry style="display: none" (lines 617–618) and neither was filled with empty-state phrasing.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	All ten rows trace to the ER Monitoring Protocol & Defining Success biomarker table (lines 412–423).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All ten ER biomarkers present, in ER order: night-time melatonin, urinary 6-sulfatoxymelatonin, LH/FSH, prolactin, hs-CRP, HbA1c, fasting insulin, ApoB, 24-hour ambulatory blood pressure, leukocyte telomere length.
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.	🟢	Lines 785–788 reproduce the ER’s three-tier cadence from line 410: hormones at 4 weeks post-course, metabolic/cardiovascular at 3 months, full set every 6–12 months.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	All six items come from the ER’s “Qualitative markers worth tracking alongside the laboratory panel” list at lines 427–432.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six carried verbatim: sleep onset latency and awakenings, subjective sleep quality, daytime energy stability, cognitive clarity and word-finding, exercise tolerance at a fixed workload, respiratory infection frequency and duration.

Issues 01/09/2026 00:57

Pass rate 100.00%. No issues found.

Issues 01/09/2026 00:45

1. 2.8 — Redundant time-to-effect sub-line: time_3_sub at line 530 reads “Measured after a single 10-day course”, restating time_3_value “One 10-day course” at line 526 verbatim and adding no information to the one-page sheet.

Fixes 01/09/2026 00:45

1. 2.8 — Redundant time-to-effect sub-line: Replaced time_3_sub (line 530) “Measured after a single 10-day course”, which merely restated time_3_value “One 10-day course”, with “Direction depends on baseline pineal output” (ER lines 168 and 205).

Issues 01/09/2026 00:41

1. 4.5 — Sheet exceeds one A4 page: Estimated rendered height is roughly twice the A4 print budget; the condensable overflow sits in the three-line Protocol sub-cells (lines 456-459, 470-474, 484-488), the redundant time_2_sub that restates time_1_sub (lines 517-520), and several over-long Monitoring “Why” cells plus the cadence line (789-792).

Fixes 01/09/2026 00:41

1. 4.5 — Protocol sub-cells condensed: Shortened all three action_#_sub cells from three rendered lines to two, e.g. “Lyophilized powder reconstituted in sterile saline or 0.5% procaine, injected intramuscularly” to “Lyophilized powder in sterile saline or 0.5% procaine, intramuscular”.
2. 4.5 — Redundant time-to-effect sub removed: Rewrote time_2_sub from “Function endpoints emerged only across years of repeated courses; nothing should be expected within weeks” to “Also years of repeated courses; nothing expected within weeks”, and trimmed time_1_sub and time_3_sub to drop the label restated in each.
3. 4.5 — Monitoring cells tightened: Condensed the “Why” text of all ten markers and the targets of markers 1, 8 and 10 so eight of ten rows now render on a single line, e.g. “Tests the lipid claim with the particle count that actually predicts events” to “The particle count that predicts events”.
4. 4.5 — Cadence line shortened: Reduced monitoring_cadence from 166 to 118 characters by dropping “10-day”, “panel” and “for as long as courses continue”, bringing it onto one rendered line.