Audit: QRS - Capsaicin for Health & Longevity

Audit conducted on 22/09/2026 16:43 using AI4L / Opus 5

Iterations

Summary

Items	Count
Total	94
Passed	84
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.	🟢	Spot-checked every populated span against the ER: protocol cells against ER Therapeutic Protocol (lines 363, 367, 369), time cells against Practical Considerations line 418 and Monitoring Protocol line 450, benefit/risk tiers against the ER headings, gates against Key Interactions & Contraindications (lines 315-339), monitoring rows against the ER table (lines 454-460).
1.2	Where the ER uses cautious phrasing (“not formally studied”, “None documented in human trials to date”, “theoretical concern”, “data are limited”), the QRS uses the same phrasing.	🟢	Cautious wording carried across: “Theoretical liver burden from reactive metabolites” (ER line 460 “theoretical liver burden”), “Appetite suppression appears partly inseparable from gastrointestinal discomfort” (ER line 191), “the link to longer life comes from observation rather than experiment” (ER line 489).
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	No strengthening or softening detected. Contraindication thresholds (Los Angeles grade C or D, 160/100 mmHg, 90 days, Child-Pugh B or C) are reproduced at ER severity.
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.	🟢	Benefits map 1:1 to ER Expected Benefits headings and risks 1:1 to Potential Risks & Side Effects headings; nothing from Benefit-Modifying Factors or Risk-Modifying Factors was promoted into a gate or tier.
1.5	PubMed IDs, study citations, expert names, clinical trial identifiers (NCT*), and brand names appear in the QRS only if they appear in the source ER for the same fact.	🟢	No PMIDs, NCT identifiers, study citations or expert names appear in the QRS. The only brand name, BioPerine, is taken from the same ER bullet (line 323).
1.6	The QRS does not introduce new attributions.	🟢	No attributions of any kind in the QRS.

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.	🟢	Register matches the ER: measured, evidence-weighted, explicit about what is observational.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Expert and data-driven (thresholds, ranges, tiers) while remaining accessible; the lede is plain-language.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	Presented as distilled evidence; no directives issued to a patient.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Protocol and cadence cells describe what trials and protocols did rather than prescribing action.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No “recommend”, “advise” or “you should” constructions anywhere in the sheet.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns anywhere in the file (checked across the full source).
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Plain language throughout; the remaining technical terms (Child-Pugh, hs-CRP, ALT, HbA1c) are load-bearing decision-gate and biomarker identifiers required by items 8.5 and 14.2.
2.8	Information is presented in a concise and very compact manner	🟢	Every gate item, tier item and monitoring cell is a single terse clause.
2.9	It DOES NOT address the reader directly	🟢	Confirmed: no direct address to the reader.
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 is pitched at proactive, risk-aware optimizers: functional biomarker ranges rather than conventional clinical cut-offs.
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.	🟢	The protocol panel assumes willingness to run a 12-week-plus course with baseline and follow-up panels.
2.12	The document is NOT written for the general population, who are unwilling to employ lifestyle and behavioral changes or follow protocols that may be inconvenient, costly, or require effort.	🟢	Not written for a general audience: functional targets, titration cadence and formulation distinctions assume commitment.
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 lede explicitly separates the solid topical case from the thin oral case and flags the mortality signal as observational, which is the distinction that matters for this audience.
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 strings “anti-aging” and “antiaging” do not occur in the QRS.
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.	🟢	The lede uses “Taken orally” rather than the ER conclusion’s “Taken by mouth” (ER line 489); no “pill”, “shot” or “bad reaction” phrasing occurs anywhere.

3. Template Integrity

