Audit: QRS - PAI-1 Inhibitors for Health & Longevity
Audit conducted on 01/09/2026 17:15 using AI4L / Opus 5
Summary
| Items | Count |
|---|---|
| Total | 93 |
| Passed | 85 |
| Failed | 0 |
| N/A | 8 |
| 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; all trace to ER text (e.g. protocol cells to ER lines 321/323/331, time cells to ER line 378, monitoring rows to ER table lines 406-415). |
| 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 framing preserved: ‘No approved protocol exists’, ‘Registered trials only’, ‘all without comparison groups’, ‘None is approved anywhere’. |
| 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 and severity classes carried across unchanged. |
| 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. | 🟢 | Benefit- and Risk-Modifying Factors are not surfaced anywhere; gates draw only from the ER Key Interactions & Contraindications 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. | 🟢 | Only brand/compound name used is TM5614 (action_2_sub), which the ER names for the same regimen fact. No PMIDs, NCT IDs, author names or years appear. |
| 1.6 | The QRS does not introduce new attributions. | 🟢 | No attributions introduced; no expert, institution, or sponsor is named anywhere 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. | 🟢 | Matches the ER’s sober, evidence-limited register throughout. |
| 2.2 | The tone of the QRS is simultaneously expert, accessible, objective, and data-driven, but also empowering and encouraging | 🟢 | Expert, objective and data-driven; the restrained framing tracks the ER’s own evidence base rather than overselling. |
| 2.3 | The QRS reads as a trusted, knowledgeable guide rather than a prescriptive doctor | 🟢 | Presents trial-derived facts; no directive voice. |
| 2.4 | The QRS avoids language that implies medical or clinical advice | 🟢 | No advice language; protocol cells are framed as what investigators did inside registered trials. |
| 2.5 | The QRS “presents information” instead of “providing guidance”, “recommending”, or “advising” | 🟢 | No ‘recommend’, ‘advise’ or ‘should’ constructions in the document’s own voice. |
| 2.6 | The QRS never addresses “the reader” directly — it presents evidence, not guidance | 🟢 | No second-person address anywhere in the file. |
| 2.7 | The QRS is written in plain language, avoiding unnecessary medical jargon | 🟢 | Plain language used where possible; residual technical terms (Child-Pugh, HOMA-IR, eGFR) are ER-sourced biomarker and gate names that cannot be dropped without losing the decision content. |
| 2.8 | Information is presented in a concise and very compact manner | 🟢 | Gate and tier items are reduced to noun phrases; rationale, mechanism and citations stripped. |
| 2.9 | It DOES NOT address the reader directly | 🟢 | Confirmed — 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. | 🟢 | Framing suits risk-aware self-directed adults: access route, dose, timing and monitoring panel are foregrounded. |
| 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. | 🟢 | Monitoring cadence and 10-marker panel assume willingness to follow an effortful protocol. |
| 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 pitched at the general population; assumes biomarker literacy. |
| 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. | 🟢 | Correctly signals that no legitimate route exists for a healthy adult, which is the decisive point 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. | 🟢 | No occurrence of ‘anti-aging’ or ‘antiaging’; ‘Longevity’ used in the title and At-A-Glance. |
| 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. | 🟢 | ‘oral medications’, ‘adverse’-register terminology used; no colloquialisms in the document’s own voice. |
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 match [qrs_template] byte-for-byte: ‘Protocol’, ‘Time to effect’, ‘Benefits’, ‘Risk & Side Effects’, ‘Monitoring’, ‘Qualitative Assessment’, ‘Contraindications’, ‘Key Interactions’, tier labels, and ‘Marker’/’Target’/’Why’. |
| 3.2 | All “<span data-qrs-var=”NAME”>…</span>” from the [qrs_template] are present in the the QRS. | 🟢 | All 34 distinct template spans present; repeatable marker_#* and qualitative_item# rows instantiated 10x and 5x respectively. |
| 3.3 | Spans that are not addressed in a checklist item are left unchanged | 🟢 | Head, CSS and the three elements are identical to the template; only checklist-addressed spans differ. |
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 is empty. The ER’s High tiers carry explanatory text (‘No benefit reaches High…’, ‘No adverse effect reaches High…’), which items 12.5/13.5 govern instead. |
| 4.2 | Where the ER presents a bulleted item as “Label: content”, the QRS uses the ER’s bold label verbatim as the cell or row label. | 🟢 | Protocol labels are the ER’s bold labels verbatim (‘No approved protocol exists’, ‘Standard trial regimen’, ‘Best time of day’); monitoring marker names and ‘Why’ cells are verbatim from the ER table. |
| 4.3 | Labels are not paraphrased, abbreviated, or invented. | 🟢 | No paraphrased or invented labels; time-to-effect labels (‘Molecular response’, ‘Tumour response’, ‘Oxygen requirement’) are taken verbatim from ER line 378. |
| 4.4 | The QRS DOES NOT use emoji indicators (no 🟩, 🟥, 🟨, etc.). Color and emphasis are conveyed through CSS and bold labels. | 🟢 | No emoji present anywhere in the file; the ER’s tier squares and the two ‘⚠️ Conflicted’ markers were correctly 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. | 🟢 | Condensation applied as required: benefit/risk tiers reduced to ER headings only, gate glosses and mechanistic rationale stripped, marker targets trimmed. Remaining volume (11 contraindications, 10 markers) is mandated by items 8.2 and 14.2. |
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 opens at line 2, immediately after <!doctype html>, 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 delimited by ‘—’ at lines 3 and 13; the preceding ‘QRS — Metadata’ text sits outside the block, which is permitted. |
| 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; not surfaced 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; only ‘duration: “00:04”’ is quoted, which is required because the value contains a colon. |
| 5.5 | The filename of the source ER is stated as “er_filename: [er_filename]” | 🟢 | er_filename: pai_1_inhibitors_2026-0901-1524_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]” | 🟢 | qrs_prompt_version: 26.7.02, 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) | 🟢 | qrs_creation_date: 2026-0901-1707 — correct 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]” | 🟢 | qrs_creator_ai_nickname: Opus |
| 5.9 | The nickname of the AI is just a single word model name without version, etc. (e.g., Opus, Sonnet, Grok, Gemini, ChatGPT) | 🟢 | Single word, no version or qualifier. |
| 5.10 | The full name of the AI used to create the document is stated as “qrs_creator_ai_fullname: [qrs_creator_ai_fullname]” | 🟢 | qrs_creator_ai_fullname: Opus 5 |
| 5.11 | The full name of the AI consists of the [qrs_creator_ai_nickname] and the model version number and no additional qualifier (e.g., Opus 4.6, Sonnet 3.2, Grok 4.5, Gemini 3.1, ChatGPT 5.4) | 🟢 | Nickname plus version number only; no additional qualifier. |
| 5.12 | The filename of the document is stated as “qrs_filename: [filename of this document]” | 🟢 | qrs_filename: pai_1_inhibitors_2026-0901-1524_Opus_QRS.html — 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. | 🟢 | Confirmed; no stray whitespace or unnecessary quoting. |
6. Page Title & Header
| # | Description | Result | Comments |
|---|---|---|---|
| 6.1 | [page_title] is set to the [canonical_topic] of the ER frontmatter followed by “ - Quick Reference Sheet” (e.g., “Intervention - Quick Reference Sheet”). The [canonical_topic] is HTML-entity-encoded as needed (e.g., & for &) |
🟢 | |
| 6.2 | [header_topic] is set to the [canonical_topic] of the ER frontmatter, with HTML entities encoded as needed (e.g., & for &) |
🟢 | header_topic is ‘PAI-1 Inhibitors for Health & Longevity’, entity-encoded. |
| 6.3 | [header_subline_date] is set to [qrs_creation_date reformatted as MM/DD/YYYY] | 🟢 | 09/01/2026, correctly derived from qrs_creation_date 2026-0901-1707. |
| 6.4 | [header_subline_model] is set to [qrs_creator_ai_fullname] | 🟢 | header_subline_model is ‘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 is byte-identical to the template apart from the two variable spans; no badge, AKA line, or audit stamp added. |
7. At-A-Glance Section
| # | Description | Result | Comments |
|---|---|---|---|
| 7.1 | [at_a_glance] is dense, execution-oriented summary of the ER Conclusion section |
🟢 | Condenses the ER Conclusion (lines 451-457) into the access-decisive points: mechanism, the genetic basis of the longevity claim, the narrowness of human data, and the absence of approval. |
| 7.2 | [at_a_glance] is no longer than 60 words | 🟢 | 57 words — under the 60-word limit. |
| 7.3 | Every fact in [at_a_glance] is supported by a distinct passage in the ER. | 🟢 | Each clause maps to a distinct Conclusion passage; ‘None is approved anywhere’ is additionally supported by ER line 365. |
| 7.4 | It DOES NOT use acronyms or technical classifications that require specialist knowledge, uses plain-language terms instead | 🟢 | No acronyms or specialist classifications; ‘PAI-1’, ‘SERPINE1’, ‘fibrinolysis’ and ‘senescence’ are all avoided in favour of plain paraphrase. |
| 7.5 | It DOES NOT cite specific trials (names, years, sample sizes, p-values) | 🟢 | No trial names, years, sample sizes or p-values. |
| 7.6 | It DOES NOT cite effect sizes, relative risks, or statistical results | 🟢 | No effect sizes, relative risks, or statistical results. |
8. Contraindications
| # | Description | Result | Comments |
|---|---|---|---|
| 8.1 | The section is derived from the ER Key Interactions & Contraindications section |
🟢 | Drawn from the ER Key Interactions & Contraindications section (lines 270-301). |
| 8.2 | [stop_items] represent the Contraindications from the ER | 🟢 | All 10 items of the ER ‘Populations who should avoid’ list are present, plus thrombolytic agents, which the ER’s interaction bullet labels an ‘Absolute contraindication’ (line 276). |
| 8.3 | Individual [stop_items] are formatted as <li></li> | 🟢 | Each item is its own <li> inside the [stop_items] 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. | 🟢 | Explanatory glosses stripped (‘a tangle of abnormal blood vessels’, ‘a ballooned artery wall’, ‘clots in the veins or lungs’); no trailing rationale, citations, or dash 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). | 🟢 | Thresholds and windows preserved: ‘below 50 × 10⁹/L or haematocrit below 30%’, ‘within 90 days’, ‘(systolic above 200 mmHg beyond 12 hours)’, ‘Child-Pugh Class B or C (moderate to severe)’. |
| 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 section is populated; the ER does identify populations that should avoid the intervention. |
| 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. <!– empty: ER names no population that should avoid the intervention –> | 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 Key Interactions & Contraindications section (lines 272-288). |
| 9.2 | [caution_items] represent the Key Interactions from the ER, excluding any that are already listed as Contraindications | 🟢 | Seven of the ER’s nine interaction bullets are carried. Thrombolytics and anticoagulants are correctly omitted because both are already captured in [stop_items] (‘Thrombolytic agents’, ‘Concurrent full-dose anticoagulation’). |
| 9.3 | Individual [caution_items] are formatted as <li></li> | 🟢 | Each item is its own <li> inside the [caution_items] 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. | 🟢 | Mechanistic glosses and mitigation clauses stripped (e.g. ‘which stop platelets clumping’, ‘which release brakes on the immune system’); no dash-trailing content 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). | 🟢 | Named example drug lists preserved in full for all seven items, including the nine-item supplement list and the four named procedures. |
| 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 section is populated; the ER does identify interactions that change how the intervention is used. |
| 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. <!– empty: ER names no interaction that changes how the intervention is used –> | N/A | The section is not empty. |
10. Protocol
| # | Description | Result | Comments |
|---|---|---|---|
| 10.1 | The section is derived from the ER Protocol section |
🟢 | Drawn from the ER Therapeutic Protocol section (lines 319-345). |
| 10.2 | The three sets of [action] items cover the three most important actionable implementation aspects from the ER Protocol section |
🟢 | The three chosen aspects are the access gate, the dose regimen, and the dosing time — the only directly actionable bullets in the ER’s protocol list; the remainder are ‘no data established’ entries. |
| 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 names more than three actionable implementation aspects, so no set is left unused. |
| 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 | 🟢 | All three time-to-effect aspects the ER states (ER line 378) are represented. |
| 11.2 | The sets are picked and ordered by the magnitude of the related benefit | 🟢 | Ordered by benefit tier: molecular response (Medium), tumour response (Medium), oxygen requirement (Low) — matching the ER’s own ordering within tiers. |
| 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, so no set is left unused. |
| 11.4 | All used [time_#label], [time#value], [time#_sub] items are filled with meaningful content derived from the ER. | 🟢 | All nine time fields populated from ER line 378; time_3_sub also carries the ER’s caveat that no longevity timeline exists. |
| 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 |
🟢 | Drawn from the ER Expected Benefits section (lines 130-198). |
| 12.2 | Key variables are [benefits_high], [benefits_medium], [benefits_low], [benefits_speculative] | 🟢 | All four benefit spans present and correctly named. |
| 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 reduced to the ER’s own subsection headings; no magnitudes, confidence intervals, mechanisms, or citations carried over. |
| 12.4 | Parenthetical content — including effect sizes, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | All parenthetical content stripped; no ‘(95% confidence interval …)’ or sample notes appear. |
| 12.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | [benefits_high] is emptied and set to style=”display: none”; the ER’s ‘No benefit reaches High’ sentence is correctly not reproduced. |
13. Risks
| # | Description | Result | Comments |
|---|---|---|---|
| 13.1 | The section is derived from the ER Potential Risks & Side Effects section |
🟢 | Drawn from the ER Potential Risks & Side Effects section (lines 214-254). |
| 13.2 | Key variables are [risks_high], [risks_medium], [risks_low], [risks_speculative] | 🟢 | All four risk spans present and correctly named. |
| 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 reduced to the ER’s own subsection headings; the ‘⚠️ Conflicted’ marker and all mechanism text stripped. |
| 13.4 | Parenthetical content — including frequencies, severity grades, sample notes, mechanistic hints, and example studies — is stripped, NOT preserved. | 🟢 | No frequencies or severity grades carried over; the ER’s ‘2 of 34 patients (5.9%)’ and ‘grade 3 or higher’ are absent. |
| 13.5 | If no items of a specific sub-section (high, medium, low, speculative) are present the respective <SPAN> is set to “display=none”, not filled with “None documented in human trials to date” or similar empty-state phrasing. | 🟢 | [risks_high] is emptied and set to style=”display: none”; the ER’s ‘No adverse effect reaches High’ sentence is correctly not reproduced. |
14. Monitoring
| # | Description | Result | Comments |
|---|---|---|---|
| 14.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from the ER Monitoring Protocol & Defining Success section (lines 400-415). |
| 14.2 | All measurable/quantifiable biomarkers from the Monitoring section are listed |
🟢 | All 10 ER biomarker rows are present in order, with targets and ‘Why’ cells matching the ER table. |
| 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. |
🟢 | Cadence populated from ER line 402: ‘Baseline, one week, four weeks, eight weeks, then every three months … tightening to weekly …’. |
15. Qualitative Assessment
| # | Description | Result | Comments |
|---|---|---|---|
| 15.1 | The section is derived from the ER Monitoring section |
🟢 | Drawn from the qualitative marker list at the end of the ER Monitoring Protocol & Defining Success section (lines 419-423). |
| 15.2 | All subjective/qualitative biomarkers from the Monitoring section are listed |
🟢 | All five ER qualitative markers are reproduced verbatim. |
Issues 01/09/2026 17:15
Pass rate 100.00%. No issues found.