European Commission, Shaping Europe's Digital Future

https://digital-strategy.ec.europa.eu/en/news

ADDED as candidate by the 2026-08-09 weekly run (this run's one new candidate): the European Commission's own 'Shaping Europe's Digital Future' newsroom, which is where CRA, NIS2 and AI Act developments are announced first. This deployment's standing policy watch names NIS2 and the CRA (2026-08-29: DORA and FINMA left the watch when the constituency narrowed to the Swiss public sector), but no source record covered the Commission newsroom even though a prior weekly already cited an article on this host as its primary. FETCH -> a direct fetch returns an empty JS application shell with no rendered article list; `python3 tools/fetch_source.py jina https://digital-strategy.ec.europa.eu/en/news` renders a clean dated listing (verified 2026-08-09, surfaced the 2026-07-27 CRA guidance and the AI Omnibus entry-into-force items). No RSS path found on the page. EUR-Lex was evaluated as the alternative and rejected as a polling source: it has no what's-new-in-cyber-policy listing and is better used as an ad-hoc legal-text lookup, as this run did for Regulation (EU) 2026/1744. Promote to active after 3 contributing runs. | 2026-08-10: candidate -> active. The state digest counted 5 distinct contributing runs, past the 3-run promotion bar; promoted mechanically from the counted evidence rather than by eyeball, per the allocation rule. | 2026-09-30 intel run: `extract` reads the newsroom without the reader. | 2026-09-29: fetch_method jina -> bridge: source_health reads it relevant and current over the direct transport, so it no longer needs the metered reader. (2026-09-29 operator-directed setup review) | 2026-10-22 (main): HTTP 403 (CloudFront 'request could not be satisfied') on the direct transport, the reader and WebFetch on 2026-10-22; a 403 never demotes, so the record stays in rotation and the next fire re-tests it. | 2026-10-23 (main): HTTP 403 (CloudFront) on the direct transport, extract, the reader and WebFetch on 2026-10-23, as on 2026-10-22; fetch_method set to blocked so health classes it handled, status stays active (a 403 never demotes); re-test at the next audit and restore bridge if extract reads it again. | 2026-10-27 (S2): 403 (CloudFront) on every transport again, including the reader fallback, `url --direct`, the feed and WebFetch; policy items from the Commission were probed by WebSearch only. | 2026-10-29 (S2): HTTP 403 on extract, url --direct and WebFetch, fourth consecutive run; the Commission press-corner JSON API is the partial substitute. | 2026-10-30 (2026-10-30T0255Z-intel, S2): `extract https://digital-strategy.ec.europa.eu/en/news` now returns the News & Views page (trafilatura direct, page date 2026-10-26) with undated highlight items and no hrefs, so drill each item for its date; fetch_method moved from blocked to bridge. | 2026-10-31 (2026-10-31T0256Z-intel health sweep): the origin reads again: `fetch_source.py feed https://digital-strategy.ec.europa.eu/en/rss.xml 5` returns dated items with links (all digital-policy news, so the record is a general-news source whose NIS2 and CRA items are rare); fetch_method moved from bridge to rss and the record left the transport-blocked set in tools/source_health.py. | 2026-11-02 intel run (S2): `feed https://digital-strategy.ec.europa.eu/en/rss.xml 15` returns ten dated items; content is general digital policy (DSA, AI Act), nothing to change.