Audit: QRS - Avoiding Tyramine for Health & Longevity

Audit conducted on 21/09/2026 05: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 cell traced to the ER: protocol list to ER Therapeutic Protocol bullet 1, split intake and half-life to their ER bullets, time-to-effect to Practical Considerations, 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.	🟢	No cautious empty-state phrasing is carried into a cell in a way that alters it; tier subsections with no entries are hidden per 12.5/13.5.
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”).	🟢	Thresholds retained unchanged (6 mg/meal, 20–30 mg/day selegiline, 6 vs 9/12 mg/24 h patch, 100 mg linezolid meals, two-week tail).
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 come only from the ER’s “Populations who should avoid” list; Key Interactions only from the ER interaction bullets; no modifying factor is promoted into 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, citations, author names, NCT IDs or brand names 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.	🟢	Same measured, mechanism-aware register as the ER.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	At-a-glance states the one strong case and the cost of the restriction without alarm or promotion.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Gate and protocol cells are nominal/passive constructions, not instructions to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	No imperatives; mitigations are stated as practice (“doses separated from meals by 30–60 minutes”).
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommended”, “should”, or “advise” anywhere in the QRS’s own voice.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns in the document.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are confined to the gates and biomarker table where they are the ER’s own names for the entities; the lede is plain.
2.8	Information is presented in a concise and very compact manner	🟢	Benefits and risks are single-line tier summaries; gate items carry the key fact only.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by search for you/your/we/our — no hits.
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.	🟢	Framing assumes a reader weighing the restriction against the fermented-food exposure it removes.
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-intake and two-week-tail cells assume willingness to follow an inconvenient regimen.
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.	🟢	Biomarker panel (dp-ucMGP, intact PTH, INR) and per-meal ceilings are aimed at a proactive reader.
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.	🟢	Lede states plainly that without enzyme-blocking medication the restriction “buys little and gives up something measurable”, mirroring the ER Conclusion.
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 “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.	🟢	“medication”, “doses”, “capsules”, “transdermal” used; no colloquial substitutes.

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 strings byte-identical to the template (lines 446, 495, 542, 636, 661, 773, 567, 584, tier labels, and the Marker/Target/Why header row at 665–667).
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 named template spans present, plus repeated marker_#* (6 rows) and qualitative_item# (5 items); the three website="..." spans are also intact.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	Diff of the QRS head/CSS block against the template is empty apart from the page_title value; footer, disclaimer and structural markup 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 source ER section mapped to a QRS element is empty; the ER’s Benefits-Medium and Risks-High tiers carry a no-item statement and are handled under 12.5/13.5 by hiding the span.
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.	🟢	All three protocol labels and all eleven Key Interaction bold labels reproduce the ER labels verbatim, including the parenthetical drug lists.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	Protocol and interaction labels verbatim; time-to-effect cells take their labels from the aspects inside the ER’s single “Time to effect” bullet, which supplies no per-aspect bold label.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji code points in the file; the ER’s “⚠️ Conflicted” markers were dropped.
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 against the ER: multi-sentence ER bullets reduced to one short line each, benefits and risks collapsed to one line per tier, no section carried over in full prose.

---

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, immediately after the doctype at 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 “—” line 3, closing “—” line 13; the descriptive text sits 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 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, correctly, because it contains a colon.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: avoiding_tyramine_2026-0921-0310_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 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-0921-0554.
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” — single word, no version.
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, no qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9 matches the actual filename avoiding_tyramine_2026-0921-0310_Opus_QRS.html.
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.	🟢	No stray whitespace or unnecessary quoting on any of the nine keys.

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: “Avoiding Tyramine for Health & Longevity - Quick Reference Sheet”.
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: “Avoiding Tyramine for Health & Longevity”.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: “09/21/2026” from qrs_creation_date 2026-0921-0554.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”.
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” 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: where tyramine forms, normal clearance, the medication case, and the net for everyone else.
7.2	[at_a_glance] is no longer than 60 words	🟢	58 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to ER Conclusion lines 439–443.
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	“enzyme-blocking medication” replaces “monoamine oxidase inhibitor”; no acronyms at all.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial reference of any kind.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers appear in the lede.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Taken from the “Populations who should avoid Avoiding Tyramine” list, ER lines 289–297.
8.2	[stop_items] represent the Contraindications from the ER	🟢	All four ER populations present, none added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Four <li> elements inside the span, lines 570–579.
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 dietary amines contribute to postural support”, “in whom removing a further food group risks…”) are stripped; no dash-trailed 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).	🟢	110 mmHg supine systolic, BMI 18.5 kg/m², T-score −2.5 or lower, 700 mg/day calcium, INR 2.0–3.0 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.	N/A	The section is not empty; the ER names four such populations.
8.8	If the section is left empty, an HTML comment inside the [stop_items] span records the ER basis for the absence, naming or quoting the ER text relied on. E.g.	N/A	The section is not empty.

9. Key Interactions

#	Description	Result	Comments
9.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Taken from the eleven interaction bullets, ER lines 267–287.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eleven ER interactions present; none duplicates any of the four contraindicated populations.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Eleven <li> elements, lines 587–626.
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.	🟢	Each ER bullet’s two-to-three sentences of mechanism are stripped to the operative fact; no dash-trailed 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).	🟢	All named drug lists retained verbatim, along with 6 mg/meal, 20–30 mg/day, 6 vs 9/12 mg/24 h, 100 mg/meal, the two-week tail, the one-to-two-week INR recheck and the 30–60 minute levodopa separation.
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 parentheses hold plain comma-separated drug names only, with no ranking 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.	N/A	The section is not empty; the ER names eleven interactions.
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 taken from ER Therapeutic Protocol, lines 317–339.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	What is restricted, how a moderate load is split, and how long restriction persists after the drug stops — the three bullets that determine what a reader actually does.
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 more than three 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 populated; labels verbatim from the ER bold labels, values and subs condensed from the same bullets.

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 ER’s “Time to effect” bullet (line 370) names exactly two aspects — immediate meal-specific protection and the nutritional consequence over months — and both are carried.
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Set 1 is the High-tier benefit (protection from the pressor response); set 2 is the slower nutritional consequence.
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.	🟢	The third pcell carries style="display: none" with all three spans empty (lines 526–536).
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	Six spans populated from ER Practical Considerations line 370.
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 retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Every entry maps to an ER benefit heading, lines 147–181.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four spans present, lines 544–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.	🟢	Headings only; the ER’s magnitude figures (15 mg vs 240 mg, HR 1.21) and citations are absent.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses 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.	🟢	The ER states no benefit reaches Medium; benefits_medium carries style="display: none" with an empty payload (line 549).

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	Every entry maps to an ER risk heading, lines 207–247.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four spans present, lines 638–655.
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.	🟢	Headings only; the ER’s relative risks (0.95, 0.92, 0.90) and study details are absent.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheses 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.	🟢	The ER states no risk reaches High; risks_high carries style="display: none" with an empty payload (line 638).

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Taken from the ER Monitoring Protocol & Defining Success biomarker table, lines 400–407.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All six ER rows present with matching targets: home seated blood pressure, resting heart rate, hs-CRP, dp-ucMGP, intact PTH, INR.
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 763 reproduces the ER’s cadence paragraph (line 398): daily for the first month and 1–2 h after unfamiliar aged food, weekly for three months, then every six to twelve months.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Taken from the ER’s qualitative marker list, lines 411–419.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All five ER items present and unaltered.

Issues 21/09/2026 05:57

Pass rate 100.00%. No issues found.