Audit: QRS - Combining Daraxonrasib, Afatinib & SD-36 to Treat Cancer

Audit conducted on 12/09/2026 23:56 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.	🟢	Spot-checked every span: protocol doses (ER Therapeutic Protocol), time-to-effect values (ER Practical Considerations), all 10 markers and cadence (ER Monitoring Protocol & Defining Success), gates (ER Key Interactions & Contraindications), benefit/risk tiers (ER Expected Benefits / Potential Risks & Side Effects).
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.	🟢	“untested in people”, “No human equivalent”, “No phase 1 dose-finding study registered”, “No target; change from own baseline” mirror ER wording.
1.3	The QRS never strengthens an ER claim (e.g., “not formally studied” → “not required”) or softens one (e.g., “do not use during pregnancy” → “use with caution during pregnancy”).	🟢	Contraindications retain absolute framing; speculative benefits stay in the Speculative tier.
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.	🟢	[stop_items] come only from the ER “Populations who should avoid” list; [caution_items] only from the ER interaction bullets; no modifying factors migrated.
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 IDs, author names or brand names anywhere in the QRS.
1.6	The QRS does not introduce new attributions.	🟢	No attributions present.

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.	🟢	Matches the ER’s sober, trade-off-forward register.
2.2	The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging	🟢	Facts stated without hedging or alarm.
2.3	The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor	🟢	No imperatives directed at a reader.
2.4	The QRS avoids language that implies medical or clinical advice	🟢	Protocol and gates are stated as documented facts, not instructions.
2.5	The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising”	🟢	No recommending verbs used.
2.6	The QRS never addresses “the reader” directly — it presents evidence, not guidance	🟢	No second-person pronouns in the file.
2.7	The QRS is written in plain language, avoiding unnecessary medical jargon	🟢	Technical terms are limited to biomarker and drug-class names carried from the ER.
2.8	Information is presented in a concise and very compact manner	🟢	All items are phrase-length; no sentences of explanation.
2.9	It DOES NOT address the reader directly	🟢	Confirmed by full-text 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.	🟢	Content assumes an informed reader weighing a high-toxicity oncology regimen.
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.	🟢	Food-separation rule, daily symptom tracking and dense monitoring schedule are presented without softening.
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 simplification toward a general-population 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.	🟢	At-a-glance states the trio is untested in people and added toxicity certain — the decisive signal 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 term does not appear.
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.	🟢	“orally once daily”, “intravenous dosing”, “medications” used throughout; no lay route phrasing.

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 verbatim.
3.2	All “…” from the [qrs_template] are present in the the QRS.	🟢	All 34 template variables present; marker_#* expanded to 10 rows and qualitative_item# to 7 items as designed.
3.3	Spans that are not addressed in a checklist item are left unchanged	🟢	The three website= spans and all CSS/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”	🟢	The ER’s ### Low 🟥 risk tier is empty and carries no empty-state phrase; the QRS adds none and hides the span per 13.5.
4.2	Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label.	🟢	“Daraxonrasib component”, “Afatinib component”, “SD-36 component”, “Time to effect”, “Time to side effects” are the ER’s bold labels verbatim.
4.3	Labels are not paraphrased, abbreviated, or invented.	🟢	The one non-bulleted label, “Blood-based tumor DNA”, is lifted verbatim from the ER Practical Considerations sentence it summarizes.
4.4	The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels.	🟢	Full-text scan returns no emoji code points.
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 rather than copied: benefit/risk items are heading-level only, gate items are stripped of rationale, marker “why” cells are single clauses, and no section spills ER 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.
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.
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 duplicate 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.	🟢	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, matches the ER filename frontmatter exactly.
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 matches 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)	🟢	qrs_creation_date: 2026-0912-2314.
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.
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” carries no context-window or other qualifier.
5.12	The filename of the document is stated as “qrs_filename: [filename of this document]”	🟢	Matches 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; all values 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 &)	🟢	“Combining Daraxonrasib, Afatinib & SD-36 to Treat Cancer - 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, entity-encoded ampersand.
6.3	[header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY]	🟢	2026-0912-2314 → 09/12/2026.
6.4	[header_subline_model] is set to [qrs_creator_ai_fullname]	🟢	“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 contains only the template’s title and subline.