#	Description	Result	Comments
3.1	The following labels and headings on the QRS are fixed and not modified: Card and section headings: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”; Gate headings: “Contraindications”, “Key Interactions”; Tier labels: “High”, “Medium”, “Low”, “Speculative”; Table column headers in Monitoring: “Marker”, “Target”, “Why”	🟢	All fixed headings verified verbatim: “Protocol”, “Time to effect”, “Benefits”, “Risk & Side Effects”, “Monitoring”, “Qualitative Assessment”, “Contraindications”, “Key Interactions”, the four tier labels, and “Marker” / “Target” / “Why”.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	Diffed the QRS span set against the template: all 34 template anchors present, the only additions being the legitimate repetitions of the marker_#* row (7x) and qualitative_item# (6x).
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	A normalised structural diff against the template shows no change outside the variable spans; the website=”evidence_review”, website=”audit” and website=”full_review” spans and the footer disclaimer 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	No ER section feeding a QRS surface is empty, so no empty-state phrasing is required.
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 labels are the ER bold labels verbatim: “Standardized capsule approach”, “Topical over-the-counter approach”, “Prescription patch approach” (ER lines 363, 367, 369).
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	No invented or paraphrased labels; gate-item shortening is confined to the parenthetical trimming that items 8.5 and 9.5 explicitly permit.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	No emoji characters anywhere in the file; the ER’s tier emoji are correctly dropped, as is the “WARNING Conflicted” marker on three ER headings.
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.	🟢	Each section is held to its budget: gate and tier items are single clauses, the lede is 68 words, and the monitoring “Why” column is condensed from the ER’s longer sentences.

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.	🟢	Metadata comment occupies lines 2-14, immediately after <!doctype html> and before any other content.
5.2	Inside that HTML comment the YAML block is delimited by a line “—” opening and a line “—” closing. Text before the opening “—” is permitted but is not parsed as YAML.	🟢	YAML opens at line 3 and closes at line 13; the preceding text “QRS - Metadata (invisible, parsed by audit tooling)” sits outside the delimiters.
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 and not echoed by any element on the sheet.
5.4	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	All values trimmed and unquoted except duration: “00:02”, which contains a colon and therefore requires quoting.
5.5	The filename of the source ER is stated as “er_filename: [er_filename]”	🟢	Line 4: er_filename: capsaicin_2026-0905-0306_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.22, matching the version badge 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-0922-1629, in YYYY-MMDD-HHMM form.
5.8	The nickname of the AI used to create the document is stated as “qrs_creator_ai_nickname: [qrs_creator_ai_nickname]”	🟢	Line 7: qrs_creator_ai_nickname: Opus
5.9	The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT)	🟢	“Opus” is a single word with no version or qualifier.
5.10	The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]”	🟢	Line 8: qrs_creator_ai_fullname: Opus 5
5.11	The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4)	🟢	“Opus 5” is nickname plus version number with no additional qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Line 9: qrs_filename: capsaicin_2026-0905-0306_Opus_QRS.html, matching the file on disk.
5.13	All frontmatter values are trimmed: no leading or trailing whitespace, no surrounding quotes unless the value contains a colon, bracket, or leading special character that requires YAML quoting.	🟢	Re-verified: no stray whitespace or unnecessary quoting in any frontmatter value.

6. Page Title & Header

#	Description	Result	Comments
6.1	[page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &)	🟢	Line 22: “Capsaicin for Health & Longevity - Quick Reference Sheet”, the ER canonical_topic with the ampersand entity-encoded.
6.2	[header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &)	🟢	Line 417: “Capsaicin for Health & Longevity”, matching ER canonical_topic (ER line 8).
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	Line 421: 09/22/2026, the MM/DD/YYYY form of qrs_creation_date 2026-0922-1629.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	Line 425: “Opus 5”, matching qrs_creator_ai_fullname.
6.5	No additional header content appears: no badge, version stamp, AKA / alternate names line, source-AI attribution, audit date, or QRS variant marker.	🟢	Header carries only the title and the template subline; no AKA line, badge, version stamp or audit date.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] opens by saying what the intervention is — its kind (e.g., dietary supplement, prescription medication, peptide, plant, procedure, practice) — and what it is used for, in plain language, before any verdict on the evidence	🟢	Opens “Capsaicin, the compound that makes chili peppers hot, is sold as a capsule, a skin cream, and a prescription patch for nerve pain” - kind and use stated before any verdict.
7.2	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Condenses the ER Conclusion (lines 489-491): solid topical case, thin oral case, observational mortality signal.
7.3	[at_a_glance] is no longer than 70 words	🟢	68 words, counted programmatically.
7.4	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause traces to a distinct ER passage: ER line 37 (what it is and its forms), line 489 (topical case solid, nasal rhinitis, oral changes small and inconsistent, observation rather than experiment).
7.5	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms or specialist classifications; “chronic runny nose” stands in for non-allergic rhinitis and “blood fats” for lipids.
7.6	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial names, years, sample sizes or p-values.
7.7	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No effect sizes, hazard ratios, confidence intervals or other statistics.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	Drawn from the ER “Populations who should avoid capsaicin” list inside Key Interactions & Contraindications (ER lines 331-339).
8.2	[stop_items] represent the Contraindications from the ER	🟢	All seven ER avoid-populations are represented, one to one, with none omitted or added.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	All seven items are discrete <li></li> elements inside the stop_items span (lines 556-562).
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.	🟢	Trailing rationale stripped throughout: “given reactive metabolite formation” and “where human safety data are absent” (ER lines 336-337) are gone; no dash-led 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).	🟢	Qualifiers preserved: Los Angeles grade C or D, at or above 160/100 mmHg, within 90 days, Child-Pugh Class B or C, and the oral / topical / patch form markers.
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 contraindication bullets use no ranking notation inside 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 section is populated, and the ER does name populations that should avoid capsaicin, so the emptiness condition correctly does not apply.
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	🟢	Drawn from the ER interaction bullets in Key Interactions & Contraindications (ER lines 315-329).
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	All eight ER interaction bullets are present and none duplicates a contraindication.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	All eight items are discrete <li></li> elements inside the caution_items span (lines 570-577).
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 “Mitigation:” clause and mechanistic explanation is stripped; the human platelet study link at ER line 319 is not carried through.
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).	🟢	Example drug lists preserved in full for all six bullets that carry them, including black pepper extract / BioPerine and the thermogenic and lipid-supplement stacks.
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 interaction bullets use no ranking notation inside parentheses.
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 section is populated and the ER does identify interactions, so the emptiness condition correctly does not apply.
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 action cells come from the ER Therapeutic Protocol section (lines 363, 367, 369).
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The three cells cover the three dose-defined delivery routes - oral capsule, topical cream, prescription patch - which are the implementable aspects the rest of the sheet’s gates, timings and monitoring are keyed to.
10.3	If less that three distinct actionable implementation aspects are mentioned in the ER the unused sets are left empty and made invisible, not filled with placeholder text or empty-state phrasing.	N/A	The ER describes more than three actionable implementation aspects, so 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 action fields carry substantive ER-derived content; no placeholders remain.

