Audit: QRS - Liothyronine for Health & Longevity

Audit conducted on 17/09/2026 03:02 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 span traces to ER text: protocol cells to Therapeutic Protocol, time cells to Practical Considerations / Expected Benefits, gates to Key Interactions & Contraindications, markers and cadence to Monitoring Protocol & Defining Success.
1.2 Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing. 🟢 The ER uses no empty-state or hedging boilerplate; the QRS invents none. The Speculative risk tier carries the ER’s own mechanistic-only framing without asserting measured effect.
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”). 🟢 “Pregnancy and lactation” stays in Contraindications, not Key Interactions; at-a-glance keeps “average gains are absent” against the ER’s “no average gain”.
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. 🟢 All 9 stop items come from the ER’s “Populations who should avoid Liothyronine” list; all 17 caution items from the ER interaction bullets. No Benefit-Modifying 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, author names, or brand names (Cytomel, Tertroxin, Thybon, Armour) appear anywhere in the QRS.
1.6 The QRS does not introduce new attributions. 🟢 No attributions of any kind in the QRS body.

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. 🟢 Declarative, evidence-first register matching the ER throughout.
2.2 The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging 🟢 Quantified targets and thresholds paired with plain-language glosses in the at-a-glance.
2.3 The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor 🟢 Protocol and monitoring cells state what is done, not what the reader must do.
2.4 The QRS avoids language that implies medical or clinical advice 🟢 No imperatives; monitoring targets are presented as ranges, cadence as a descriptive schedule.
2.5 The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” 🟢 No instances of “recommend”, “advise”, or “should” outside inherited template CSS comments.
2.6 The QRS never addresses “the reader” directly — it presents evidence, not guidance 🟢 No second-person pronouns anywhere in the document.
2.7 The QRS is written in plain language, avoiding unnecessary medical jargon 🟢 Technical terms are retained only where clinically load-bearing, with named drug examples in parentheses for each interaction class.
2.8 Information is presented in a concise and very compact manner 🟢 Gate items and tier lists are stripped to key facts; no mechanistic rationale or mitigation text carried over.
2.9 It DOES NOT address the reader directly 🟢 Confirmed by full-document scan for “you” / “your”.
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. 🟢 Ten-marker monitoring panel, trough-timed free T3 target and two-yearly densitometry cadence assume a proactive, testing-literate reader.
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. 🟢 Split fasted dosing, four-hourly separations and a ten-analyte panel are presented without hedging on inconvenience.
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. 🟢 Functional target ranges tighter than conventional lab cut-offs are carried through unsoftened.
2.13 Framing, takeaways, and risk/benefit weighting throughout the document reflect this audience, including where an intervention’s signal for the average person differs from its signal for this audience. 🟢 The at-a-glance states the null average effect alongside the symptomatic-responder signal, and the Speculative risk tier carries the longevity counter-signal.
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 occurrence of “anti-aging” or “antiaging”; the title uses “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)”; “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. 🟢 No “pill”, “shot”, “by mouth” or “bad reaction”; the QRS uses “adverse events”, “acute myocardial infarction”, “administered” register throughout.

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 headings byte-identical to [qrs_template]; tier labels intact in both tier lists except the benefits Speculative tier, which is correctly hidden per 12.5.
3.2 All “…” from the [qrs_template] are present in the the QRS. 🟢 All 34 template variable names present; the repeatable marker_#_* and qualitative_item_# patterns are expanded to 10 and 8 instances respectively.
3.3 Spans that are not addressed in a checklist item are left unchanged 🟢 Normalized structural diff against the template shows no change outside variable regions: CSS, website="…" spans, footer disclaimer and layout markup are untouched.

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 The only empty ER subsection is Expected Benefits → Speculative, which carries no empty-state phrasing at all; the display:none path of 12.5 governs instead.
4.2 Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. 🟢 “Standard combination regimen”, “Best time of day” and “Baseline biomarkers” are verbatim ER bold labels from Therapeutic Protocol.
4.3 Labels are not paraphrased, abbreviated, or invented. 🟢 Monitoring marker names match the ER biomarker table verbatim; time-to-effect labels track the ER benefit headings they are tied to.
4.4 The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. 🟢 No emoji in the document; the ER’s ⚠️ Conflicted and ⭕️ markers are stripped, and tiering is carried by the CSS palette plus 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 reduced to the minimum consistent with the completeness requirements of 9.2, 14.2 and 15.2: gate items carry no rationale, tier lists no effect sizes, and marker rows reuse the ER’s own one-clause “Why” text.