7. At-A-Glance Section

#	Description	Result	Comments
7.1	[at_a_glance] is dense, execution-oriented summary of the ER Conclusion section	🟢	Tracks the ER Conclusion’s four moves: two approved agents plus one research compound, distinct mechanisms, the retracted-then-republished animal work, and certain toxicity against unproven combination benefit.
7.2	[at_a_glance] is no longer than 60 words	🟢	53 words.
7.3	Every fact in [at_a_glance] is supported by a distinct passage in the ER.	🟢	Each clause maps to ER Conclusion or Motivation text (“never been given to a person”, “prevented relapse”, “retracted … then republished”, “toxicity load that is certain”).
7.4	It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead	🟢	No acronyms; “growth signal”, “research compound”, “withdrawn” used in place of technical terms.
7.5	It DOES NOT cite specific trials (names, years, sample sizes, p-values)	🟢	No trial identifiers.
7.6	It DOES NOT cite effect sizes, relative risks, or statistical results	🟢	No numbers at all.

8. Contraindications

#	Description	Result	Comments
8.1	The section is derived from the ER Key Interactions & Contraindications section	🟢	All seven items come from the ER “Populations who should avoid” list.
8.2	[stop_items] represent the Contraindications from the ER	🟢	7 ER bullets → 7 QRS items, one-to-one.
8.3	Individual [stop_items] are formatted as <li></li>	🟢	Seven <li> elements inside the span.
8.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	Rationales stripped (“for whom the expected benefit does not offset the toxicity burden”, “since it has no human safety data at any dose”, “the worst category on the standard liver function score”).
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).	🟢	“Child-Pugh Class C”, “below 30 mL/min/1.73 m²”, “at least 2 weeks after the last dose”, “any grade”, “grade 3 or higher” 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 in these bullets.
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 populated; the emptiness condition 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	🟢	All ten items map to the ER’s ten interaction bullets.
9.2	[caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications	🟢	10 of 10 interaction bullets carried; no overlap with the contraindication list.
9.3	Individual [caution_items] are formatted as <li></li>	🟢	Ten <li> elements inside the span.
9.4	Items are as concise as possible. No trailing explanations, no elaborations, no mechanistic rationale, no attributions, no citations, no study details. No content after an em-dash, en-dash, or hyphen-dash (e.g., “— dose reduction required”, “— reduced efficacy”) — these trailing clauses are stripped. Just the key fact.	🟢	Consequences and mitigations dropped; glossary asides such as “two classes of stomach-acid-reducing drugs” removed.
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).	🟢	Every named-drug list preserved, including “ciclosporin, absolute avoid” and the supplement examples.
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 these 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.	N/A	The section is populated; the emptiness condition 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 cells come from the ER Therapeutic Protocol bullets.
10.2	The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section	🟢	The per-agent dosing of each of the three components, with food separation folded into the afatinib sub-line.
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 three distinct aspects; all 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.	🟢	Nine cells populated; dose ranges, reduction steps and the absent phase 1 study all trace to ER 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	🟢	Imaging response (~8 weeks), circulating tumor DNA (2-4 weeks), and onset of side effects (first 2 weeks).
11.2	The sets are picked and ordered by the magnitude of the related benefit	🟢	Tumor response (High-tier benefit) first, its earlier blood proxy second, toxicity onset last.
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	Three distinct aspects exist in the ER; all sets are used.
11.4	All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER.	🟢	Nine cells populated from ER Practical Considerations.
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.

12. Benefits