11. Time to Effect

#	Description	Result	Comments
11.1	The three sets of [time] items cover the three most important time-to-effect aspects from the ER	🟢	The three cells reproduce the three aspects of the ER Practical Considerations time-to-effect bullet (line 418) plus the 12-week interval from Monitoring Protocol (line 450).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Ordered High to Low by related benefit tier: patch analgesia (High), thermogenic and appetite effects (Medium), body-composition and lipid changes (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 describes three distinct time-to-effect aspects, so 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 time fields carry substantive ER-derived content.
11.5	If the ER does not provide any information on time to effect, the section is removed completely from the Protocol Panel	N/A	The ER does provide time-to-effect information, so the section is correctly retained.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	All four tiers are drawn from the ER Expected Benefits section (lines 151-223).
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four benefit spans are present and populated (lines 530-546).
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 the ER sub-headings alone; no magnitudes, confidence intervals, trial counts or mechanisms are carried through.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content survives; the ER’s “WARNING Conflicted” markers on two Low-tier headings are dropped.
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 benefit tiers contain 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 four tiers are drawn from the ER Potential Risks & Side Effects section (lines 241-295).
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four risk spans are present and populated (lines 589-604).
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.	🟢	Items are the ER sub-headings alone; no relative risks, odds ratios, incidence figures or mechanisms are carried through.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parenthetical content survives; the ER’s “WARNING Conflicted” markers on the two Low-tier headings are dropped.
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 risk tiers contain 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	🟢	Table rows are taken from the ER Monitoring Protocol & Defining Success biomarker table (lines 452-460).
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All seven ER biomarkers are present with their functional ranges intact: waist circumference, fasting triglycerides, total cholesterol, HbA1c, seated blood pressure, hs-CRP 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.	🟢	Populated from ER line 450: baseline panel, 2-week symptom review, 12-week full panel, then every 6-12 months, with the topical and patch exception retained.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	The six items come from the qualitative-marker list in the same ER Monitoring Protocol & Defining Success section (lines 464-469).
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All six ER qualitative markers are listed, one per span, in ER order.

Issues 22/09/2026 16:43

Pass rate 100.00%. No issues found.

Issues 22/09/2026 16:36

1. 4.5 — Sheet overflows one A4 page: Modelled render height is roughly 1.9 A4 pages; the Monitoring “Why” column (lines 628–694) and the Qualitative Assessment items (lines 713–734) carry ER wording over verbatim instead of being condensed to the per-section budget, and contraindication 3 (line 558) wraps to a third line.

Fixes 22/09/2026 16:36

1. 4.5 — Monitoring “Why” column condensed: Shortened all seven marker_#_why cells from verbatim ER prose to single-line equivalents (e.g. “Covers the theoretical liver burden from reactive capsaicin metabolites” to “Theoretical liver burden from reactive metabolites”), cutting the Monitoring card by roughly 70px.
2. 4.5 — Qualitative items trimmed: Removed the trailing elaborations from qualitative_item_1 (“especially during dose titration” to “during titration”) and qualitative_item_3 (dropped “the mechanism through which energy intake falls”).
3. 4.5 — Contraindication wrap reduced: Tightened the hypertension/infarction item to “Uncontrolled hypertension at or above 160/100 mmHg or myocardial infarction within 90 days (patch)”, keeping both thresholds and the time window while dropping one wrapped line.