Audit: QRS - L-Tryptophan for Health & Longevity

Audit conducted on 28/08/2026 05:39 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	93
Passed	83
Failed	0
N/A	10
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 an ER passage: protocol cells to ER Therapeutic Protocol bullets 1–3, time cells to the Practical Considerations “Time to effect” bullet, benefit/risk tiers to the ER tier headings, gates to Key Interactions & Contraindications, markers and cadence to the Monitoring Protocol & Defining Success table and narrative.
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.	🟢	At-a-glance “keeps safety open” mirrors the ER conclusion’s “keep the question genuinely open”; no cautious ER phrasing is dropped or hardened.
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”).	🟢	Absolute contraindications stay in the stop gate (MAOIs, linezolid/methylene blue, pregnancy/breastfeeding); cautions stay in the caution gate. No tier or severity is shifted.
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.	🟢	Nothing from Benefit-Modifying Factors or Risk-Modifying Factors appears in the gates or the risk card; each QRS section draws only on its mapped ER section.
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.	🟢	The QRS carries no PMIDs, citations, expert names, NCT identifiers, or brand names at all.
1.6	The QRS does not introduce new attributions.	🟢	No attributions are present anywhere in the sheet.

2. Focus, Tone & Audience

#	Description	Result	Comments
2.1	The QRS follows the tone of the ER, which is determined by the ER’s own language, phrasing, and framing.	🟢	Measured, non-promotional register matching the ER, including the unresolved framing of the 1989 outbreak.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Concrete thresholds (1 g, 500 cells/µL, 45–80 µmol/L) alongside plain-language explanations give the reader actionable grounding without hype.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Statements are descriptive (“Taken 30–60 minutes before bed”), never imperative.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No “should”, “must”, “recommend”, or “advise” anywhere in the body.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	All cells are declarative statements of what the evidence shows or what protocols do.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns occur in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms that remain (Child-Pugh Class B or C, kynurenine-to-tryptophan ratio) are decision-relevant thresholds required by items 8.5 and 14.2.
2.8	Information is presented in a concise and very compact manner	🟢	Gate items, benefit and risk tiers are reduced to key facts; no elaborations carried over.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by scan of the rendered body text — no direct address.
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.	🟢	Functional ranges rather than conventional lab cut-offs, a seven-marker monitoring panel and a titration-relevant dose threshold all assume a proactive 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.	🟢	Protocol requires two-hour separation from protein, bedtime timing, and repeat blood work at 4 weeks and 3 months.
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 “just take one at night” framing; the sheet retains the full contraindication and interaction burden.
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 leads with the one replicated benefit and immediately pairs it with the unresolved safety question, matching the ER’s weighting.
2.14	The document’s own voice frames usage in longevity terms, not “anti-aging” (e.g., “anti-aging clinics”, “anti-aging community”, “anti-aging medicine”). Proper names that contain “anti-aging” (e.g., “American Academy of Anti-Aging Medicine”) are quoted verbatim.	🟢	The string “anti-aging” does not occur; 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)”; “injection” not “shot”; “adverse event” not “bad reaction”). Direct quotes from sources are exempt.	🟢	Uses “sedating over-the-counter medication”, “hepatic impairment”, “absolute eosinophil count”; no “pill”, “shot”, or similar consumer-grade terms.

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, gate heads, tier labels and column headers match the template byte-for-byte (lines 445, 491, 538, 567, 586, 616, 644, 648–650, 762).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variable names are present; marker_#_* is instantiated as marker_1–marker_7 and qualitative_item_# as items 1–5, for 60 spans total.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff against the template shows the head, CSS block, all structural markup, the three <span website="..."> hooks and the footer disclaimer are unchanged.

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 ER section that maps to a QRS variable is empty.
4.2	Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label.	🟢	Protocol cell labels (“Standard sleep dose”, “Separation from protein”, “Optional carbohydrate pairing”) and all seven monitoring row labels are verbatim ER labels.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Time-to-effect cell labels (“Night-time waking”, “Mood”, “Falling asleep”) are taken from the wording of the ER’s own “Time to effect” bullet rather than invented.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters appear; tiers are conveyed by bold labels plus the green/red card palettes.
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 its minimum permitted content: gate items are stripped to the key fact plus mandatory qualifiers, benefit and risk tiers are collapsed to semicolon-separated headings, and the monitoring rows carry only the ER’s “Why Measure It?” phrase without the Context/Notes column.