#	Description	Result	Comments
12.1	The section is derived from the ER Expected Benefits section	🟢	Each tier lists the ER’s own benefit headings.
12.2	Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative]	🟢	All four present and populated.
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.	🟢	Heading-level phrases only; no magnitudes, no sponsor notes, no “⚠️ Conflicted” marker.
12.4	Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheticals remain in any tier.
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 carry items in the ER.

13. Risks

#	Description	Result	Comments
13.1	The section is derived from the ER Potential Risks & Side Effects section	🟢	All items are ER risk headings.
13.2	Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative]	🟢	All four present.
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.	🟢	8 high, 8 medium and 3 speculative items, each a bare heading phrase; no odds ratios or incidence figures.
13.4	Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved.	🟢	No parentheticals remain.
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’s ### Low 🟥 tier is empty and [risks_low] carries style="display:none" with no empty-state text (line 583).

14. Monitoring

#	Description	Result	Comments
14.1	The section is derived from the ER Monitoring section	🟢	Table mirrors the ER biomarker table.
14.2	All measurable/quantifiable biomarkers from the Monitoring section are listed	🟢	All 10 ER rows present in order: hemoglobin, ANC, ALT, AST, total bilirubin, sodium, potassium/magnesium, eGFR, ctDNA, CA 19-9.
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.	🟢	Baseline, week 2 and 4, 4-weekly to 6 months, then 8-12-weekly; imaging 8-weekly for a year then 12-weekly — matches the ER text.

15. Qualitative Assessment

#	Description	Result	Comments
15.1	The section is derived from the ER Monitoring section	🟢	Items come from the ER’s “Qualitative markers worth tracking” list.
15.2	All subjective/qualitative biomarkers from the Monitoring section are listed	🟢	All 7 ER qualitative markers present, one per list item.

Issues 12/09/2026 23:56

Pass rate 100.00%. No issues found.

Issues 12/09/2026 23:49

1. 4.2 / 4.3 — Interaction label paraphrased: The ninth Key Interactions item (QRS line 564) uses the invented label “Supplements with additive toxicity” instead of the ER’s verbatim bold label “Supplements with additive effects on the same toxicities:” (ER line 371).

Fixes 12/09/2026 23:49

1. 4.2 / 4.3 — Interaction label restored verbatim: Changed the ninth Key Interactions item from “Supplements with additive toxicity” to the ER’s verbatim bold label “Supplements with additive effects on the same toxicities”, keeping the example-supplement parenthetical.

Issues 12/09/2026 23:42

1. 4.5 — Sheet renders at about two A4 pages: At the template’s own print geometry the sheet totals roughly 2160 px against ≈1030 px of usable A4 height, driven mainly by the Key Interactions gate (lines 555-566, ≈414 px) and the Monitoring card (lines 593-719, ≈528 px), with action_2_sub (line 461), at_a_glance (line 433) and eight Monitoring target / why cells each wrapping further than necessary.

Fixes 12/09/2026 23:42

1. 4.5 — At-a-glance shortened: Trimmed the lede from 60 to 53 words (“Benefit from each approved drug alone is well documented” → “Each approved drug works alone”), dropping one wrapped line from a 16 px block.
2. 4.5 — Protocol cells tightened: Condensed all three action_#_sub cells (e.g. “Continuous, reduced to 30 mg or 20 mg for toxicity. Empty stomach: with daraxonrasib, at least one hour before or two hours after food.” → “Continuous; 30 or 20 mg for toxicity. Empty stomach with daraxonrasib, 1 h before or 2 h after food.”), cutting the action row from five wrapped lines to three.
3. 4.5 — Time-to-effect cells tightened: Shortened time_1_sub and time_3_sub to one-clause statements, cutting the time row from three wrapped lines to two.
4. 4.5 — Key Interactions supplement item shortened: Rewrote the longest gate item as “Supplements with additive toxicity (high-dose magnesium, vitamin C, inulin, high-dose niacin, green tea)”, saving a line while keeping all five named examples.
5. 4.5 — Monitoring cells condensed: Shortened eleven target and why cells (rows 1, 2, 5, 6, 7, 8, 9, 10) so each now fits a single line, cutting roughly eight wrapped lines from the biomarker table; all ten biomarkers and their functional ranges are retained.
6. 4.5 — Monitoring cadence condensed: Rewrote the cadence sentence using interval notation (“then every 4 weeks for 6 months” → “4-weekly for 6 months”), preserving every interval the ER states.