5. Metadata

# Description Result Comments
5.1 The metadata is placed inside a single HTML comment that is the first element after “<!doctype html>” and before any other comment, head, or body content. 🟢 Lines 2–14; the next comment (the template banner) follows at line 16.
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, preceded only by the permitted banner text on line 2.
5.3 The metadata is not visible in any rendered view of the QRS and is not surfaced by any other element on the sheet. 🟢 Enclosed in an HTML comment; no metadata value is echoed into 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, which is required by its colon.
5.5 The filename of the source ER is stated as “er_filename: [er_filename]” 🟢 er_filename: liothyronine_2026-0914-0341_Opus_ER.md, matching the ER frontmatter filename.
5.6 Version of the QRS.md file used to create the document is stated as “qrs_prompt_version: [Version of QRS.md]” 🟢 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) 🟢 qrs_creation_date: 2026-0917-0241.
5.8 The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]” 🟢 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) 🟢 Single word, 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]” 🟢 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, no context-window or tier qualifier.
5.12 The filename of the document is stated as “qrs_filename: [filename of this document]” 🟢 qrs_filename: liothyronine_2026-0914-0341_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 or redundant 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., &amp; for &) 🟢 “Liothyronine for Health & Longevity - Quick Reference Sheet” (line 22), 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., &amp; for &) 🟢 “Liothyronine for Health & Longevity” (line 417), matching ER canonical_topic.
6.3 [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] 🟢 2026-0917-0241 → “09/17/2026” (line 421).
6.4 [header_subline_model] is set to [qrs_creator_ai_fullname] 🟢 “Opus 5” (line 425).
6.5 No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker. 🟢 Header holds only the title and the template subline; the ER’s “Also known as” list is 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 it is, what replacement achieves, the split symptomatic picture, and the source of harm.
7.2 [at_a_glance] is no longer than 60 words 🟢 59 words.
7.3 Every fact in [at_a_glance] is supported by a distinct passage in the ER. 🟢 Each clause maps to a distinct Conclusion sentence (ER lines 516 and 518).
7.4 It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead 🟢 Uses “active thyroid hormone” and “storage hormone” in place of T3/T4; no acronyms, no clinical-register vocabulary.
7.5 It DOES NOT cite specific trials (names, years, sample sizes, p-values) 🟢 No trial name, year, sample size or p-value.
7.6 It DOES NOT cite effect sizes, relative risks, or statistical results 🟢 No numeric result of any kind.

8. Contraindications

# Description Result Comments
8.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Sourced from the “Populations who should avoid Liothyronine” list (ER lines 349–357).
8.2 [stop_items] represent the Contraindications from the ER 🟢 All 9 ER avoid-list entries present, in ER order.
8.3 Individual [stop_items] are formatted as <li></li> 🟢 Nine <li> elements inside the span (lines 568–588).
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 pregnancy rationale (“crosses the placenta poorly…”) and the ECG-measure gloss are stripped; no dash-trailing clauses 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). 🟢 “within 90 days”, “Class III to IV”, “QRS complex above 120 ms”, “QT at or above 460 ms in women and 450 ms in men”, “T-score of −2.5 or below” all 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. N/A The ER uses no ranking notation in the avoid list.
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 nine such populations and the section is correspondingly populated.
8.8 If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

9. Key Interactions