---

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 comment opens on line 2, 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 --- on line 3, closing --- on line 13; the “QRS — Metadata” caption precedes 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 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, and it 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: l_tryptophan_2026-0828-0325_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 version badge at the top of QRS.md.
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-0828-0533, 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 with no trailing qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: l_tryptophan_2026-0828-0325_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 including the appended git_user and git_issue; all clean.

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: “L-Tryptophan for Health & Longevity - Quick Reference Sheet”, matching the ER canonical_topic with the ampersand 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: “L-Tryptophan for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 08/28/2026, correctly derived from 2026-0828-0533.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching the 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 the template subline only; the ER’s “Also known as” line was 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 into what the compound is, the one replicated effect with its dose and timing conditions, and the two dominant safety points.
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 sentence of the ER Conclusion (lines 456, 458).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “eosinophilia-myalgia syndrome” is rendered as “a painful muscle and immune illness” and serotonin/melatonin as “the messengers most tied to sleep and mood”.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, sample sizes or p-values; “1989” refers to the historical outbreak, not to a study.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect sizes or statistics; “a gram or more” is a dose, not an effect estimate.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items trace to the two “Absolute contraindication” bullets and the “Populations who should avoid L-Tryptophan” list (ER lines 288, 294, 306–313).
8.2	[stop_items] represent the Contraindications from the ER	🟢	Complete: MAOIs, linezolid/methylene blue, EMS history or eosinophilia >500, carcinoid tumors, Child-Pugh B/C, pregnancy/breastfeeding, active eosinophilic disorder. Nothing omitted, nothing added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <li> elements inside the stop_items span (lines 570–581).
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 rationale clauses (“in whom no adequate safety data exist”, the eosinophilic-disorder gloss, the Child-Pugh definition) are all stripped; no dashes carry trailing content.
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).	🟢	The 14-day washout window, the 500 cells/µL threshold, the Child-Pugh Class B or C staging and the four named MAOIs 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 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.	🟢	The ER names multiple such populations and the section is correctly 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	🟢	All seven items trace to the ER’s “Caution” bullets (ER lines 290–304).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	Exactly the seven caution bullets; the two absolute-contraindication bullets (MAOIs, linezolid/methylene blue) are correctly excluded and appear only in the stop gate.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Seven <li> elements inside the caution_items span (lines 589–606).
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 rationale sentence (“These antidepressants keep serotonin active longer…”, the 500 mg ceiling, the carbidopa mechanism) is stripped; only the agent class plus examples remains.
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 six ER example-drug lists are preserved; the redundant “SAMe or” acronym is trimmed while “S-adenosylmethionine” is kept.
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.	🟢	The ER names seven such interactions and the section is correctly 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	🟢	The three cells correspond to the first three bullets of the ER Therapeutic Protocol (ER lines 335–339).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	Dose/timing, protein separation and carbohydrate pairing are the three execution steps the ER places first; the remaining bullets are competing approaches, lineage and modifiers rather than core 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 provides three or more actionable aspects and 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 spans are populated; labels are the ER bold labels verbatim and the subs restate the ER’s own wording.

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	🟢	Night-time waking, mood and sleep onset are exactly the three latencies given in the ER “Time to effect” bullet (ER line 392).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Order matches the ER benefit tiers: night-time waking (High), mood (Medium), falling asleep (Low).
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 provides three distinct time-to-effect aspects and 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.	🟢	All nine spans are populated; the subs reproduce the ER sentences and the values condense them to “First nights”, “About 7 days” and “Over a week”.
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 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 listed benefits map one-to-one onto the ER Expected Benefits sub-headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans are present and populated (lines 540–560).
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 the ER headings only; no magnitudes, trial counts or “⚠️ Conflicted” markers carried over.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any benefit 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.	N/A	All four tiers have items in the ER, so no span needs hiding.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All five listed risks map one-to-one onto the ER Potential Risks & Side Effects sub-headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans are present and populated (lines 618–638).
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.	🟢	The 11%/29%/50% incidence figures, the 70 mg/kg threshold and the Fernstrom attributions are all omitted; only the harm names remain.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses appear in any risk 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 tiers have items in the ER, so no span needs hiding.

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Marker names, targets and “why” text are taken verbatim from the ER Monitoring Protocol & Defining Success biomarker table (ER lines 424–430).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All seven ER biomarkers are present: absolute eosinophil count, plasma tryptophan, kynurenine-to-tryptophan ratio, hs-CRP, serum PLP, serum 25-hydroxyvitamin D and ALT.
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.	🟢	Line 753: baseline draw, CBC with differential at 4 weeks and 3 months, then every 6–12 months, with tryptophan and kynurenine repeated only on poor response — matching ER lines 418 and 420.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	The five items reproduce the ER’s qualitative marker list (ER lines 434–438).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five are present: awakenings/minutes awake, residual sedation, daytime alertness, mood stability, and new muscle/skin/nerve symptoms.

Issues 28/08/2026 05:39

Pass rate 100.00%. No issues found.