Issues 12/09/2026 23:34

1. 1.3 — At-a-glance overstates single-agent evidence: [at_a_glance] (line 433) claims “Benefit from each drug alone is well documented”, but the ER states SD-36 “has never been given to a person” (ER line 555) and that it has no human data at any dose, so the claim is strengthened beyond the ER for one of the three agents.

Fixes 12/09/2026 23:34

1. 1.3 — At-a-glance single-agent claim narrowed: Changed “Benefit from each drug alone is well documented” to “Benefit from each approved drug alone is well documented”, so the claim no longer extends to SD-36, which the ER states has never been given to a person. At-a-glance remains within the 60-word limit.

Issues 12/09/2026 23:28

1. 1.1 / 7.3 — Retraction reason misstated: At-a-glance (line 433) says the animal report was “withdrawn over undisclosed author finances”; the ER (lines 39, 156, 557) states it was retracted because three authors held undisclosed financial interests, a conflict-of-interest disclosure failure rather than a matter of the authors’ personal finances.
2. 1.3 — “at least” dropped from two windows: Contraindication 1 (line 542) gives “for 2 weeks after the last dose” where ER line 377 says “for at least two weeks”, and action_2_sub (line 461) gives “one hour before or two hours after food” where ER line 417 says “at least one hour before or two hours after food”; both convert an ER minimum into an exact window.

Fixes 12/09/2026 23:28

1. 1.1 / 7.3 — Retraction reason corrected: At-a-glance now reads “withdrawn over the authors’ undisclosed financial interests” instead of “withdrawn over undisclosed author finances”, matching the ER’s conflict-of-interest wording; “the added toxicity” was trimmed to “added toxicity” to keep the passage at 59 words.
2. 1.3 — “at least” restored in two windows: The contraception contraindication now reads “for at least 2 weeks after the last dose” and the afatinib food-separation sub-cell now reads “at least one hour before or two hours after food”, restoring the ER’s minimum-window phrasing.

Issues 12/09/2026 23:22

1. 4.5 — Sheet overruns one A4 page: The QRS carries uncondensed ER prose well past the one-page budget — every Qualitative Assessment item retains its trailing rationale clause (lines 727-746), the circulating tumor DNA and CA 19-9 targets restate the same “track against the individual’s own baseline” sentence in full (lines 697, 708), and the Protocol subs (lines 450, 461, 472) and two Key Interactions items (lines 558, 564) carry explanatory tails.

Fixes 12/09/2026 23:22

1. 4.5 — Qualitative items stripped of rationale: Removed the trailing explanatory clauses from six of the seven Qualitative Assessment items (e.g. “Breathlessness and cough, tracked deliberately because gradual onset is easy to attribute to the disease” → “Breathlessness and cough, including gradual onset”), keeping all seven ER markers.
2. 4.5 — Monitoring targets condensed: Shortened the two open-ended targets to “No established target; change from own baseline” and “No established optimal value; trend against own baseline”, and tightened the cadence line without dropping any interval.
3. 4.5 — Protocol subs tightened: Condensed all three action subs (e.g. “Any human use would require a phase 1 dose-finding study; no such study has been registered.” → “Human use would require a phase 1 dose-finding study; none registered.”) and trimmed the redundant lead from the tumor DNA time-to-effect sub.
4. 4.5 — Gate items shortened: Trimmed the contraception contraindication and the P-glycoprotein and supplement interaction parentheticals (“ciclosporin is an absolute avoid under the daraxonrasib label” → “ciclosporin, absolute avoid”), preserving every named drug, threshold and time window.