# Description Result Comments
9.1 The section is derived from the ER Key Interactions & Contraindications section 🟢 Sourced from the 17 interaction bullets at ER lines 313–345.
9.2 [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications 🟢 All 17 ER interaction bullets present; none duplicates a contraindication.
9.3 Individual [caution_items] are formatted as <li></li> 🟢 Seventeen <li> elements inside the span (lines 596–617).
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 mechanism sentence and “Mitigation:” clause is stripped; the ashwagandha bullet drops its trial citation. No dash-trailing clauses.
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). 🟢 Named exemplars retained for sulfonylureas, sympathomimetics, enzyme inducers, sequestrants/binders, PPIs/antacids, oestrogens and iron/calcium; the biotin threshold “above 5 mg daily” is 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. N/A The ER uses no ranking notation in the interaction bullets.
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 17 such interactions and the section is correspondingly populated.
9.8 If the section is left empty, an HTML comment inside the [caution_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g. N/A The section is not empty.

10. Protocol

# Description Result Comments
10.1 The section is derived from the ER Protocol section 🟢 All three cells trace to ER Therapeutic Protocol bullets (lines 383, 391, 403).
10.2 The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section 🟢 Dose regimen and ratio, dose timing, and the baseline panel that selects the candidate — the three decisions needed before and at initiation.
10.3 If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing. N/A The ER supplies twelve protocol bullets; all three sets are used.
10.4 All used [action_#label], [action#value], [action#_sub] items are filled with meaningful content derived from the ER Protocol section. 🟢 All nine cells populated; the 13:1–20:1 ratio, 30–60 minute fasting window and 4 pm cut-off are carried through exactly.

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 🟢 Biochemical steady state (3–4 days), symptom assessment window (6–12 weeks) and weight change (6 weeks).
11.2 The sets are picked and ordered by the magnitude of the related benefit 🟢 Correction of hypothyroidism (ER High tier) first, then the two ER Low-tier benefits in ER order.
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 more than three time-to-effect aspects; all three sets are used.
11.4 All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. 🟢 Subs quote the ER’s own qualifications: steady state in three to four days, 5–22 week trial periods, and full-substitution-only weight loss.
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 time-to-effect data (Practical Considerations, ER line 440), so the section is retained.

12. Benefits

# Description Result Comments
12.1 The section is derived from the ER Expected Benefits section 🟢 All eight benefit headings across the ER’s High, Medium and Low tiers are represented.
12.2 Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] 🟢 All four spans present at lines 542–558.
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 bare benefit headings; no Magnitude: figures carried over.
12.4 Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in any benefits item.
12.5 If no items of a specific sub-section (high, medium, low, speculative) are present the respective is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. 🟢 The ER’s empty Expected Benefits → Speculative tier is handled with style="display: none" on the span, with no empty-state text (line 558).

13. Risks

# Description Result Comments
13.1 The section is derived from the ER Potential Risks & Side Effects section 🟢 All nine risk headings across the ER’s four tiers are represented.
13.2 Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] 🟢 All four spans present and populated at lines 629–650.
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. 🟢 Bare headings only; no hazard ratios, confidence intervals or the ER’s ⚠️ Conflicted markers.
13.4 Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. 🟢 No parentheses in any risks item.
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. N/A All four ER risk tiers contain items, so no span needs hiding.

14. Monitoring

# Description Result Comments
14.1 The section is derived from the ER Monitoring section 🟢 Rows mirror the biomarker table in Monitoring Protocol & Defining Success (ER lines 472–483).
14.2 All measurable/quantifiable biomarkers from the Monitoring section are listed 🟢 All 10 ER biomarkers present in ER order, with target ranges and “Why” text carried over verbatim.
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. 🟢 Reproduces ER line 470: 6 and 12 weeks then 6-monthly, lipids and SHBG at 6 months, densitometry every 24 months below 0.4 mIU/L, heart rate at every review.

15. Qualitative Assessment

# Description Result Comments
15.1 The section is derived from the ER Monitoring section 🟢 Sourced from the qualitative marker list at ER lines 487–494.
15.2 All subjective/qualitative biomarkers from the Monitoring section are listed 🟢 All 8 ER qualitative markers present verbatim and in ER order.

Issues 17/09/2026 03:02

Pass rate 100.00%. No issues found.

Issues 17/09/2026 02:53

  1. 1.1 / 1.3 — Conditional turned into fact: The seventh contraindication (line 583) reads “where suppression is needed”, whereas ER line 355 says “where suppression would be needed”, converting the ER’s conditional scenario into a factual assertion.

Fixes 17/09/2026 02:53

  1. 1.1 / 1.3 — Conditional restored in contraindication: The seventh contraindication now reads “where suppression would be needed” instead of “where suppression is needed”, matching the ER’s conditional phrasing.

Issues 17/09/2026 02:46

  1. 1.3 — Hedge dropped from At-A-Glance: [at_a_glance] (line 436) asserts “though the most symptomatic improve”, strengthening the ER Conclusion (line 516), which hedges with “the most symptomatic participants within individual studies have tended to prefer and improve on treatments containing it”.

Fixes 17/09/2026 02:46

  1. 1.3 — ER hedge restored in At-A-Glance: Changed [at_a_glance] from “though the most symptomatic improve” to “though the most symptomatic have tended to improve”, matching the ER Conclusion hedge; the lede remains within the 60-word budget at 59 words.