Objection (high): Defective callout and directive option sets. 'ATTENTION: SCAMMEDS' is not a word, not an audience, and reads as victim-blaming. 'Send this to any september you know' and 'Forward this to the septembers in your life' are extraction artifacts — 'September' was scraped out of the byline 'IRS Tax Tip 2021-142, September 27, 2021' and mistaken for an audience entity. 'Send this to any fraudster you know' instructs readers to forward a fraud alert to fraudsters. Four of the eight offered options are unusable and two are actively harmful if selected. The fact that share_directive resolved to null does not cure the option list; a defective menu means the next pick can be wrong. All four should be struck before publication.
Resolved: Partially mitigated by share_directive being null, so no defective directive was actually published in this pass. The option list itself remains uncorrected.
Objection (high): Same extraction failure visible in targeting_dropped: 'DIRECTIVE NOT IN EVIDENCE: filing — no harvested source describes this group.' 'Filing' is a verb lifted from 'help victims file casualty loss claims', not a group. Together with 'september' and 'scammeds', this is three independent noun-phrase misparses from one two-row harvest. That is a systemic entity-extraction problem, not three isolated typos, and it should lower confidence in any other entity-derived field in this record.
Not resolved — preserved on the record.
Objection (high): Date currency is never surfaced to the reader. The sole substantive source is IRS Tax Tip 2021-142, dated September 27, 2021 — over four years old. The date appears only in the evidence limitation and confidence_reasons, i.e. in the machinery, not in the finding text the audience reads. The finding opens 'An IRS tax tip states...' in the bare present, and the claim is written in the timeless present ('criminals make unsolicited contact'). A reader would reasonably infer a current IRS advisory. The publication date belongs in the first finding sentence.
Not resolved — preserved on the record.
Objection (medium): Standing guidance is dressed as an incident alert. Nothing in either row reports an actual campaign, a victim, a loss, a named fake charity or a specific disaster. This is evergreen advisory copy the IRS reissues periodically. Yet the package carries an alert framing, an 'ATTENTION: DISASTER VICTIMS AND DONORS' callout and a risk_line written as though money is currently moving. The limitation sentence covers scale ('unknown to us') but never says the plainer thing: no harvested source reports any actual incident. That sentence should be added.
Not resolved — preserved on the record.
Objection (medium): Row b82e5efc is typed etype SOURCED on the strength of a headline alone — no body, no date, no author. A bare title supports exactly one proposition: that a page with that title exists at that URL. Typing it SOURCED alongside a fully quoted advisory creates a false impression of two-source corroboration for a claim that in fact rests on one document. It should be downgraded (title-only / existence-only) or dropped, and confidence_reasons should say plainly that the second row contributes zero corroboration to the claim rather than the softer 'adds little beyond its title'.
Resolved: Partially pre-resolved: the draft already carries a dedicated limitation sentence ('Our harvested material does not include the body text of the second IRS item, only its title') and an accurate evidence-level limitation. My objection is confined to the etype label and the softness of the confidence_reasons wording, not to concealment.
Objection (medium): Orphaned unknown. 'Whether the deductible-contribution figures cited for tax year 2021 still apply' refers to figures the alert never cites — the draft correctly omitted the $300/$600 above-the-line deduction. As written the unknown implies the alert relied on those numbers. Worse, it frames an expired provision as merely uncertain: that deduction lapsed after tax year 2021. If the line is kept it should read as a source-staleness marker ('the source page contains a tax-year-2021 deduction provision that the alert does not repeat'), not as an open question.
Resolved: Partially mitigated: the draft did not repeat the expired $300/$600 figures in the finding, which was the right call. Only the unknowns entry is defective.
Objection (medium): The claim drops a scam vector the source explicitly records. The tip says: 'Also, taxpayers may search for a charity online and be directed to a website or social media page that is not affiliated with the actual charity.' That is victim-initiated contact, not unsolicited contact. The claim sentence states the tactic as unsolicited-contact-only, and the advice sentence ('never through a link, caller or message that came to you unasked') implicitly tells readers that self-initiated search is the safe route — which is the one route the source warns is also compromised. This is a real safety inversion, not a stylistic quibble. The advice must be amended to say search results themselves can be spoofed, hence look-up via the Tax Exempt Organization Search specifically rather than via general web search.
Not resolved — preserved on the record.
Objection (low): Source-to-claim stretch on the IRS-impersonation branch. The source says the thieves 'say they can help victims file casualty loss claims and get tax refunds'; it does not say what they extract. The claim rolls this into 'to take money and personal financial details from disaster victims'. The motive is a plausible inference but it is an inference, and the claim states it as reported fact.
Not resolved — preserved on the record.
Objection (low): Republishing an operational phone number (866-562-5227) harvested from a four-year-old page without any current-verification marker. The number is likely still live, but the harvest cannot establish that, and a stale hotline number in a fraud alert is a reuse target. It should be attributed in-line as listed in the 2021 tip.
Resolved: Partially mitigated: the number is attributed to 'the tip' in the finding sentence, which signals it is quoted rather than independently verified, though the tip's date is not given alongside it.
Objection (low): URL form. Both rows are recorded as 'irs.gov/newsroom/...' without scheme or host prefix. The canonical IRS host is www.irs.gov. Domain match is genuine and I do not dispute authenticity, but bare truncated URLs in a phishing-awareness product set a poor example and should be rendered in full canonical form.
Not resolved — preserved on the record.
Preserved dissentON THE RECORDI do not accept that this package is publication-ready. Four of eight offered share/callout options are extraction garbage, two of them ('send this to any fraudster you know', 'ATTENTION: SCAMMEDS') are affirmatively bad copy, and the fact that the current pass happened to select none of them is luck, not control.
ON THE RECORDThe most serious substantive defect is OBJ-07 and I want it recorded even if the Desk disagrees. The source warns twice about victim-initiated search leading to spoofed charity pages. The draft's advice sentence tells readers to 'look the charity up yourself' and to distrust only inbound contact. That is precisely the failure mode the IRS flagged, and the draft has inverted the source's safety guidance while appearing to follow it. Advice that is not merely unsupported but contrary to the cited source is worse than advice with no row_ids.
ON THE RECORDI regard the second harvested row as evidentiary padding. A headline with no body, no date and no author establishes that a URL exists and nothing else. Listing it as SOURCED evidence with a claim_sentence gives a one-source alert the visual weight of a two-source alert. The disclosure sentence is honest, but honest disclosure does not make a title into evidence, and the row should have been dropped rather than dressed.
ON THE RECORDOn currency: publishing a September 2021 advisory in the present tense with no date in the reader-facing text is a real misrepresentation of freshness, regardless of whether the underlying advice remains sound. Advice being still-true and a source being still-current are different claims, and this draft lets the reader conflate them.