{ "row": "iptc-metawatch", "entity": "iptc-metawatch", "address": "IPTC Metawatch", "addresses": [ { "address": "IPTC Metawatch", "slug": "iptc-metawatch-aio-20261029", "addr_id": "ADDR-d50977993169", "obs_id": "OBS-7f18ba03c974", "axn": "AXN:0ACF.CAPTURE.🔩🟤◀️⛵⏫🌻" } ], "epoch": "2026-10-29", "type": "C (public entity on which the archive bears: a monitor of photo-metadata survival; an entity of the provenance meta-aggregator)", "surface": "Google AI Overview (expanded)", "auth": "signed out, incognito", "status": { "procedure": "EA-NEGONT-02 v0.9, #1690: equal case, ρ = extends, read from the provenance census record, the capture record and #725's statement of relation; archive selected by D/R/O (22 deposits admitted by reading, 14 with claims and 8 grouped as instances; 3 of them from the hop of 164), with the provenance census record (22 claims) and the Capture Registry's findings and analysis (13 claims) ledgered as the archive's records of the entity; the field B by origin (6 cards, the census's one own page carried as card 1, 2 Wikipedia sources); the composer read the ledgers, never the transcript, except where the brief asks for T's claims and the delta", "ledger": "unaudited (§3.8: one extractor per ledger); field quotes 41/41 verified by script against saved text, the Wikipedia response summary or the card text; archive quotes 63/63 verified against the registry, census.json and the deposit texts", "frozen": false, "breaches": [] }, "spec": "EA-NEGONT-02 v0.9, #1690", "objects": { "T": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/T1-iptc-metawatch-aio-20261029.txt", "sha256": "f3fbe313559dac5937b0fa7b4d714abff7bc0c6ef00c7c2b834d212441b89023", "words": 123, "cards": 6, "words_note": "one transcript at one address (123 words in the answer body including the closing offer, links reduced to their text, citation markers and the card rail excluded; 6 cards)", "claims": [ "T1-1 definition: 'The International Press Telecommunications Council (IPTC) launched Metawatch, a free and open public monitoring tool that tracks how news publishers handle photo metadata.'", "T1-2 monthly checks: 'Automatically crawls and analyzes news websites every month to see if embedded metadata survives publication.'", "T1-3 global scale: 'Monitors over 500 news publishers across 122 countries.'", "T1-4 metadata tracked: 'Checks whether crucial embedded details—such as credits, captions, copyright notices, Exif data, and IPTC/XMP photo metadata—are preserved or stripped when images are published online.'", "T1-5 per-field breakdown: 'Provides a Metawatch Field Breakdown to evaluate performance on specific metadata attributes.'", "T1-6 closer (an offer): 'Would you like to know more about how to check a specific publisher's score or how to properly embed IPTC photo metadata into your own images?'" ], "register": { "register": "data/EA-WG-CAPTURES-01.json", "slug": "iptc-metawatch-aio-20261029", "obs_id": "OBS-7f18ba03c974" }, "transcripts": [ { "address": "IPTC Metawatch", "slug": "iptc-metawatch-aio-20261029", "addr_id": "ADDR-d50977993169", "obs_id": "OBS-7f18ba03c974", "axn": "AXN:0ACF.CAPTURE.🔩🟤◀️⛵⏫🌻", "date": "2026-10-29", "surface": "Google AI Overview (expanded)", "auth": "signed out, incognito", "sha256": "f3fbe313559dac5937b0fa7b4d714abff7bc0c6ef00c7c2b834d212441b89023", "sha256_of": "the registry's 'transcript' string (utf-8)", "sha256_raw": "b61bab5780693da6a81f663af57e6bc106d822c5255eb1182d5284fe8ba54fee", "words": 123, "cards": 6, "card_rail": [ "1. IPTC — Announcing Metawatch: a monthly check on which news publishers keep ... - IPTC", "2. IPTC — Overview — Metawatch - IPTC", "3. LinkedIn·Paul Melcher — IPTC Publishes Metawatch, Revealing Image Metadata Issues - LinkedIn", "4. IPTC — Per-field breakdown - Metawatch - IPTC", "5. IPTC — Watching AI platforms, news publishers and real-world C2PA - IPTC", "6. IPTC — Photo Metadata Archives - IPTC" ], "claims": [ "T1-1 definition: 'The International Press Telecommunications Council (IPTC) launched Metawatch, a free and open public monitoring tool that tracks how news publishers handle photo metadata.'", "T1-2 monthly checks: 'Automatically crawls and analyzes news websites every month to see if embedded metadata survives publication.'", "T1-3 global scale: 'Monitors over 500 news publishers across 122 countries.'", "T1-4 metadata tracked: 'Checks whether crucial embedded details—such as credits, captions, copyright notices, Exif data, and IPTC/XMP photo metadata—are preserved or stripped when images are published online.'", "T1-5 per-field breakdown: 'Provides a Metawatch Field Breakdown to evaluate performance on specific metadata attributes.'", "T1-6 closer (an offer): 'Would you like to know more about how to check a specific publisher's score or how to properly embed IPTC photo metadata into your own images?'" ], "markers": "Inline links are google.com/goto tokens, opaque; the paste is the Overview expanded (operator's default of 2026-10-01; the 'AI Mode Conversation' view is the Overview expanded, ruled 2026-10-18); signed out and incognito (operator's default of 2026-10-14). The 'You said' line carried the query twice and is given once in the registry's transcript.", "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/T1-iptc-metawatch-aio-20261029.txt" } ] }, "KO": { "title": "IPTC Metawatch", "genre": "knowledge object, equal case, under EA-NEGONT-02 v0.9 (#1690): the archive's sources and the field's admitted on equal terms, ontology included, in one claim space", "status": "composed 2026-10-29 under v0.9 (briefs rebuild/negative-of-the-negative/v09/BRIEF-NEW-ROW-AGGREGATOR.md and BRIEF-NEW-ROW-PROVENANCE.md); not frozen; ledgers unaudited", "sentences": [ { "n": 1, "para": 0, "sense": "what it is", "text": "IPTC Metawatch is the International Press Telecommunications Council's free, open monitor of whether news publishers keep the credits, captions and rights information embedded in their photographs, checked every month across more than 500 publishers in 122 countries (IPTC announcement, 5 October 2026); the provenance census record types it as a monitor of the media lineage whose capability is to test, its provenance object 'the lead photograph of a news article, as served to the reader', its operator the IPTC at metawatch.iptc.org (provenance census record).", "claims": [ "F1", "PE-01", "PE-02", "PE-04", "PE-03" ] }, { "n": 2, "para": 0, "sense": "what it is", "text": "Its own overview states the object from the side of the carrier: Metawatch 'tracks how often major news publishers preserve embedded photo metadata' — Exif, IPTC Photo Metadata in its IIM and XMP forms, and C2PA — and scores the photographs a curated list of publishers serves (Metawatch overview), the carrier the census record names as 'embedded metadata (Exif, IPTC IIM and XMP) and C2PA manifests' (provenance census record).", "claims": [ "F21", "PE-06" ] }, { "n": 3, "para": 0, "sense": "what it is", "text": "Content Credentials stand in the first of the dimensions of provenance the archive's provenance packet distinguishes: frameworks for the artifact (C2PA / Content Credentials) and for the corpus 'are not designed to address the survival of authorial lineage through AI synthesis', artifact provenance verifying that 'this file' was created by 'this source' at 'this time', at the moment of creation (#725); the same packet places IPTC AI metadata at 'Layer 1 metadata', 'Disclosure, not lineage' (#725).", "claims": [ "O725-01", "O725-03", "O725-07" ] }, { "n": 4, "para": 1, "sense": "the method", "text": "On the first of each month its crawler visits 508 news publishers in 122 countries, takes up to 20 recent articles from each and reads the lead photograph of every article, checking Exif, IPTC Photo Metadata and C2PA Content Credentials and scoring creator, caption, copyright and credit line, 'the “4 Cs”' (IPTC announcement); the census record's unit is 'a news publisher, sampled each month through up to 20 recent articles', its count 508 publishers in 122 countries as of October 2026, monthly on the first, its relation types creator, credit, copyright, caption, the PLUS data-mining preference and Content Credentials (provenance census record); the per-field page calls the four scored fields 'the \"Four Cs\" of news photo provenance', the others tracked for context (Metawatch per-field breakdown).", "claims": [ "F5", "F6", "PE-07", "PE-10", "PE-05", "F28" ] }, { "n": 5, "para": 1, "sense": "open data", "text": "The crawler is 'deliberately light', about 40 to 60 requests per publisher a month, honouring robots.txt and keeping no article text or image files, and every run is published as open data under CC BY 4.0, new results appearing on the first of every month (IPTC announcement); the overview names it 'A project of the International Press Telecommunications Council', its data CC BY 4.0, with an opt-out for publishers by email (Metawatch overview), and the census record carries 'every run published as open data' under 'CC BY 4.0 (each run's data)' (provenance census record).", "claims": [ "F7", "F19", "F26", "PE-11" ] }, { "n": 6, "para": 2, "sense": "the transformation tested", "text": "What it tests is a transformation: credits 'are lost between camera and reader' as content management systems re-encode images, delivery networks resize them and optimisation tools discard what looks like unnecessary bytes, and once an image is copied or collected by an AI crawler its embedded metadata 'is often the only record of where it came from and on what terms it may be used' (IPTC announcement); the census record names the transformation tested 'publication through a news site's pipeline (CMS, CDN, image optimisation)' (provenance census record).", "claims": [ "F3", "F4", "PE-08" ] }, { "n": 7, "para": 2, "sense": "the transformation tested", "text": "The archive's packet states the loss one layer on: 'A C2PA-signed image whose caption is rewritten by a model that strips the photographer's name has lost semantic provenance even though artifact provenance is preserved', the dimensions being independent, so that 'Solving any one dimension does not solve the others' (#725).", "claims": [ "O725-05", "O725-04" ] }, { "n": 8, "para": 3, "sense": "predecessors", "text": "Metawatch builds on IMATAG's 2018 State of Image Metadata study and the IPTC's own prototype crawler of 2019, and differs in measuring every month (IPTC announcement; the census record quotes the sentence as its lineage evidence, provenance census record), and the census record relates it as part of the IPTC's photo-metadata tests, beside the census's C2PA conformance entry, while keeping it apart from the earlier test: 'NOT the 2019 IPTC social-media test: it measures news publishers monthly' (provenance census record).", "claims": [ "F8", "PE-17", "PE-15", "PE-13" ] }, { "n": 9, "para": 4, "sense": "the dates", "text": "Its overview dates five runs, the first on 2026-06-03 and then monthly to 2026-10-01 (Metawatch overview), and the announcement counts 294 publishers 'measured every month since June' (IPTC announcement).", "claims": [ "F23", "F12" ] }, { "n": 10, "para": 4, "sense": "the dates", "text": "The IPTC's post of 8 September 2026 reports that at the 2026 Photo Metadata Conference, held 'Last Thursday', Brendan Quinn 'appeared again to introduce Metawatch', 'IPTC’s new public service that monitors real-world usage of metadata in images across the global news industry, tracking IPTC/XMP, C2PA, AI opt-outs and more' (IPTC, 8 September 2026); Paul Melcher's LinkedIn post of 14 September 2026, read by its card alone, says the IPTC 'now publishes Metawatch' (LinkedIn card); the conference took as its focus AI transparency and content provenance, 'tracking real-world adoption of content transparency technologies by AI engines, news sites, software and services' (IPTC, 8 September 2026).", "claims": [ "F32", "F34", "F27", "F33" ] }, { "n": 11, "para": 4, "sense": "the dates", "text": "The announcement is dated 5 October 2026 and is the newest post under the IPTC's Photo Metadata tag (IPTC announcement; Photo Metadata archive); the census record's lifecycle is active, 'announced 5 October 2026', its founding given the same way, the run reported for October 2026 and the record read on 2026-10-29 (provenance census record).", "claims": [ "F20", "F35", "PE-12" ] }, { "n": 12, "para": 4, "sense": "the dates", "text": "The Capture Registry records the difference: the record 'dates the monitor by its announcement, 5 October 2026', two cards date it earlier, the IPTC post of 8 September and Melcher's post of 14 September, and the September showing is carried at the capture 'unchecked against the posts themselves' (Capture Registry, 2026-10-29).", "claims": [ "CAP-1-05", "CAP-1-06", "CAP-1-07" ] }, { "n": 13, "para": 5, "sense": "findings", "text": "In the October run 7.2% of editorial images carried a credit or copyright notice, against IMATAG's 8% in 2018, so that keeping the photographer's credit attached 'has not improved'; 321 of the 425 publishers it could crawl kept none of the scored IPTC fields; 11% of 6,580 images carried any IPTC metadata, the photographer's name on 7.9%, the credit line on 5.7%, copyright on 5.6% (IPTC announcement); the census record's retention results carry the 7.2% and the 321 of 425 with the 27 of 6,580 images bearing a C2PA manifest (provenance census record), and the announcement reads its first results as showing 'how little has changed since 2018' and why metadata 'matters more than ever now that AI companies are crawling the web' (IPTC announcement).", "claims": [ "F9", "F10", "PE-09", "F2" ] }, { "n": 14, "para": 5, "sense": "findings", "text": "The overview gives the latest run as 2026-10-01, 425 sites, 122 countries and 6,580 images, a mean IPTC score of 5.96, 11% with any IPTC and 0.5% with C2PA, and says that 'Any average describes almost nobody here' (Metawatch overview); the per-field page counts over 6,514 images, Creator at 7.9%, CreditLine 5.7%, Copyright 5.3%, CaptionDescription 5%, the licensing fields below 3% (Metawatch per-field breakdown), so that copyright stands at 5.6% in the announcement and at 5.3% on the per-field page.", "claims": [ "F22", "F24", "F29", "F31", "F10" ] }, { "n": 15, "para": 6, "sense": "where the stripping happens", "text": "On where the loss happens the operator's pages differ in emphasis: the announcement finds 'It isn’t the CDN’s fault', images through Cloudflare, Akamai, CloudFront and Fastly losing their metadata 87% to 95% of the time and images with no CDN 87%, so that 'Stripping appears to happen in the publishing pipeline', the fix 'usually a setting, not a project' (IPTC announcement; the census record quotes the pipeline sentence as its evidence, provenance census record), while the per-field page reads its dataset as 'publishers and CDNs are discarding metadata that the photographers and agencies almost certainly embedded upstream' (Metawatch per-field breakdown).", "claims": [ "F11", "F18", "PE-19", "F31" ] }, { "n": 16, "para": 6, "sense": "the archive's artifacts", "text": "The archive's specification for machine-eligible handwritten artifacts embeds IPTC Creator (the author or heteronym), Credit, CopyrightNotice, Headline, Description and DateCreated in every published derivative, with an XMP mirror and C2PA manifests wrapping the IPTC/EXIF assertions (#1409); it records embedded IPTC photo metadata as extracted by Google and travelling with the image, its composition role unknown, 'scaffold the pipeline provably reads' (#1409); and it carries the same fields in a visible membrane because 'physically embodied metadata survives screenshot, rehosting, filename change, metadata stripping, PDF embedding, and sidecar loss', under a triple redundancy of pixels, embedded IPTC/XMP/C2PA and external records (#1409).", "claims": [ "R1409-01", "O1409-02", "O1409-04", "R1409-05" ] }, { "n": 17, "para": 6, "sense": "the archive's artifacts", "text": "The archive's identifier stamp for a lossless image sits in its EXIF ImageDescription or UserComment (#1432), and its self-audit protocol plans a 'Hash/signature manifest (C2PA-compatible) binding provenance claims to deposited objects' (#204).", "claims": [ "R1432-01", "R204-01" ] }, { "n": 18, "para": 7, "sense": "movement", "text": "Some publishers moved: USA Today from no credit metadata in 2019 to 95% of its lead photographs carrying credit, creator and copyright in September, Les Echos from 6% to 75%, and across the 294 publishers measured monthly since June those keeping any metadata rose from 60 to 67; France led October at 19.8 of 100, ahead of Germany at 19.2, with only countries of more than three scored publishers ranked (IPTC announcement).", "claims": [ "F12", "F13" ] }, { "n": 19, "para": 8, "sense": "AI and Content Credentials", "text": "Of 505 publishers whose policies were checked, 234 block at least one AI crawler in robots.txt, but 'robots.txt protects a website, not a photograph', and the PLUS Data Mining field appears on 0.6% of images (IPTC announcement); the archive's training-layer protocol holds that robots.txt and C2PA, which it does not call useless, operate 'primarily at the publication / legal / evidentiary layer rather than at the training-survival layer' (#127).", "claims": [ "F15", "O127-01" ] }, { "n": 20, "para": 8, "sense": "AI and Content Credentials", "text": "Leaving out the IPTC's own site, 27 of 6,580 images carried a C2PA manifest, all but one signed by an AI or design tool and none 'from a camera or a newsroom’s own signing', and seven carried a Digital Source Type disclosing generative-AI editing, so that, in the announcement's reading, provenance in news photography 'is arriving first through the tools that make synthetic images' (IPTC announcement); the per-field page finds DigitalSourceType on 0.2% of images and the AI prompt and AI system fields on none (Metawatch per-field breakdown), properties the IPTC Photo Metadata Standard added for AI-generated content on 27 November 2025 (Photo Metadata archive).", "claims": [ "F16", "F17", "F30", "F36" ] }, { "n": 21, "para": 8, "sense": "AI and Content Credentials", "text": "The archive's packet calls the adoption of artifact authenticity 'uneven' and C2PA's ingredient assertions 'optional, under-adopted' (#725), and its field manual holds that C2PA standards and watermarking have not 'achieved sufficient adoption to function as infrastructure' (#499).", "claims": [ "O725-02", "O725-06", "O499-01" ] }, { "n": 22, "para": 8, "sense": "trust anchors", "text": "The archive reads C2PA's trust as a device's: C2PA 'attests what a device reports having done' where a content-derived identifier 'computes what the bytes are', validation optional in the first, the two complementary (#1443), C2PA anchoring in device and issuer certificates and the AXN regime in content derivation and a public ledger (#1409), C2PA securing 'the camera's testimony, not the author's' (#1444).", "claims": [ "O1443-01", "O1443-02", "O1409-07", "O1444-01" ] }, { "n": 23, "para": 8, "sense": "disclosure", "text": "It declares a nonsynthetic capture by the IPTC DigitalSourceType inside the file, 'in the same controlled vocabulary whose trainedAlgorithmicMedia value marks the synthetic class', and holds that 'C2PA, FADGI, and IPTC provenance vocabularies are the same insight arriving as standards' (#1409).", "claims": [ "R1409-03", "O1409-06" ] }, { "n": 24, "para": 9, "sense": "stated limits", "text": "The monitor states its limits: the United States slipped from first to fourth in October because AP and USA Today 'began blocking automated access this month', 'a reminder that bot-blocking aimed at AI also shuts out research' (IPTC announcement; quoted in the census record's evidence, provenance census record), and publishers reached without a photograph are listed as no_images rather than scored zero, 'usually our blind spot rather than their practice' (Metawatch overview); the census record leaves unchecked 'the Metawatch site itself and its published run data' and IMATAG's 2018 study, and marks the monitor 'NOT a C2PA verifier' (provenance census record).", "claims": [ "F14", "PE-18", "F25", "PE-16", "PE-14" ] }, { "n": 25, "para": 10, "sense": "beyond the file", "text": "The archive holds the artifact dimension necessary and insufficient: C2PA 'prevents forgery; it does not constitute authorship' (#729), 'C2PA authenticates media' and does not cover text (#621), and 'When a 5,000-word article becomes a 200-word AI Overview, C2PA cannot tell you what was lost' (#615).", "claims": [ "O729-01", "O729-02", "O621-01", "O615-01" ] }, { "n": 26, "para": 10, "sense": "beyond the file", "text": "It finds that metadata standards, C2PA among them, do not address the measurable reception consequences of provenance and attribution (#833), that provenance and attribution studies, C2PA among them, 'have focused on attribution loss in AI outputs' (#1003), and that cross-format content provenance standards give 'starting points for the public and machine-readable layers' (#95).", "claims": [ "O833-01", "O1003-01", "O95-01" ] }, { "n": 27, "para": 11, "sense": "reception", "text": "On Google's AI Overview, signed out, on 2026-10-29, the Capture Registry finds the method and scale right ('Every month', 'more than 500 news publishers in 122 countries' and the fields are the announcement's own) and 'Free and open' matched to the census record's licence quote, checked against that record and the pages it saved (Capture Registry, 2026-10-29).", "claims": [ "CAP-1-01", "CAP-1-02", "CAP-1-03" ] }, { "n": 28, "para": 11, "sense": "reception", "text": "It finds the findings absent, 'The composition gives what the monitor checks and none of what it found', and the access limit not composed; it reads the Overview first as naming 'the maker, the method and the scale of a monitor three weeks old', then as composing 'A new provenance monitor' 'at the grain of its feature list', when what it measures is 'the erasure of credit in the publishing pipeline', carrying 'the instrument' and leaving out 'its reading', the IPTC photo metadata capture's pattern 'in small: the carrier composed, the loss omitted' (Capture Registry, 2026-10-29).", "claims": [ "CAP-1-04", "CAP-1-08", "CAP-1-09", "CAP-1-10", "CAP-1-11" ] }, { "n": 29, "para": 11, "sense": "reception", "text": "At the capture the IPTC is named, Paul Melcher and Brendan Quinn appear only in cards, no identifier is given and the monitor's own pages are cited, and no card cites the census record, which landed on provenanceerasure.org the same day (Capture Registry, 2026-10-29).", "claims": [ "CAP-1-13", "CAP-1-12" ] }, { "n": 30, "para": 12, "sense": "the record and the encyclopedia", "text": "The census record asks of each entity 'What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?', each quote verbatim from a saved source, and for Metawatch read one source, the announcement, on 2026-10-29 (provenance census record); Wikipedia has no article on IPTC Metawatch and no article text naming it beside the IPTC, and its article on the operator, which does not name Metawatch, describes the IPTC as 'a consortium of the world's major news agencies, other news providers and news industry vendors' acting as 'the global standards body of the news media', whose photo metadata, the IIM set that XMP has largely superseded, is 'by far IPTC's most widely used standard' (Wikipedia).", "claims": [ "PE-20", "PE-21", "PE-22", "F37", "F38", "F39", "F40", "F41" ] } ], "joins": [ { "act": "order of senses", "sentences": "1–30", "claims": [], "note": "equal case (§4.7): the entity's dependency order (what it is, the method, open data, the transformation tested, predecessors, the dates, the findings, where the stripping happens, the archive's artifacts, movement, AI and Content Credentials, limits, beyond the file, reception, the record and the encyclopedia), field and archive claims ordered together by genealogy within each sense; neither ledger placed first as a block" }, { "act": "holding together (two figures for copyright)", "sentences": [ 14 ], "claims": [ "F10", "F29" ], "note": "P_coh within the field: the announcement's 5.6% (of 6,580 images) and the per-field page's 5.3% (of 6,514) both composed with their sources; the KO says only that they differ" }, { "act": "holding together (where the loss happens)", "sentences": [ 15 ], "claims": [ "F11", "F31", "PE-19" ], "note": "P_coh within the operator's pages: 'It isn’t the CDN’s fault … Stripping appears to happen in the publishing pipeline' against 'publishers and CDNs are discarding metadata'; both composed, each with its page, at its modality (interpretation)" }, { "act": "holding together (the dates)", "sentences": [ 9, 10, 11, 12 ], "claims": [ "F23", "F12", "F32", "F34", "F27", "F20", "PE-12", "CAP-1-05", "CAP-1-06", "CAP-1-07" ], "note": "the runs from 2026-06-03, the September showing and the October announcement composed in one sense with the census record's lifecycle and the capture's account of the difference; the KO does not resolve which date the entity begins at (open block)" }, { "act": "placing beside (the carrier and the archive's dimension)", "sentences": [ 2, 3 ], "claims": [ "F21", "PE-06", "O725-01", "O725-03", "O725-07" ], "note": "#725 names C2PA / Content Credentials and IPTC AI metadata as the artifact layer; the KO places Content Credentials and IPTC AI metadata there and does not extend #725's category to Exif, which #725 does not name" }, { "act": "placing beside (the finding and the archive's artifacts)", "sentences": [ 15, 16, 17 ], "claims": [ "F11", "R1409-01", "O1409-04", "R1409-05" ], "note": "the archive's embedding of the same fields and its membrane against stripping composed after the field's account of where the stripping happens; no claim is made that the archive's images were measured by the monitor" }, { "act": "placing beside (Content Credentials adoption)", "sentences": [ 20, 21, 22 ], "claims": [ "F16", "O725-02", "O725-06", "O499-01", "O1444-01", "O1443-01" ], "note": "the monitor's 27 of 6,580 manifests, none from a camera, composed before the archive's statements of uneven adoption and of C2PA as the camera's testimony; held together as a sense, not called a confirmation" } ], "plan": { "order": [ "F1", "PE-01", "PE-02", "PE-04", "PE-03", "F21", "PE-06", "O725-01", "O725-03", "O725-07", "F5", "F6", "PE-07", "PE-10", "PE-05", "F28", "F7", "F19", "F26", "PE-11", "F3", "F4", "PE-08", "O725-05", "O725-04", "F8", "PE-17", "PE-15", "PE-13", "F23", "F12", "F32", "F34", "F27", "F33", "F20", "F35", "PE-12", "CAP-1-05", "CAP-1-06", "CAP-1-07", "F9", "F10", "PE-09", "F2", "F22", "F24", "F29", "F31", "F11", "F18", "PE-19", "R1409-01", "O1409-02", "O1409-04", "R1409-05", "R1432-01", "R204-01", "F13", "F15", "O127-01", "F16", "F17", "F30", "F36", "O725-02", "O725-06", "O499-01", "O1443-01", "O1443-02", "O1409-07", "O1444-01", "R1409-03", "O1409-06", "F14", "PE-18", "F25", "PE-16", "PE-14", "O729-01", "O729-02", "O621-01", "O615-01", "O833-01", "O1003-01", "O95-01", "CAP-1-01", "CAP-1-02", "CAP-1-03", "CAP-1-04", "CAP-1-08", "CAP-1-09", "CAP-1-10", "CAP-1-11", "CAP-1-13", "CAP-1-12", "PE-20", "PE-21", "PE-22", "F37", "F38", "F39", "F40", "F41" ], "senses": { "what it is": [ 1, 2, 3 ], "the method": [ 4 ], "open data": [ 5 ], "the transformation tested": [ 6, 7 ], "predecessors": [ 8 ], "the dates": [ 9, 10, 11, 12 ], "findings": [ 13, 14 ], "where the stripping happens": [ 15 ], "the archive's artifacts": [ 16, 17 ], "movement": [ 18 ], "AI and Content Credentials": [ 19, 20, 21 ], "trust anchors": [ 22 ], "disclosure": [ 23 ], "stated limits": [ 24 ], "beyond the file": [ 25, 26 ], "reception": [ 27, 28, 29 ], "the record and the encyclopedia": [ 30 ] }, "case_by_sense": { "equal (one claim space; nothing translated)": [ "what it is", "the method", "open data", "the transformation tested", "predecessors", "the dates", "findings", "where the stripping happens", "the archive's artifacts", "movement", "AI and Content Credentials", "trust anchors", "disclosure", "stated limits", "beyond the file", "reception", "the record and the encyclopedia" ] }, "carried": { "archive": 63, "field": 41, "not_composed": {} }, "conflict_log": [ { "rule": "D_pres vs channel", "result": "no cut: the KO carries every field and archive claim; the compression's bound met (body 337 words) with no channel log" }, { "rule": "P_coh", "result": "F10 against F29 (sentence 14: copyright 5.6% or 5.3%); F11 against F31 (sentence 15: the pipeline, or publishers and CDNs); F20/PE-12 beside F23, F32, F34, F27 (sentences 9–12: the dates): each composed with its source" }, { "rule": "N_c", "result": "every claim at its source's modality: the announcement's 'appears' (F11) and 'arriving first' (F17) as its interpretations; the archive's readings (#725, #1409, #1443, #1444, #729, #499, #615, #621, #127, #833, #1003, #95) as interpretations or stipulations, as the ledger codes them; the capture's findings as the registry's observations and readings" }, { "rule": "O_leg", "result": "no opaque material in the ledgers" } ] } }, "P": { "title": "IPTC Metawatch", "genre": "the compression: AIO's interaction grammar (lede, headed clusters, bolded labels, card rail), composed from the v0.9 plan in one claim space; it faces on the card, with AIO's transcript a record within it", "status": "composed 2026-10-29 from the v0.9 knowledge object; not frozen", "lede": { "text": "is the IPTC's free, open monthly monitor of whether news publishers keep the photo metadata embedded in their images: 508 publishers in 122 countries, the lead photograph of up to 20 recent articles each, scored on creator, caption, copyright and credit line.", "claims": [ "F1", "F5", "F6", "PE-04", "PE-10" ] }, "sections": [ { "icon": "🗂️", "head": "What it is", "items": [ { "label": "Object:", "text": "the lead photograph as served to the reader; its carriers Exif, IPTC IIM and XMP, C2PA (census record; overview).", "claims": [ "PE-04", "PE-06", "PE-02", "F21" ] }, { "label": "Dimension:", "text": "artifact provenance, the file at its creation; IPTC AI metadata 'Disclosure, not lineage' (#725).", "claims": [ "O725-01", "O725-03", "O725-07" ] }, { "label": "Open:", "text": "every run CC BY 4.0, new results on the 1st (IPTC; census record).", "claims": [ "F7", "F19", "F26", "PE-11", "PE-03" ] } ] }, { "icon": "📅", "head": "When", "items": [ { "label": "Runs:", "text": "monthly from 2026-06-03 (overview).", "claims": [ "F23", "F12" ] }, { "label": "Shown:", "text": "introduced by Brendan Quinn at the Photo Metadata Conference (IPTC, 8 September); 'now publishes' (Paul Melcher, 14 September).", "claims": [ "F32", "F34", "F27" ] }, { "label": "Announced:", "text": "5 October 2026, the census record's date; the Capture Registry carries the earlier showing.", "claims": [ "F20", "F35", "PE-12", "CAP-1-05", "CAP-1-06", "CAP-1-07" ] } ] }, { "icon": "📉", "head": "What it found, October 2026", "items": [ { "label": "Credit:", "text": "7.2% of images (IMATAG, 2018: 8%).", "claims": [ "F9", "PE-09", "F2" ] }, { "label": "Nothing kept:", "text": "321 of 425 crawlable publishers; 11% of 6,580 images carry any IPTC field; copyright 5.6% (announcement) or 5.3% (per-field page).", "claims": [ "F10", "F22", "F24", "F29", "F31" ] }, { "label": "Content Credentials:", "text": "27 of 6,580 images, all but one signed by AI or design tools, none by a camera or newsroom.", "claims": [ "F16", "F17", "F30", "F36" ] }, { "label": "AI crawlers:", "text": "46% of publishers block one; the data-mining field is on 0.6% of images.", "claims": [ "F15" ] } ] }, { "icon": "🔧", "head": "Where it is lost", "items": [ { "label": "Pipeline:", "text": "87–95% lost with or without a CDN; stripping 'appears' to be the publisher's, the fix 'usually a setting' (IPTC; census record); the per-field page names publishers and CDNs.", "claims": [ "F3", "F4", "F11", "F18", "F31", "PE-08", "PE-19" ] }, { "label": "Beyond the file:", "text": "a signed image whose caption loses the photographer's name keeps artifact provenance, loses semantic provenance (#725); C2PA secures 'the camera's testimony, not the author's' (#1444).", "claims": [ "O725-05", "O725-04", "O1444-01", "O1443-01", "O1443-02", "O1409-07" ] }, { "label": "Against stripping:", "text": "the archive embeds Creator, Credit and Copyright in its own images and repeats them in the pixels (#1409).", "claims": [ "R1409-01", "O1409-02", "O1409-04", "R1409-05", "R1432-01" ] } ] }, { "icon": "⚠️", "head": "Limits", "items": [ { "label": "Access:", "text": "AP and USA Today blocked it in October: 'bot-blocking aimed at AI also shuts out research' (IPTC).", "claims": [ "F14", "PE-18" ] }, { "label": "Blind spots:", "text": "no photograph means no_images, not zero (overview); the census record left the site unchecked.", "claims": [ "F25", "PE-16" ] } ] }, { "icon": "👁️", "head": "On the Overview", "items": [ { "label": "Composed:", "text": "method and scale, right; findings, limit and dates, absent (Capture Registry, 2026-10-29).", "claims": [ "CAP-1-01", "CAP-1-02", "CAP-1-04", "CAP-1-08", "CAP-1-09" ] }, { "label": "Pattern:", "text": "'the carrier composed, the loss omitted' (Capture Registry).", "claims": [ "CAP-1-10", "CAP-1-11" ] } ] } ], "open": [ { "question": "When did Metawatch begin: with its first run, its showing at the conference, or its announcement?", "rests_on": [ "F23", "F12", "F32", "F34", "F27", "F20", "PE-12", "CAP-1-05", "CAP-1-06", "CAP-1-07" ], "modality": "documented, all (the overview's run dates, the September post, the LinkedIn card by snippet, the announcement, the census record's lifecycle)", "would_resolve": "the monitor's methodology or about page giving its first public date; the conference video; the LinkedIn post's text" }, { "question": "Is copyright on 5.6% of images or 5.3%?", "rests_on": [ "F10", "F29" ], "modality": "documented, both (the announcement over 6,580 images; the per-field page over 6,514)", "would_resolve": "the 2026-10-01 run's open data, counted by field over one denominator" }, { "question": "Is the metadata stripped by the publisher's pipeline, or by publishers and CDNs?", "rests_on": [ "F11", "F31", "PE-19" ], "modality": "interpretation, both (two of the operator's pages)", "would_resolve": "the run data by CDN and by publisher, with the image as uploaded compared to the image as served" }, { "question": "Does a credit kept in the file survive the composition that summarizes the page it is on?", "rests_on": [ "F4", "O725-05", "O615-01", "CAP-1-10" ], "modality": "interpretation (the announcement; #725; #615; the Capture Registry)", "would_resolve": "a capture at an address whose answer carries an image with IPTC credit embedded, checked for the credit in the composition" }, { "question": "Opacity: Paul Melcher's LinkedIn post.", "rests_on": [ "F27" ], "modality": "attributed (title and snippet only; the post could not be found or fetched)", "would_resolve": "the post's URL and text" } ], "rail": [ { "lineage": "what it is: a free, open monthly monitor of whether news publishers keep embedded photo metadata", "claims": [ "F1", "PE-01", "PE-02", "F21", "PE-14" ], "earliest": "B1" }, { "lineage": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "claims": [ "PE-04", "PE-06", "F5", "F6", "PE-07", "PE-10", "PE-05", "F28", "CAP-1-01" ], "earliest": "B1" }, { "lineage": "open data, cadence and the operator", "claims": [ "PE-03", "F7", "F19", "F26", "PE-11", "CAP-1-02" ], "earliest": "B1" }, { "lineage": "the artifact dimension of provenance", "claims": [ "O725-01", "O725-03", "O729-01", "O1003-01", "O95-01" ], "earliest": 95 }, { "lineage": "IPTC metadata as disclosure, not lineage", "claims": [ "O725-07", "R1409-03", "O1409-06" ], "earliest": 725 }, { "lineage": "the transformation tested: credit lost between camera and reader", "claims": [ "F3", "F4", "PE-08" ], "earliest": "B1" }, { "lineage": "artifact provenance kept, the meaning lost", "claims": [ "O725-05", "O725-04", "O127-01", "O729-02", "O621-01", "O615-01", "O833-01" ], "earliest": 615 }, { "lineage": "predecessors: IMATAG 2018 and the IPTC prototype crawler of 2019", "claims": [ "F8", "PE-17", "PE-15", "PE-13" ], "earliest": "B1" }, { "lineage": "dates: runs from June, a September showing, the October announcement", "claims": [ "F23", "F32", "F34", "F27", "F20", "PE-12", "CAP-1-05", "CAP-1-06", "CAP-1-07" ], "earliest": "B5" }, { "lineage": "movement: publishers and countries", "claims": [ "F12", "F13" ], "earliest": "B1" }, { "lineage": "the operator: the IPTC and its photo metadata standard", "claims": [ "F33", "F35", "F39", "F40", "F41" ], "earliest": "B5" }, { "lineage": "findings: credit and the scored fields (October 2026)", "claims": [ "F9", "F10", "PE-09", "F2", "F22", "F24", "F29" ], "earliest": "B1" }, { "lineage": "where the stripping happens: the publishing pipeline", "claims": [ "F31", "F11", "F18", "PE-19" ], "earliest": "B1" }, { "lineage": "the archive's own artifacts: the fields embedded, the membrane against stripping", "claims": [ "R1409-01", "O1409-02", "O1409-04", "R1409-05", "R1432-01", "R204-01" ], "earliest": 204 }, { "lineage": "AI: crawler blocking, the data-mining field, Content Credentials, the AI fields", "claims": [ "F15", "F16", "F17", "F30", "F36" ], "earliest": "B6" }, { "lineage": "adoption: uneven, under-adopted", "claims": [ "O725-02", "O725-06", "O499-01" ], "earliest": 499 }, { "lineage": "trust anchors: the device's testimony and content derivation", "claims": [ "O1443-01", "O1443-02", "O1409-07", "O1444-01" ], "earliest": 1409 }, { "lineage": "stated limits: access blocked, the crawler's blind spots", "claims": [ "F14", "PE-18", "F25", "CAP-1-08" ], "earliest": "B1" }, { "lineage": "the record's method and its limits", "claims": [ "PE-16", "CAP-1-03", "PE-20", "PE-21", "PE-22" ], "earliest": "PE" }, { "lineage": "reception: the composition layer at the address", "claims": [ "CAP-1-04", "CAP-1-09", "CAP-1-10", "CAP-1-11", "CAP-1-13", "CAP-1-12" ], "earliest": "capture:iptc-metawatch-aio-20261029" }, { "lineage": "reception: the encyclopedia", "claims": [ "F37", "F38" ], "earliest": "B7" } ], "body_words": 337, "entity": "Composed under v0.9, equal case (ρ = extends): KO_B sentences surviving 0 of 12; every field claim carried." }, "P_B": { "title": "IPTC Metawatch", "arm": "B (the field alone)", "genre": "popup — the compression from the field ledger alone (cards, own pages, Wikipedia)", "status": "composed 2026-10-29 from the field ledger alone; not frozen", "lede": { "text": "is the IPTC's free, open monitor that checks every month whether more than 500 news publishers in 122 countries keep the credits, captions and rights information embedded in their photographs.", "claims": [ "F1", "F21" ] }, "sections": [ { "icon": "🗂️", "head": "What it is", "items": [ { "label": "Method:", "text": "508 publishers, up to 20 articles each, the lead photograph; the 4 Cs scored (IPTC).", "claims": [ "F5", "F6", "F28" ] }, { "label": "Open:", "text": "CC BY 4.0, monthly on the 1st (IPTC; overview).", "claims": [ "F7", "F19", "F26" ] }, { "label": "Lineage:", "text": "IMATAG 2018; the IPTC crawler of 2019 (IPTC).", "claims": [ "F8" ] } ] }, { "icon": "📅", "head": "When", "items": [ { "label": "Dates:", "text": "runs from 2026-06-03; shown at the conference (8 September post); announced 5 October 2026.", "claims": [ "F23", "F32", "F34", "F27", "F20", "F35", "F12" ] } ] }, { "icon": "📉", "head": "What it found", "items": [ { "label": "Credit:", "text": "7.2% of images (8% in 2018); 321 of 425 publishers keep no scored field; copyright 5.6% or 5.3%.", "claims": [ "F9", "F10", "F22", "F24", "F29", "F31", "F2" ] }, { "label": "Pipeline:", "text": "loss with or without a CDN; the fix a setting (IPTC); publishers and CDNs (per-field page).", "claims": [ "F3", "F4", "F11", "F18" ] }, { "label": "AI:", "text": "46% block an AI crawler; C2PA on 27 of 6,580 images; AI fields nearly empty.", "claims": [ "F15", "F16", "F17", "F30", "F36", "F33" ] }, { "label": "Movement:", "text": "60 to 67 of 294 publishers keep metadata; France first.", "claims": [ "F12", "F13" ] } ] }, { "icon": "⚠️", "head": "Limits", "items": [ { "label": "Access and blind spots:", "text": "AP and USA Today blocked it; no_images not zero.", "claims": [ "F14", "F25" ] }, { "label": "Encyclopedia:", "text": "no Wikipedia article; the IPTC's article omits it.", "claims": [ "F37", "F38", "F39", "F40", "F41" ] } ] } ], "open": [ { "question": "Copyright 5.6% or 5.3%?", "rests_on": [ "F10", "F29" ], "modality": "documented, both", "would_resolve": "the October run data" }, { "question": "Pipeline, or publishers and CDNs?", "rests_on": [ "F11", "F31" ], "modality": "interpretation, both", "would_resolve": "the run data by CDN" }, { "question": "Opacity: Paul Melcher's LinkedIn post (snippet only).", "rests_on": [ "F27" ], "modality": "attributed", "would_resolve": "the post's text" } ], "rail": [ { "lineage": "what it is: a free, open monthly monitor of whether news publishers keep embedded photo metadata", "claims": [ "F1", "F21" ], "earliest": "B1" }, { "lineage": "open data, cadence and the operator", "claims": [ "F26", "F7", "F19" ], "earliest": "B1" }, { "lineage": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "claims": [ "F5", "F6", "F28" ], "earliest": "B1" }, { "lineage": "the transformation tested: credit lost between camera and reader", "claims": [ "F3", "F4" ], "earliest": "B1" }, { "lineage": "findings: credit and the scored fields (October 2026)", "claims": [ "F2", "F9", "F10", "F22", "F24", "F29" ], "earliest": "B1" }, { "lineage": "predecessors: IMATAG 2018 and the IPTC prototype crawler of 2019", "claims": [ "F8" ], "earliest": "B1" }, { "lineage": "dates: runs from June, a September showing, the October announcement", "claims": [ "F23", "F34", "F32", "F27", "F20" ], "earliest": "B5" }, { "lineage": "the operator: the IPTC and its photo metadata standard", "claims": [ "F35", "F33", "F39", "F40", "F41" ], "earliest": "B5" }, { "lineage": "where the stripping happens: the publishing pipeline", "claims": [ "F31", "F11", "F18" ], "earliest": "B1" }, { "lineage": "movement: publishers and countries", "claims": [ "F12", "F13" ], "earliest": "B1" }, { "lineage": "AI: crawler blocking, the data-mining field, Content Credentials, the AI fields", "claims": [ "F15", "F16", "F17", "F30", "F36" ], "earliest": "B6" }, { "lineage": "stated limits: access blocked, the crawler's blind spots", "claims": [ "F14", "F25" ], "earliest": "B1" }, { "lineage": "reception: the encyclopedia", "claims": [ "F37", "F38" ], "earliest": "B7" } ], "body_words": 171, "entity": "With no archive claim admitted, the entry is the IPTC's monitor at its own pages' resolution: what it checks, what it found, when it was shown." }, "KO_B": { "title": "IPTC Metawatch", "arm": "B (the field alone)", "genre": "knowledge object", "status": "composed 2026-10-29; not frozen", "sentences": [ { "n": 1, "para": 0, "text": "The IPTC describes Metawatch as a free, open monitor that checks every month whether more than 500 news publishers in 122 countries keep the credits, captions and rights information embedded in their photographs (IPTC announcement, 5 October 2026).", "claims": [ "F1" ] }, { "n": 2, "para": 0, "text": "Its overview says Metawatch tracks how often major news publishers preserve embedded photo metadata (Exif, IPTC Photo Metadata in IIM and XMP, and C2PA), crawling a curated list monthly; it is a project of the IPTC, its data licensed CC BY 4.0 (Metawatch overview).", "claims": [ "F21", "F26" ] }, { "n": 3, "para": 0, "text": "Each month the crawler visits 508 publishers in 122 countries, takes up to 20 recent articles from each and reads the lead photograph, checking Exif, IPTC and C2PA and scoring the 4 Cs, creator, caption, copyright and credit line, the per-field page's 'Four Cs' of news photo provenance; the crawler is light, every run is open data, and results appear on the first of the month (IPTC announcement; per-field breakdown).", "claims": [ "F5", "F6", "F28", "F7", "F19" ] }, { "n": 4, "para": 0, "text": "The announcement explains the problem as credits lost between camera and reader through re-encoding, resizing and optimisation, and says embedded metadata is often the only record of an image's origin and terms once it is copied or crawled for AI; its first results show little change since 2018 (IPTC announcement).", "claims": [ "F3", "F4", "F2" ] }, { "n": 5, "para": 0, "text": "It builds on IMATAG's 2018 study and the IPTC's 2019 prototype crawler and differs in measuring monthly (IPTC announcement).", "claims": [ "F8" ] }, { "n": 6, "para": 1, "text": "Its runs run from 2026-06-03 to 2026-10-01 (overview); it was introduced by Brendan Quinn at the 2026 Photo Metadata Conference, reported on 8 September 2026 (IPTC), Paul Melcher's LinkedIn card of 14 September says the IPTC now publishes it, and the announcement is dated 5 October 2026, the newest post under the Photo Metadata tag.", "claims": [ "F23", "F34", "F32", "F27", "F20", "F35" ] }, { "n": 7, "para": 1, "text": "In October 7.2% of editorial images carried a credit or copyright notice (IMATAG 2018: 8%), 321 of 425 crawlable publishers kept no scored field and 11% of 6,580 images carried any IPTC metadata (IPTC announcement; overview), with copyright at 5.6% in the announcement and 5.3% of 6,514 images on the per-field page, and even Creator below one image in ten (per-field breakdown).", "claims": [ "F9", "F10", "F22", "F24", "F29", "F31" ] }, { "n": 8, "para": 1, "text": "The announcement finds that images lose metadata at about the same rate with or without a CDN, so that stripping appears to happen in the publishing pipeline and the fix is usually a setting, while the per-field page says publishers and CDNs discard it (IPTC announcement; per-field breakdown).", "claims": [ "F11", "F18", "F31" ] }, { "n": 9, "para": 1, "text": "USA Today and Les Echos improved, the number of publishers keeping any metadata rose from 60 to 67 of 294, and France led the October country ranking (IPTC announcement).", "claims": [ "F12", "F13" ] }, { "n": 10, "para": 1, "text": "Nearly half of publishers block an AI crawler in robots.txt, but the data-mining field is on 0.6% of images, 27 of 6,580 images carry a C2PA manifest, almost all signed by AI or design tools, and the AI fields the standard added in 2025 are nearly empty (IPTC announcement; per-field breakdown; Photo Metadata archive); the IPTC's 2026 conference focused on content provenance and the tracking of its real-world adoption (IPTC).", "claims": [ "F15", "F16", "F17", "F30", "F36", "F33" ] }, { "n": 11, "para": 1, "text": "Its stated limits are publishers blocking automated access, as AP and USA Today did in October, and publishers returning no photograph, listed as no_images (IPTC announcement; overview).", "claims": [ "F14", "F25" ] }, { "n": 12, "para": 1, "text": "Wikipedia has no article on Metawatch; its article on the IPTC, which does not name the monitor, calls it the news media's global standards body and photo metadata its most widely used standard (Wikipedia).", "claims": [ "F37", "F38", "F39", "F40", "F41" ] } ] }, "L_B": { "words": 556, "text": "The IPTC describes Metawatch as a free, open monitor that checks every month whether more than 500 news publishers in 122 countries keep the credits, captions and rights information embedded in their photographs (IPTC announcement, 5 October 2026). Its overview says Metawatch tracks how often major news publishers preserve embedded photo metadata (Exif, IPTC Photo Metadata in IIM and XMP, and C2PA), crawling a curated list monthly; it is a project of the IPTC, its data licensed CC BY 4.0 (Metawatch overview). Each month the crawler visits 508 publishers in 122 countries, takes up to 20 recent articles from each and reads the lead photograph, checking Exif, IPTC and C2PA and scoring the 4 Cs, creator, caption, copyright and credit line, the per-field page's 'Four Cs' of news photo provenance; the crawler is light, every run is open data, and results appear on the first of the month (IPTC announcement; per-field breakdown). The announcement explains the problem as credits lost between camera and reader through re-encoding, resizing and optimisation, and says embedded metadata is often the only record of an image's origin and terms once it is copied or crawled for AI; its first results show little change since 2018 (IPTC announcement). It builds on IMATAG's 2018 study and the IPTC's 2019 prototype crawler and differs in measuring monthly (IPTC announcement). Its runs run from 2026-06-03 to 2026-10-01 (overview); it was introduced by Brendan Quinn at the 2026 Photo Metadata Conference, reported on 8 September 2026 (IPTC), Paul Melcher's LinkedIn card of 14 September says the IPTC now publishes it, and the announcement is dated 5 October 2026, the newest post under the Photo Metadata tag. In October 7.2% of editorial images carried a credit or copyright notice (IMATAG 2018: 8%), 321 of 425 crawlable publishers kept no scored field and 11% of 6,580 images carried any IPTC metadata (IPTC announcement; overview), with copyright at 5.6% in the announcement and 5.3% of 6,514 images on the per-field page, and even Creator below one image in ten (per-field breakdown). The announcement finds that images lose metadata at about the same rate with or without a CDN, so that stripping appears to happen in the publishing pipeline and the fix is usually a setting, while the per-field page says publishers and CDNs discard it (IPTC announcement; per-field breakdown). USA Today and Les Echos improved, the number of publishers keeping any metadata rose from 60 to 67 of 294, and France led the October country ranking (IPTC announcement). Nearly half of publishers block an AI crawler in robots.txt, but the data-mining field is on 0.6% of images, 27 of 6,580 images carry a C2PA manifest, almost all signed by AI or design tools, and the AI fields the standard added in 2025 are nearly empty (IPTC announcement; per-field breakdown; Photo Metadata archive); the IPTC's 2026 conference focused on content provenance and the tracking of its real-world adoption (IPTC). Its stated limits are publishers blocking automated access, as AP and USA Today did in October, and publishers returning no photograph, listed as no_images (IPTC announcement; overview). Wikipedia has no article on Metawatch; its article on the IPTC, which does not name the monitor, calls it the news media's global standards body and photo metadata its most widely used standard (Wikipedia).", "note": "L_F(B) is realized as the field arm's expansion (objects.KO_B): the field alone, cards, the own page carried as card 1, and Wikipedia." }, "L_BA": { "words": 2278, "text": "IPTC Metawatch is the International Press Telecommunications Council's free, open monitor of whether news publishers keep the credits, captions and rights information embedded in their photographs, checked every month across more than 500 publishers in 122 countries (IPTC announcement, 5 October 2026); the provenance census record types it as a monitor of the media lineage whose capability is to test, its provenance object 'the lead photograph of a news article, as served to the reader', its operator the IPTC at metawatch.iptc.org (provenance census record). Its own overview states the object from the side of the carrier: Metawatch 'tracks how often major news publishers preserve embedded photo metadata' — Exif, IPTC Photo Metadata in its IIM and XMP forms, and C2PA — and scores the photographs a curated list of publishers serves (Metawatch overview), the carrier the census record names as 'embedded metadata (Exif, IPTC IIM and XMP) and C2PA manifests' (provenance census record). Content Credentials stand in the first of the dimensions of provenance the archive's provenance packet distinguishes: frameworks for the artifact (C2PA / Content Credentials) and for the corpus 'are not designed to address the survival of authorial lineage through AI synthesis', artifact provenance verifying that 'this file' was created by 'this source' at 'this time', at the moment of creation (#725); the same packet places IPTC AI metadata at 'Layer 1 metadata', 'Disclosure, not lineage' (#725). On the first of each month its crawler visits 508 news publishers in 122 countries, takes up to 20 recent articles from each and reads the lead photograph of every article, checking Exif, IPTC Photo Metadata and C2PA Content Credentials and scoring creator, caption, copyright and credit line, 'the “4 Cs”' (IPTC announcement); the census record's unit is 'a news publisher, sampled each month through up to 20 recent articles', its count 508 publishers in 122 countries as of October 2026, monthly on the first, its relation types creator, credit, copyright, caption, the PLUS data-mining preference and Content Credentials (provenance census record); the per-field page calls the four scored fields 'the \"Four Cs\" of news photo provenance', the others tracked for context (Metawatch per-field breakdown). The crawler is 'deliberately light', about 40 to 60 requests per publisher a month, honouring robots.txt and keeping no article text or image files, and every run is published as open data under CC BY 4.0, new results appearing on the first of every month (IPTC announcement); the overview names it 'A project of the International Press Telecommunications Council', its data CC BY 4.0, with an opt-out for publishers by email (Metawatch overview), and the census record carries 'every run published as open data' under 'CC BY 4.0 (each run's data)' (provenance census record). What it tests is a transformation: credits 'are lost between camera and reader' as content management systems re-encode images, delivery networks resize them and optimisation tools discard what looks like unnecessary bytes, and once an image is copied or collected by an AI crawler its embedded metadata 'is often the only record of where it came from and on what terms it may be used' (IPTC announcement); the census record names the transformation tested 'publication through a news site's pipeline (CMS, CDN, image optimisation)' (provenance census record). The archive's packet states the loss one layer on: 'A C2PA-signed image whose caption is rewritten by a model that strips the photographer's name has lost semantic provenance even though artifact provenance is preserved', the dimensions being independent, so that 'Solving any one dimension does not solve the others' (#725). Metawatch builds on IMATAG's 2018 State of Image Metadata study and the IPTC's own prototype crawler of 2019, and differs in measuring every month (IPTC announcement; the census record quotes the sentence as its lineage evidence, provenance census record), and the census record relates it as part of the IPTC's photo-metadata tests, beside the census's C2PA conformance entry, while keeping it apart from the earlier test: 'NOT the 2019 IPTC social-media test: it measures news publishers monthly' (provenance census record). Its overview dates five runs, the first on 2026-06-03 and then monthly to 2026-10-01 (Metawatch overview), and the announcement counts 294 publishers 'measured every month since June' (IPTC announcement). The IPTC's post of 8 September 2026 reports that at the 2026 Photo Metadata Conference, held 'Last Thursday', Brendan Quinn 'appeared again to introduce Metawatch', 'IPTC’s new public service that monitors real-world usage of metadata in images across the global news industry, tracking IPTC/XMP, C2PA, AI opt-outs and more' (IPTC, 8 September 2026); Paul Melcher's LinkedIn post of 14 September 2026, read by its card alone, says the IPTC 'now publishes Metawatch' (LinkedIn card); the conference took as its focus AI transparency and content provenance, 'tracking real-world adoption of content transparency technologies by AI engines, news sites, software and services' (IPTC, 8 September 2026). The announcement is dated 5 October 2026 and is the newest post under the IPTC's Photo Metadata tag (IPTC announcement; Photo Metadata archive); the census record's lifecycle is active, 'announced 5 October 2026', its founding given the same way, the run reported for October 2026 and the record read on 2026-10-29 (provenance census record). The Capture Registry records the difference: the record 'dates the monitor by its announcement, 5 October 2026', two cards date it earlier, the IPTC post of 8 September and Melcher's post of 14 September, and the September showing is carried at the capture 'unchecked against the posts themselves' (Capture Registry, 2026-10-29). In the October run 7.2% of editorial images carried a credit or copyright notice, against IMATAG's 8% in 2018, so that keeping the photographer's credit attached 'has not improved'; 321 of the 425 publishers it could crawl kept none of the scored IPTC fields; 11% of 6,580 images carried any IPTC metadata, the photographer's name on 7.9%, the credit line on 5.7%, copyright on 5.6% (IPTC announcement); the census record's retention results carry the 7.2% and the 321 of 425 with the 27 of 6,580 images bearing a C2PA manifest (provenance census record), and the announcement reads its first results as showing 'how little has changed since 2018' and why metadata 'matters more than ever now that AI companies are crawling the web' (IPTC announcement). The overview gives the latest run as 2026-10-01, 425 sites, 122 countries and 6,580 images, a mean IPTC score of 5.96, 11% with any IPTC and 0.5% with C2PA, and says that 'Any average describes almost nobody here' (Metawatch overview); the per-field page counts over 6,514 images, Creator at 7.9%, CreditLine 5.7%, Copyright 5.3%, CaptionDescription 5%, the licensing fields below 3% (Metawatch per-field breakdown), so that copyright stands at 5.6% in the announcement and at 5.3% on the per-field page. On where the loss happens the operator's pages differ in emphasis: the announcement finds 'It isn’t the CDN’s fault', images through Cloudflare, Akamai, CloudFront and Fastly losing their metadata 87% to 95% of the time and images with no CDN 87%, so that 'Stripping appears to happen in the publishing pipeline', the fix 'usually a setting, not a project' (IPTC announcement; the census record quotes the pipeline sentence as its evidence, provenance census record), while the per-field page reads its dataset as 'publishers and CDNs are discarding metadata that the photographers and agencies almost certainly embedded upstream' (Metawatch per-field breakdown). The archive's specification for machine-eligible handwritten artifacts embeds IPTC Creator (the author or heteronym), Credit, CopyrightNotice, Headline, Description and DateCreated in every published derivative, with an XMP mirror and C2PA manifests wrapping the IPTC/EXIF assertions (#1409); it records embedded IPTC photo metadata as extracted by Google and travelling with the image, its composition role unknown, 'scaffold the pipeline provably reads' (#1409); and it carries the same fields in a visible membrane because 'physically embodied metadata survives screenshot, rehosting, filename change, metadata stripping, PDF embedding, and sidecar loss', under a triple redundancy of pixels, embedded IPTC/XMP/C2PA and external records (#1409). The archive's identifier stamp for a lossless image sits in its EXIF ImageDescription or UserComment (#1432), and its self-audit protocol plans a 'Hash/signature manifest (C2PA-compatible) binding provenance claims to deposited objects' (#204). Some publishers moved: USA Today from no credit metadata in 2019 to 95% of its lead photographs carrying credit, creator and copyright in September, Les Echos from 6% to 75%, and across the 294 publishers measured monthly since June those keeping any metadata rose from 60 to 67; France led October at 19.8 of 100, ahead of Germany at 19.2, with only countries of more than three scored publishers ranked (IPTC announcement). Of 505 publishers whose policies were checked, 234 block at least one AI crawler in robots.txt, but 'robots.txt protects a website, not a photograph', and the PLUS Data Mining field appears on 0.6% of images (IPTC announcement); the archive's training-layer protocol holds that robots.txt and C2PA, which it does not call useless, operate 'primarily at the publication / legal / evidentiary layer rather than at the training-survival layer' (#127). Leaving out the IPTC's own site, 27 of 6,580 images carried a C2PA manifest, all but one signed by an AI or design tool and none 'from a camera or a newsroom’s own signing', and seven carried a Digital Source Type disclosing generative-AI editing, so that, in the announcement's reading, provenance in news photography 'is arriving first through the tools that make synthetic images' (IPTC announcement); the per-field page finds DigitalSourceType on 0.2% of images and the AI prompt and AI system fields on none (Metawatch per-field breakdown), properties the IPTC Photo Metadata Standard added for AI-generated content on 27 November 2025 (Photo Metadata archive). The archive's packet calls the adoption of artifact authenticity 'uneven' and C2PA's ingredient assertions 'optional, under-adopted' (#725), and its field manual holds that C2PA standards and watermarking have not 'achieved sufficient adoption to function as infrastructure' (#499). The archive reads C2PA's trust as a device's: C2PA 'attests what a device reports having done' where a content-derived identifier 'computes what the bytes are', validation optional in the first, the two complementary (#1443), C2PA anchoring in device and issuer certificates and the AXN regime in content derivation and a public ledger (#1409), C2PA securing 'the camera's testimony, not the author's' (#1444). It declares a nonsynthetic capture by the IPTC DigitalSourceType inside the file, 'in the same controlled vocabulary whose trainedAlgorithmicMedia value marks the synthetic class', and holds that 'C2PA, FADGI, and IPTC provenance vocabularies are the same insight arriving as standards' (#1409). The monitor states its limits: the United States slipped from first to fourth in October because AP and USA Today 'began blocking automated access this month', 'a reminder that bot-blocking aimed at AI also shuts out research' (IPTC announcement; quoted in the census record's evidence, provenance census record), and publishers reached without a photograph are listed as no_images rather than scored zero, 'usually our blind spot rather than their practice' (Metawatch overview); the census record leaves unchecked 'the Metawatch site itself and its published run data' and IMATAG's 2018 study, and marks the monitor 'NOT a C2PA verifier' (provenance census record). The archive holds the artifact dimension necessary and insufficient: C2PA 'prevents forgery; it does not constitute authorship' (#729), 'C2PA authenticates media' and does not cover text (#621), and 'When a 5,000-word article becomes a 200-word AI Overview, C2PA cannot tell you what was lost' (#615). It finds that metadata standards, C2PA among them, do not address the measurable reception consequences of provenance and attribution (#833), that provenance and attribution studies, C2PA among them, 'have focused on attribution loss in AI outputs' (#1003), and that cross-format content provenance standards give 'starting points for the public and machine-readable layers' (#95). On Google's AI Overview, signed out, on 2026-10-29, the Capture Registry finds the method and scale right ('Every month', 'more than 500 news publishers in 122 countries' and the fields are the announcement's own) and 'Free and open' matched to the census record's licence quote, checked against that record and the pages it saved (Capture Registry, 2026-10-29). It finds the findings absent, 'The composition gives what the monitor checks and none of what it found', and the access limit not composed; it reads the Overview first as naming 'the maker, the method and the scale of a monitor three weeks old', then as composing 'A new provenance monitor' 'at the grain of its feature list', when what it measures is 'the erasure of credit in the publishing pipeline', carrying 'the instrument' and leaving out 'its reading', the IPTC photo metadata capture's pattern 'in small: the carrier composed, the loss omitted' (Capture Registry, 2026-10-29). At the capture the IPTC is named, Paul Melcher and Brendan Quinn appear only in cards, no identifier is given and the monitor's own pages are cited, and no card cites the census record, which landed on provenanceerasure.org the same day (Capture Registry, 2026-10-29). The census record asks of each entity 'What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?', each quote verbatim from a saved source, and for Metawatch read one source, the announcement, on 2026-10-29 (provenance census record); Wikipedia has no article on IPTC Metawatch and no article text naming it beside the IPTC, and its article on the operator, which does not name Metawatch, describes the IPTC as 'a consortium of the world's major news agencies, other news providers and news industry vendors' acting as 'the global standards body of the news media', whose photo metadata, the IIM set that XMP has largely superseded, is 'by far IPTC's most widely used standard' (Wikipedia).", "rail": [], "note": "L(B ∪ A) in the equal-terms case (v0.9 §0.4), realized as the knowledge object (objects.KO); its rail is the compression's, by lineage." } }, "field": [ { "id": "B1", "card": "IPTC — Announcing Metawatch: a monthly check on which news publishers keep ... - IPTC", "fetched": "card; B1.html HTTP 200 sha256 23d67ed30137cda5; also the census's own page (B1-census.html sha256 0a7fea35f38f83bb, = the census record's)", "origin": "card" }, { "id": "B2", "card": "IPTC — Overview — Metawatch - IPTC", "fetched": "card; B2.html HTTP 200 sha256 4a9a9fb3a2a1ae5a", "origin": "card" }, { "id": "B3", "card": "LinkedIn·Paul Melcher — IPTC Publishes Metawatch, Revealing Image Metadata Issues - LinkedIn", "fetched": "unreachable: no URL found by title and site (WebSearch ×5, guessed pulse URL → article_not_found, profile behind sign-in); card title and snippet only", "origin": "card" }, { "id": "B4", "card": "IPTC — Per-field breakdown - Metawatch - IPTC", "fetched": "card; B4.html HTTP 200 sha256 320d791c70043eb1", "origin": "card" }, { "id": "B5", "card": "IPTC — Watching AI platforms, news publishers and real-world C2PA - IPTC", "fetched": "card; B5.html HTTP 200 sha256 a2176a9721211134", "origin": "card" }, { "id": "B6", "card": "IPTC — Photo Metadata Archives - IPTC", "fetched": "card; B6.html HTTP 200 sha256 4afb0a05b1a4f8fe", "origin": "card" }, { "id": "B7", "card": "Wikipedia — IPTC Metawatch / Metawatch (no article)", "fetched": "Wikipedia; raw wikitext HTTP 404, rendered HTTP 404, search no results; B7.wiki sha256 ab5b734ed1436ef2, B7.html sha256 e8dfe552afbe33e9, B7.txt sha256 8d4106a54ed94b08", "origin": "wikipedia" }, { "id": "B8", "card": "Wikipedia — International Press Telecommunications Council", "fetched": "Wikipedia; raw wikitext HTTP 200, rendered HTTP 200; B8.wiki sha256 c9111b64b71f2a9c, B8.html sha256 65a1179436e98711, B8.txt sha256 cb0c0b3b92c37275", "origin": "wikipedia" } ], "field_claims": { "F1": { "source": "B1", "origin": "card", "locus": "announcement, standfirst ¶1", "quote": "The IPTC has launched Metawatch , a free, open monitor that checks every month whether more than 500 news publishers in 122 countries keep the credits, captions and rights information embedded in their photographs.", "claim": "the monitor defined by its operator: free, open, monthly, more than 500 publishers in 122 countries, whether they keep the credits, captions and rights information embedded in their photographs", "modality": "stipulation", "kind": "definition", "kernel": true, "const": true, "lineage": "what it is: a free, open monthly monitor of whether news publishers keep embedded photo metadata", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F2": { "source": "B1", "origin": "card", "locus": "announcement, standfirst ¶2", "quote": "The first results show how little has changed since 2018, which publishers have fixed their sites, and why keeping metadata matters more than ever now that AI companies are crawling the web.", "claim": "the operator's summary of its first results: little changed since 2018; some publishers fixed; metadata matters more now that AI companies crawl the web", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "findings: credit and the scored fields (October 2026)", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F3": { "source": "B1", "origin": "card", "locus": "'Credits are lost between camera and reader' (heading and ¶2)", "quote": "Credits are lost between camera and reader … In practice, most of it is gone by the time a reader sees the picture. Content management systems re-encode images, content delivery networks resize them, and optimisation tools discard anything that looks like unnecessary bytes.", "claim": "the transformation: credits lost between camera and reader as CMSs re-encode, CDNs resize and optimisation tools discard metadata", "modality": "interpretation", "kind": "function", "kernel": true, "const": false, "lineage": "the transformation tested: credit lost between camera and reader", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F4": { "source": "B1", "origin": "card", "locus": "'Credits are lost between camera and reader' ¶3", "quote": "When an image is copied, shared or collected by an AI crawler, the embedded metadata is often the only record of where it came from and on what terms it may be used.", "claim": "why it matters: for a copied, shared or AI-crawled image the embedded metadata is often the only record of origin and terms", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "the transformation tested: credit lost between camera and reader", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F5": { "source": "B1", "origin": "card", "locus": "'What Metawatch does' ¶1 s1–2", "quote": "Metawatch checks every month: does the photo metadata survive publication? On the first of each month our well-behaved crawler visits 508 news publishers in 122 countries, takes up to 20 recent articles from each, and reads the lead photograph of every article.", "claim": "the method: monthly, whether photo metadata survives publication; 508 publishers in 122 countries, up to 20 recent articles each, the lead photograph of each", "modality": "stipulation", "kind": "function", "kernel": true, "const": true, "lineage": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F6": { "source": "B1", "origin": "card", "locus": "'What Metawatch does' ¶1 s3", "quote": "It checks each image for Exif, IPTC Photo Metadata (in both IIM and XMP form) and C2PA Content Credentials, and scores how each site carry the fields that matter most: creator, caption, copyright and credit line (the “4 Cs”).", "claim": "what is checked and scored: Exif, IPTC Photo Metadata (IIM and XMP) and C2PA Content Credentials; the score on creator, caption, copyright and credit line, the 4 Cs", "modality": "stipulation", "kind": "definition", "kernel": false, "const": true, "lineage": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F7": { "source": "B1", "origin": "card", "locus": "'What Metawatch does' ¶2", "quote": "The crawler is deliberately light: about 40 to 60 requests per publisher per month, honouring robots.txt and keeping no article text or image files. How it works is documented in full, and every run is published as open data under CC BY 4.0, so anyone can check our numbers or ask their own questions.", "claim": "a light crawler (40–60 requests per publisher a month, robots.txt honoured, no text or images kept); method documented; every run open data under CC BY 4.0", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "open data, cadence and the operator", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F8": { "source": "B1", "origin": "card", "locus": "'What Metawatch does' ¶3", "quote": "Metawatch builds on IMATAG’s 2018 State of Image Metadata study and IPTC’s own prototype crawler from 2019 , presented at the 2019 Photo Metadata Conference . This service is different in that we now measure every month, so we can compare trends over time.", "claim": "its predecessors: IMATAG's 2018 study and the IPTC's 2019 prototype crawler; it differs in measuring every month", "modality": "documented", "kind": "genealogy", "kernel": false, "const": false, "lineage": "predecessors: IMATAG 2018 and the IPTC prototype crawler of 2019", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F9": { "source": "B1", "origin": "card", "locus": "'What we found' ¶1", "quote": "In 2018 IMATAG found that 8% of editorial images carried a credit or copyright notice. Applying the same test to our October run gives 7.2%. Whatever else has changed in news publishing since then, keeping the photographer’s credit attached to the photograph has not improved.", "claim": "the headline finding: 7.2% of editorial images with a credit or copyright notice in October 2026 against IMATAG's 8% in 2018; no improvement", "modality": "documented", "kind": "fact", "kernel": true, "const": false, "lineage": "findings: credit and the scored fields (October 2026)", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F10": { "source": "B1", "origin": "card", "locus": "'What we found' ¶2", "quote": "In the October run, 321 of the 425 publishers we could crawl, three out of four kept none of the IPTC fields we score on any image we sampled. Only 11% of the 6,580 images carried any IPTC metadata at all . The field that survives most often is the photographer’s name, on just 7.9% of images; the credit line is on 5.7% and copyright on 5.6%.", "claim": "321 of 425 crawlable publishers kept none of the scored fields; 11% of 6,580 images carry any IPTC metadata; creator 7.9%, credit line 5.7%, copyright 5.6%", "modality": "documented", "kind": "fact", "kernel": true, "const": false, "lineage": "findings: credit and the scored fields (October 2026)", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F11": { "source": "B1", "origin": "card", "locus": "'What we found' ¶3", "quote": "It isn’t the CDN’s fault. Images served through Cloudflare, Akamai, CloudFront and Fastly lost their metadata 87% to 95% of the time, but images served with no CDN at all also lost metadata 87% of the time. Stripping appears to happen in the publishing pipeline, which means that publishers can fix it.", "claim": "the loss through four CDNs (87–95%) matches the loss with no CDN (87%); stripping appears to happen in the publishing pipeline, which publishers can fix", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "where the stripping happens: the publishing pipeline", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F12": { "source": "B1", "origin": "card", "locus": "'What we found' ¶4", "quote": "USA Today carried no credit metadata when IMATAG measured it in 2019; in September 95% of its lead photographs carried credit, creator and copyright. Les Echos went from 6% to 75%. … Across the 294 publishers we have measured every month since June, the number keeping any metadata rose from 60 to 67. It is early, but the needle can move.", "claim": "movement: USA Today from none (2019) to 95% (September 2026); Les Echos 6% to 75%; of 294 publishers measured monthly since June, those keeping any metadata rose from 60 to 67", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "movement: publishers and countries", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F13": { "source": "B1", "origin": "card", "locus": "'Which countries do best' ¶1", "quote": "France tops our October ranking, with an average publisher score of 19.8 out of 100, just ahead of Germany at 19.2. Taiwan enters at third. We rank only countries where we scored more than three publishers, so that one well-run newsroom cannot carry a whole country; 34 countries qualified this month.", "claim": "the October country ranking (France 19.8, Germany 19.2, Taiwan third) and its rule (more than three publishers scored; 34 countries)", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "movement: publishers and countries", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F14": { "source": "B1", "origin": "card", "locus": "'Which countries do best' ¶2 (after the chart)", "quote": "The United States led in September and slipped to fourth in October, but only because two of its best-scoring publishers were out of reach: AP and USA Today began blocking automated access this month. It is a reminder that bot-blocking aimed at AI also shuts out research.", "claim": "the stated access limit: AP and USA Today blocked automated access in October, moving the United States from first to fourth; bot-blocking aimed at AI also shuts out research", "modality": "self-description", "kind": "limit", "kernel": true, "const": false, "lineage": "stated limits: access blocked, the crawler's blind spots", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F15": { "source": "B1", "origin": "card", "locus": "'AI: a locked front door, an open back door' ¶1–2", "quote": "Of the 505 publishers whose policies we checked, 234 (46%) block at least one AI crawler in their robots.txt. … But robots.txt protects a website, not a photograph. … IPTC Photo Metadata has a field for exactly this: PLUS Data Mining . Only 15 publishers (3.0%) put it on any image we sampled, and it appears on 0.6% of images overall.", "claim": "234 of 505 publishers (46%) block an AI crawler in robots.txt, which protects a site and not a photograph; the PLUS Data Mining field is used by 15 publishers and appears on 0.6% of images", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "AI: crawler blocking, the data-mining field, Content Credentials, the AI fields", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F16": { "source": "B1", "origin": "card", "locus": "'AI: a locked front door, an open back door' ¶3 s1–2", "quote": "Leaving out IPTC’s own site, 27 of the 6,580 images we analysed carried a C2PA manifest, and all but one were signed by an AI or design tool: OpenAI, Adobe, Canva or Google (the last had a signer we couldn’t read). None came from a camera or a newsroom’s own signing.", "claim": "27 of 6,580 images carry a C2PA manifest, all but one signed by an AI or design tool; none from a camera or a newsroom's own signing", "modality": "documented", "kind": "fact", "kernel": true, "const": false, "lineage": "AI: crawler blocking, the data-mining field, Content Credentials, the AI fields", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F17": { "source": "B1", "origin": "card", "locus": "'AI: a locked front door, an open back door' ¶3 s3–4", "quote": "Seven images carried an IPTC Digital Source Type saying they had been edited with generative AI, which is exactly the kind of disclosure the field was designed for. Provenance in news photography is arriving first through the tools that make synthetic images, not through the photojournalism that most needs it.", "claim": "seven images disclose generative-AI editing by Digital Source Type; provenance in news photography arrives first through the tools that make synthetic images", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "AI: crawler blocking, the data-mining field, Content Credentials, the AI fields", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F18": { "source": "B1", "origin": "card", "locus": "'What publishers can do' ¶1 s1–2", "quote": "The fix is usually a setting, not a project. Most image pipelines strip metadata by default to save a few kilobytes; most can be told to keep it.", "claim": "the fix: a setting; most image pipelines strip metadata by default and can be told to keep it", "modality": "interpretation", "kind": "function", "kernel": false, "const": false, "lineage": "where the stripping happens: the publishing pipeline", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F19": { "source": "B1", "origin": "card", "locus": "closing ¶", "quote": "Metawatch automatically publishes new results on the first of every month.", "claim": "new results published automatically on the first of every month", "modality": "stipulation", "kind": "function", "kernel": false, "const": false, "lineage": "open data, cadence and the operator", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F20": { "source": "B1", "origin": "card", "locus": "dateline and title", "quote": "Oct 5 2026 … Announcing Metawatch: a monthly check on which news publishers keep photo metadata", "claim": "the announcement, dated 5 October 2026", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "dates: runs from June, a September showing, the October announcement", "date": "2026-10-05 (posted)", "quote_ok": true, "checked_against": "saved text B1.txt (sha256 18f7fcf5c0e6a366…), whitespace-normalised" }, "F21": { "source": "B2", "origin": "card", "locus": "overview, opening", "quote": "Metawatch tracks how often major news publishers preserve embedded photo metadata (Exif, IPTC Photo Metadata (in both original IIM format and newer XMP format), and C2PA) on the images they publish. We crawl a curated list of publishers monthly and score the photographs they serve.", "claim": "the monitor's own page: how often major news publishers preserve embedded photo metadata (Exif, IPTC IIM and XMP, C2PA); a curated list crawled monthly, the served photographs scored", "modality": "stipulation", "kind": "definition", "kernel": true, "const": true, "lineage": "what it is: a free, open monthly monitor of whether news publishers keep embedded photo metadata", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B2.txt (sha256 0214693d56a73dc9…), whitespace-normalised" }, "F22": { "source": "B2", "origin": "card", "locus": "overview, run summary", "quote": "Latest run 2026-10-01 Sites crawled 425 Countries 122 Images analysed 6,580 … Mean IPTC score 5.96 … % with any IPTC 11% % with C2PA 0.5%", "claim": "the latest run, 2026-10-01: 425 sites, 122 countries, 6,580 images; mean IPTC score 5.96; 11% with any IPTC, 0.5% with C2PA", "modality": "documented", "kind": "fact", "kernel": true, "const": false, "lineage": "findings: credit and the scored fields (October 2026)", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B2.txt (sha256 0214693d56a73dc9…), whitespace-normalised" }, "F23": { "source": "B2", "origin": "card", "locus": "overview, 'How this run’s top 10 ranked in earlier runs' (chart axis and point titles)", "quote": "How this run’s top 10 ranked in earlier runs … 2026-06-03 2026-07-01 2026-08-01 2026-09-01 2026-10-01 … France: #1 of 26 on 2026-06-03 — score 22.8, 10 publishers", "claim": "five runs on the overview, the first dated 2026-06-03, then monthly to 2026-10-01", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "dates: runs from June, a September showing, the October announcement", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B2.txt (sha256 0214693d56a73dc9…), whitespace-normalised" }, "F24": { "source": "B2", "origin": "card", "locus": "overview, 'How the scores are distributed'", "quote": "Any average describes almost nobody here: a small group embed metadata thoroughly, and 321 of 425 publishers embed none we can find at all.", "claim": "the distribution: a small group embeds metadata thoroughly; 321 of 425 embed none", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "findings: credit and the scored fields (October 2026)", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B2.txt (sha256 0214693d56a73dc9…), whitespace-normalised" }, "F25": { "source": "B2", "origin": "card", "locus": "overview, 'How the scores are distributed', note", "quote": "Publishers we reached but got no photograph from are listed separately as no_images rather than scored zero, since that is usually our blind spot rather than their practice.", "claim": "the stated limit: publishers reached without a photograph are listed as no_images, not scored zero, as the crawler's blind spot", "modality": "self-description", "kind": "limit", "kernel": true, "const": false, "lineage": "stated limits: access blocked, the crawler's blind spots", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B2.txt (sha256 0214693d56a73dc9…), whitespace-normalised" }, "F26": { "source": "B2", "origin": "card", "locus": "footer", "quote": "Metawatch · A project of the International Press Telecommunications Council . Data licensed CC BY 4.0 . … Publishers may opt out by emailing office@iptc.org .", "claim": "a project of the IPTC; data CC BY 4.0; publishers may opt out by email", "modality": "documented", "kind": "attribution", "kernel": false, "const": false, "lineage": "open data, cadence and the operator", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B2.txt (sha256 0214693d56a73dc9…), whitespace-normalised" }, "F27": { "source": "B3", "origin": "card", "locus": "card title and snippet (LinkedIn unreachable)", "quote": "IPTC Publishes Metawatch, Revealing Image Metadata Issues - LinkedIn … Sep 14, 2026 — International Press Telecommunications Council (IPTC) now publishes Metawatch. It crawls news publishers every month and checks what ...", "claim": "Paul Melcher's LinkedIn post (14 September 2026, by its card): the IPTC now publishes Metawatch, crawling news publishers monthly (title and snippet only)", "modality": "attributed", "kind": "fact", "kernel": true, "const": false, "lineage": "dates: runs from June, a September showing, the October announcement", "date": "2026-09-14 (card date; snippet only)", "quote_ok": true, "checked_against": "the card's title/snippet in the registry's cite_list" }, "F28": { "source": "B4", "origin": "card", "locus": "per-field page, ¶2", "quote": "The \"scored\" badge marks the four fields that contribute to a site's overall score (the \"Four Cs\" of news photo provenance); the others are tracked for context but don't affect the score", "claim": "the score: four fields scored, the 'Four Cs' of news photo provenance; others tracked for context", "modality": "stipulation", "kind": "definition", "kernel": true, "const": false, "lineage": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B4.txt (sha256 7776927a7a2be141…), whitespace-normalised" }, "F29": { "source": "B4", "origin": "card", "locus": "per-field page, table rows (Field, Type, Present, Total, Population, Score weight)", "quote": "Creator scored 517 6,514 7.9% 25% … CreditLine scored 373 6,514 5.7% 25% … Copyright scored 348 6,514 5.3% 25% … CaptionDescription scored 324 6,514 5% 25%", "claim": "the four scored fields over 6,514 images: Creator 7.9%, CreditLine 5.7%, Copyright 5.3%, CaptionDescription 5%", "modality": "documented", "kind": "fact", "kernel": true, "const": false, "lineage": "findings: credit and the scored fields (October 2026)", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B4.txt (sha256 7776927a7a2be141…), whitespace-normalised" }, "F30": { "source": "B4", "origin": "card", "locus": "per-field page, table rows (AI fields)", "quote": "DigitalSourceType tracked 15 6,514 0.2% … AIPromptInformation tracked 0 6,514 0% … AISystemUsed tracked 0 6,514 0%", "claim": "the AI-related fields: DigitalSourceType on 0.2% (15 images); AIPromptInformation and AISystemUsed on none", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "AI: crawler blocking, the data-mining field, Content Credentials, the AI fields", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B4.txt (sha256 7776927a7a2be141…), whitespace-normalised" }, "F31": { "source": "B4", "origin": "card", "locus": "per-field page, 'What this tells us'", "quote": "Even the best-populated field — Creator at 7.9% — appears on fewer than one in ten images we fetched. The fields most relevant to licensing ( WebStatement , LicensorURL ) are below 3%. The dataset as a whole tells a consistent story: publishers and CDNs are discarding metadata that the photographers and agencies almost certainly embedded upstream.", "claim": "the reading of the dataset: even Creator is on fewer than one in ten images; licensing fields below 3%; publishers and CDNs discard metadata embedded upstream", "modality": "interpretation", "kind": "interpretation", "kernel": false, "const": false, "lineage": "where the stripping happens: the publishing pipeline", "date": "2026-10-29 (page undated; as fetched; latest run 2026-10-01)", "quote_ok": true, "checked_against": "saved text B4.txt (sha256 7776927a7a2be141…), whitespace-normalised" }, "F32": { "source": "B5", "origin": "card", "locus": "dateline and ¶1 s1", "quote": "Sep 8 2026 … Last Thursday, the photo metadata industry came together for the 2026 IPTC Photo Metadata Conference.", "claim": "the IPTC's post of 8 September 2026 dates the 2026 Photo Metadata Conference 'Last Thursday'", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "dates: runs from June, a September showing, the October announcement", "date": "2026-09-08 (posted)", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 c5bb8d7509c13bac…), whitespace-normalised" }, "F33": { "source": "B5", "origin": "card", "locus": "¶1 s3", "quote": "This year we focussed on the industry’s implementation of recent legislation around AI transparency and content provenance, tracking real-world adoption of content transparency technologies by AI engines, news sites, software and services.", "claim": "the conference's focus: AI transparency and content provenance, the real-world adoption of content transparency technologies by AI engines, news sites, software and services", "modality": "self-description", "kind": "fact", "kernel": false, "const": false, "lineage": "the operator: the IPTC and its photo metadata standard", "date": "2026-09-08 (posted)", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 c5bb8d7509c13bac…), whitespace-normalised" }, "F34": { "source": "B5", "origin": "card", "locus": "last ¶ before the videos", "quote": "Lastly, Brendan Quinn appeared again to introduce Metawatch , IPTC’s new public service that monitors real-world usage of metadata in images across the global news industry, tracking IPTC/XMP, C2PA, AI opt-outs and more.", "claim": "Brendan Quinn introduced Metawatch at the conference: the IPTC's new public service monitoring real-world usage of metadata in images across the news industry (IPTC/XMP, C2PA, AI opt-outs)", "modality": "documented", "kind": "genealogy", "kernel": true, "const": false, "lineage": "dates: runs from June, a September showing, the October announcement", "date": "2026-09-08 (posted)", "quote_ok": true, "checked_against": "saved text B5.txt (sha256 c5bb8d7509c13bac…), whitespace-normalised" }, "F35": { "source": "B6", "origin": "card", "locus": "tag archive, title and newest post", "quote": "Photo Metadata Archives - IPTC … Oct 5 2026 … Announcing Metawatch: a monthly check on which news publishers keep photo metadata", "claim": "the announcement is the newest post under the IPTC's Photo Metadata tag", "modality": "documented", "kind": "fact", "kernel": true, "const": false, "lineage": "the operator: the IPTC and its photo metadata standard", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 b1633287a8889a7e…), whitespace-normalised" }, "F36": { "source": "B6", "origin": "card", "locus": "tag archive, post of 27 November 2025", "quote": "Nov 27 2025 … IPTC Photo Metadata Standard adds new properties for AI-generated content", "claim": "the IPTC Photo Metadata Standard added properties for AI-generated content (2025.1, 27 November 2025)", "modality": "documented", "kind": "genealogy", "kernel": false, "const": false, "lineage": "AI: crawler blocking, the data-mining field, Content Credentials, the AI fields", "date": "2025-11-27 (as listed)", "quote_ok": true, "checked_against": "saved text B6.txt (sha256 b1633287a8889a7e…), whitespace-normalised" }, "F37": { "source": "B7", "origin": "wikipedia", "locus": "Wikipedia: titles IPTC_Metawatch and Metawatch; full-text search", "quote": "raw wikitext IPTC_Metawatch (action=raw, redirect=no): HTTP 404 … Wikipedia does not have an article with this exact name. … full-text search for \"Metawatch\" IPTC (namespace 0): There were no results matching the query.", "claim": "Wikipedia has no article on the monitor and no article text naming it beside the IPTC", "modality": "documented", "kind": "fact", "kernel": true, "const": false, "lineage": "reception: the encyclopedia", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 8d4106a54ed94b08…), whitespace-normalised" }, "F38": { "source": "B7", "origin": "wikipedia", "locus": "Wikipedia: the operator's article, searched for the name", "quote": "operator's article International_Press_Telecommunications_Council (raw wikitext action=raw, HTTP 200; rendered page HTTP 200, saved as B8): the string Metawatch does not occur in either.", "claim": "the operator's Wikipedia article does not name Metawatch", "modality": "documented", "kind": "fact", "kernel": false, "const": false, "lineage": "reception: the encyclopedia", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B7.txt (sha256 8d4106a54ed94b08…), whitespace-normalised" }, "F39": { "source": "B8", "origin": "wikipedia", "locus": "lead ¶1", "quote": "The International Press Telecommunications Council ( IPTC ), based in London , United Kingdom , is a consortium of the world's major news agencies , other news providers and news industry vendors and acts as the global standards body of the news media.", "claim": "the operator: a London-based consortium of news agencies, providers and vendors, the global standards body of the news media", "modality": "documented", "kind": "definition", "kernel": true, "const": false, "lineage": "the operator: the IPTC and its photo metadata standard", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B8.txt (sha256 cb0c0b3b92c37275…), whitespace-normalised" }, "F40": { "source": "B8", "origin": "wikipedia", "locus": "'Photo metadata' ¶1–2", "quote": "The IPTC defined a set of metadata properties that can be applied to images, part of a broader standard developed in the early 1990s and known as the IPTC Information Interchange Model (IIM). … The Extensible Metadata Platform (XMP) has largely superseded IIM's image file header structure", "claim": "the operator's photo metadata: the IIM set of the early 1990s, its file-header structure largely superseded by XMP", "modality": "documented", "kind": "genealogy", "kernel": false, "const": false, "lineage": "the operator: the IPTC and its photo metadata standard", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B8.txt (sha256 cb0c0b3b92c37275…), whitespace-normalised" }, "F41": { "source": "B8", "origin": "wikipedia", "locus": "'Photo metadata' ¶3", "quote": "Because of its nearly universal acceptance among photographers — even amateurs — this is by far IPTC's most widely used standard.", "claim": "the encyclopedia's account: photo metadata, nearly universally accepted among photographers, is the IPTC's most widely used standard", "modality": "interpretation", "kind": "interpretation", "kernel": true, "const": false, "lineage": "the operator: the IPTC and its photo metadata standard", "date": "2026-10-29 (as fetched)", "quote_ok": true, "checked_against": "saved text B8.txt (sha256 cb0c0b3b92c37275…), whitespace-normalised" } }, "field_sources": { "B1": "IPTC — Announcing Metawatch: a monthly check on which news publishers keep ... - IPTC", "B2": "IPTC — Overview — Metawatch - IPTC", "B3": "LinkedIn·Paul Melcher — IPTC Publishes Metawatch, Revealing Image Metadata Issues - LinkedIn", "B4": "IPTC — Per-field breakdown - Metawatch - IPTC", "B5": "IPTC — Watching AI platforms, news publishers and real-world C2PA - IPTC", "B6": "IPTC — Photo Metadata Archives - IPTC", "B7": "Wikipedia — IPTC Metawatch / Metawatch (no article)", "B8": "Wikipedia — International Press Telecommunications Council" }, "delta": { "T_vs_LB": "At 'IPTC Metawatch' (T1, six cards: B1–B6; 123 words) the composition gives the monitor at the grain of its feature list. Composed from its cards: the definition, 'a free and open public monitoring tool that tracks how news publishers handle photo metadata' (T1-1), at the grain of the announcement's 'free, open monitor' (B1 F1) and the overview's 'tracks how often major news publishers preserve embedded photo metadata' (B2 F21), the operator named; the monthly check, 'to see if embedded metadata survives publication' (T1-2), the announcement's 'does the photo metadata survive publication?' (B1 F5); the scale, 'over 500 news publishers across 122 countries' (T1-3), the announcement's opening (F1); the fields, 'credits, captions, copyright notices, Exif data, and IPTC/XMP photo metadata' (T1-4), from F1's credits and captions, F9's 'credit or copyright notice' and F6's Exif and IPTC; 'free and open' at the coarse grain of F7's open data under CC BY 4.0; the per-field breakdown by its existence (T1-5; B4, F28–F29), none of its figures. Available, not composed: every finding (B1 F9, F10: 7.2% against IMATAG's 8%, 321 of 425 publishers keeping no scored field, 11% of images with any IPTC; B2 F22, F24; B4 F29–F31; the C2PA finding F16 and its reading F17; the AI-crawler and data-mining figures F15; movement F12, F13), the transformation and why it matters (F3, F4), where the stripping happens (F11, F18, F31), the predecessors (F8), the open-data terms and cadence (F7 in part, F19, F26), every date (B5 F32, F34, B3 F27, B1 F20, B2 F23) and the operator's other pages' context (B5 F33, B6 F35, F36). Limit dropped: the access limit (B1 F14: AP and USA Today blocking automated access; 'bot-blocking aimed at AI also shuts out research') and the blind spot (B2 F25: no_images, not zero); and T1-3's 'Monitors over 500' gives the publishers visited (F5: 508) without the stated limit that 425 could be crawled (F10 'the 425 publishers we could crawl'; F22 'Sites crawled 425'). Substituted reading at the carrier: T1-4's list of what is checked drops C2PA Content Credentials, which both the announcement (F6) and the overview (F21) name among the three carriers checked, and gives 'preserved or stripped' without the finding that most is stripped. Force: none raised. Composed without attribution: none at the source's resolution beyond the IPTC's own feature list, attributed to the IPTC by the sentence's subject; Paul Melcher (B3) and Brendan Quinn (B5) are not named in the body. Assigned to another: none. Content replaced by use: T1-6, an offer to explain how to check a publisher's score or embed IPTC metadata (N_ext). The Capture Registry names the same omissions at its own grain: 'The composition gives what the monitor checks and none of what it found' (CAP-1-04); the access limit 'is not composed' (CAP-1-08); 'the composition carries the instrument and leaves out its reading' (CAP-1-10).", "T_vs_LB_reading": "v0.9 §0.5: the first diff is ontological. T and the field agree on the entity (the IPTC's monthly monitor of photo-metadata survival), and T composes the instrument as a list of features: its object, cadence, scale and fields. What the field holds as the instrument's reason for being, its measurements of loss and its stated limits, is not composed; the carrier list is cut to Exif and IPTC/XMP. Of the 36 claims on the six cards, T composes 8, at or coarser than the cards' grain.", "LB_vs_LBA": "Admission adds, in one claim space with the field's: the place of the monitor's carriers in the archive's dimensions of provenance (C2PA / Content Credentials and IPTC AI metadata as the artifact layer, 'Disclosure, not lineage': O725-01, O725-03, O725-07, O729-01); the next layer of the same loss (the signed image whose caption loses the photographer's name: O725-05, O725-04; what C2PA cannot tell at a summary: O615-01, O621-01, O729-02, O833-01, O1003-01); the archive's statements of adoption (O725-02, O725-06, O499-01) beside the monitor's 27 manifests in 6,580; the trust anchors (the device's testimony against content derivation: O1443-01, O1443-02, O1409-07, O1444-01); the archive's own practice with the same fields and its design against their stripping (R1409-01, O1409-02, R1409-03, O1409-04, R1409-05, O1409-06, R1432-01, R204-01, O127-01, O95-01); the census record's typing, object, carrier, unit, transformation and dating of the entity (PE-01–PE-22), with its own limits (PE-16); and the Capture Registry's observation of the composition at the address (CAP-1-01–CAP-1-13), including the dating question it carries (CAP-1-05–07). Nothing in the field is contradicted by an archive claim; one field-internal divergence (copyright 5.6% or 5.3%) and one difference of emphasis between the operator's pages (pipeline, or publishers and CDNs) are carried from the field. The census record's founding date ('announced 5 October 2026') is qualified by the field's earlier dates (runs from 2026-06-03, the conference showing reported on 8 September 2026), which the capture names (CAP-1-06).", "alignment": { "T1_cards_claims": [ "F1", "F2", "F3", "F4", "F5", "F6", "F7", "F8", "F9", "F10", "F11", "F12", "F13", "F14", "F15", "F16", "F17", "F18", "F19", "F20", "F21", "F22", "F23", "F24", "F25", "F26", "F27", "F28", "F29", "F30", "F31", "F32", "F33", "F34", "F35", "F36" ], "T1_composed": [ "F1", "F21", "F5", "F6", "F7", "F28", "F29", "F9" ], "T1_outside_cards": [], "rule": "a field claim counts as composed when T states it at its source's grain or coarser; F6 and F7 are composed in part (F6 without C2PA; F7 as 'free and open'); the typology of what is not is in T_vs_LB (§6.2)" } }, "kernel": [ { "K": "K1", "claim": "`CAP-1-01`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K2", "claim": "`CAP-1-02`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "open data, cadence and the operator", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K3", "claim": "`CAP-1-03`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "the record's method and its limits", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K4", "claim": "`CAP-1-04`", "source": "Capture Registry, 2026-10-29", "M_src": "interpretation", "sense": "reception: the composition layer at the address", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K5", "claim": "`CAP-1-05`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "dates: runs from June, a September showing, the October announcement", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K6", "claim": "`CAP-1-06`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "dates: runs from June, a September showing, the October announcement", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K7", "claim": "`CAP-1-07`", "source": "Capture Registry, 2026-10-29", "M_src": "self-description", "sense": "dates: runs from June, a September showing, the October announcement", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K8", "claim": "`CAP-1-08`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "stated limits: access blocked, the crawler's blind spots", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K9", "claim": "`CAP-1-09`", "source": "Capture Registry, 2026-10-29", "M_src": "interpretation", "sense": "reception: the composition layer at the address", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K10", "claim": "`CAP-1-10`", "source": "Capture Registry, 2026-10-29", "M_src": "interpretation", "sense": "reception: the composition layer at the address", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K11", "claim": "`CAP-1-11`", "source": "Capture Registry, 2026-10-29", "M_src": "interpretation", "sense": "reception: the composition layer at the address", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K12", "claim": "`CAP-1-12`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "reception: the composition layer at the address", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K13", "claim": "`CAP-1-13`", "source": "Capture Registry, 2026-10-29", "M_src": "documented", "sense": "reception: the composition layer at the address", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing finding (an observation of the composition at the entity's address)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K14", "claim": "`PE-01`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "what it is: a free, open monthly monitor of whether news publishers keep embedded photo metadata", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K15", "claim": "`PE-02`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "what it is: a free, open monthly monitor of whether news publishers keep embedded photo metadata", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K16", "claim": "`PE-03`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "open data, cadence and the operator", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K17", "claim": "`PE-04`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K18", "claim": "`PE-05`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K19", "claim": "`PE-06`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K20", "claim": "`PE-07`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K21", "claim": "`PE-08`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "the transformation tested: credit lost between camera and reader", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K22", "claim": "`PE-09`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "findings: credit and the scored fields (October 2026)", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (restates the field: one lineage with B1, the announcement)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K23", "claim": "`PE-10`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (restates the field: one lineage with B1, the announcement)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K24", "claim": "`PE-11`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "open data, cadence and the operator", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (restates the field: one lineage with B1, the announcement)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K25", "claim": "`PE-12`", "source": "provenance census record, 2026-10-29", "M_src": "documented", "sense": "dates: runs from June, a September showing, the October announcement", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "qualified claim (F23, F32, F34, F27: the field dates runs from 2026-06-03 and a public showing in September 2026)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K26", "claim": "`PE-13`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "predecessors: IMATAG 2018 and the IPTC prototype crawler of 2019", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K27", "claim": "`PE-14`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "what it is: a free, open monthly monitor of whether news publishers keep embedded photo metadata", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K28", "claim": "`PE-15`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "predecessors: IMATAG 2018 and the IPTC prototype crawler of 2019", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K29", "claim": "`PE-16`", "source": "provenance census record, 2026-10-29", "M_src": "self-description", "sense": "the record's method and its limits", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K30", "claim": "`PE-17`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "predecessors: IMATAG 2018 and the IPTC prototype crawler of 2019", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (restates the field: one lineage with B1, the announcement)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K31", "claim": "`PE-18`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "stated limits: access blocked, the crawler's blind spots", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (restates the field: one lineage with B1, the announcement)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K32", "claim": "`PE-19`", "source": "provenance census record, 2026-10-29", "M_src": "attributed", "sense": "where the stripping happens: the publishing pipeline", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (restates the field: one lineage with B1, the announcement)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K33", "claim": "`PE-20`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "the record's method and its limits", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K34", "claim": "`PE-21`", "source": "provenance census record, 2026-10-29", "M_src": "stipulation", "sense": "the record's method and its limits", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K35", "claim": "`PE-22`", "source": "provenance census record, 2026-10-29", "M_src": "documented", "sense": "the record's method and its limits", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "none (the record's statement of a field the field also gives, or of its own method)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K36", "claim": "`O725-01`", "source": "#725", "M_src": "interpretation", "sense": "the artifact dimension of provenance", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K37", "claim": "`O725-02`", "source": "#725", "M_src": "interpretation", "sense": "adoption: uneven, under-adopted", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K38", "claim": "`O725-03`", "source": "#725", "M_src": "stipulation", "sense": "the artifact dimension of provenance", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K39", "claim": "`O725-04`", "source": "#725", "M_src": "interpretation", "sense": "artifact provenance kept, the meaning lost", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K40", "claim": "`O725-05`", "source": "#725", "M_src": "interpretation", "sense": "artifact provenance kept, the meaning lost", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K41", "claim": "`O725-06`", "source": "#725", "M_src": "interpretation", "sense": "adoption: uneven, under-adopted", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K42", "claim": "`O725-07`", "source": "#725", "M_src": "interpretation", "sense": "IPTC metadata as disclosure, not lineage", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K43", "claim": "`R1409-01`", "source": "#1409", "M_src": "stipulation", "sense": "the archive's own artifacts: the fields embedded, the membrane against stripping", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K44", "claim": "`O1409-02`", "source": "#1409", "M_src": "interpretation", "sense": "the archive's own artifacts: the fields embedded, the membrane against stripping", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K45", "claim": "`R1409-03`", "source": "#1409", "M_src": "stipulation", "sense": "IPTC metadata as disclosure, not lineage", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K46", "claim": "`O1409-04`", "source": "#1409", "M_src": "interpretation", "sense": "the archive's own artifacts: the fields embedded, the membrane against stripping", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K47", "claim": "`R1409-05`", "source": "#1409", "M_src": "stipulation", "sense": "the archive's own artifacts: the fields embedded, the membrane against stripping", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K48", "claim": "`O1409-06`", "source": "#1409", "M_src": "interpretation", "sense": "IPTC metadata as disclosure, not lineage", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K49", "claim": "`O1409-07`", "source": "#1409", "M_src": "interpretation", "sense": "trust anchors: the device's testimony and content derivation", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K50", "claim": "`O1443-01`", "source": "#1443", "M_src": "interpretation", "sense": "trust anchors: the device's testimony and content derivation", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K51", "claim": "`O1443-02`", "source": "#1443", "M_src": "attributed", "sense": "trust anchors: the device's testimony and content derivation", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K52", "claim": "`O1444-01`", "source": "#1444", "M_src": "interpretation", "sense": "trust anchors: the device's testimony and content derivation", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K53", "claim": "`O729-01`", "source": "#729", "M_src": "interpretation", "sense": "the artifact dimension of provenance", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K54", "claim": "`O729-02`", "source": "#729", "M_src": "interpretation", "sense": "artifact provenance kept, the meaning lost", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K55", "claim": "`O499-01`", "source": "#499", "M_src": "interpretation", "sense": "adoption: uneven, under-adopted", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K56", "claim": "`O615-01`", "source": "#615", "M_src": "interpretation", "sense": "artifact provenance kept, the meaning lost", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K57", "claim": "`O621-01`", "source": "#621", "M_src": "interpretation", "sense": "artifact provenance kept, the meaning lost", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K58", "claim": "`O127-01`", "source": "#127", "M_src": "interpretation", "sense": "artifact provenance kept, the meaning lost", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K59", "claim": "`O833-01`", "source": "#833", "M_src": "interpretation", "sense": "artifact provenance kept, the meaning lost", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K60", "claim": "`O1003-01`", "source": "#1003", "M_src": "interpretation", "sense": "the artifact dimension of provenance", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K61", "claim": "`O95-01`", "source": "#95", "M_src": "interpretation", "sense": "the artifact dimension of provenance", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K62", "claim": "`R204-01`", "source": "#204", "M_src": "stipulation", "sense": "the archive's own artifacts: the fields embedded, the membrane against stripping", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" }, { "K": "K63", "claim": "`R1432-01`", "source": "#1432", "M_src": "stipulation", "sense": "the archive's own artifacts: the fields embedded, the membrane against stripping", "qualifiers carried": "—", "f (source's own falsifiers)": "— (none stated; watch: a later composition at the address that states or drops the claim, attributed or not, uptake §8.3)", "contrast": "missing distinction (the field has no claim on the point)", "resolver": "a later capture at 'IPTC Metawatch' (ADDR-d50977993169) on Google AI Overview, seated in the Capture Registry (§8.3)" } ], "kernel_T": [ { "claim": "F9", "note": "the headline finding, 7.2% with credit or copyright against 8% in 2018, absent" }, { "claim": "F10", "note": "321 of 425 publishers keeping no scored field; 11% of images with any IPTC, absent" }, { "claim": "F16", "note": "27 of 6,580 images with a C2PA manifest, none from a camera or newsroom, absent" }, { "claim": "F14", "note": "the access limit (AP and USA Today blocking), absent" }, { "claim": "F11", "note": "where the stripping happens (the publishing pipeline, not the CDN), absent" }, { "claim": "F6", "note": "C2PA Content Credentials among the carriers checked, cut from the list" }, { "claim": "F8", "note": "the predecessors (IMATAG 2018, the 2019 crawler), absent" }, { "claim": "F23", "note": "the run dates from 2026-06-03, absent" }, { "claim": "F34", "note": "the September showing at the conference, absent" }, { "claim": "F25", "note": "the crawler's blind spot (no_images, not zero), absent" }, { "claim": "F15", "note": "AI-crawler blocking and the data-mining field, absent" }, { "claim": "F4", "note": "why the embedded record matters once an image is copied or crawled, absent" } ], "ledger": { "archive": "datasets/negative-of-the-negative/v2/ledgers/iptc-metawatch/ledger-archive.json", "field": "datasets/negative-of-the-negative/v2/ledgers/iptc-metawatch/field.json", "selection": "datasets/negative-of-the-negative/v2/traversal/iptc-metawatch/", "config": "datasets/negative-of-the-negative/v2/panel/configs/iptc-metawatch.json", "intake": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/", "audit": null }, "ontology": { "composition": "equal", "composition_note": "equal-terms case (v0.9 §0.9, §4.1): one claim space; the field's and the archive's claims ordered together by the entity's dependency and by genealogy within each sense; nothing translated; every field claim composed as received", "case": { "value": "equal", "statement": "The archive reads the field's entity as the entity: the provenance census record describes Metawatch from the IPTC's own announcement, each field with a verbatim quote and its basis, and asks of it the census's question (what provenance it carries, through which operation, with what evidence of survival); the Capture Registry reads the composition of the same monitor; the deposits that bear on its class (#725, #1409, #1443, #1444, #729 and the rest) state their relation to the content-provenance frameworks as extension and complement ('Extension and completion, not substitution or critique'; 'complementary rather than competing'). Nothing in the defining material contests what the monitor is; the archive adds senses on the field's own object (the dimension its carriers occupy, the loss beyond the file, the trust anchor, the archive's own practice with the same fields) and the capture's observation. No ontology is supplied that the field lacks, so the law of the suppressed witness does not apply (§0.10).", "loci": [ { "dep": "PE", "locus": "census.json rows[slug == 'iptc-metawatch'], provenance_object", "quote": "the lead photograph of a news article, as served to the reader" }, { "dep": "PE", "locus": "census.json rows[slug == 'iptc-metawatch'], transformations_tested", "quote": "publication through a news site's pipeline (CMS, CDN, image optimisation)" }, { "dep": "PE", "locus": "census.json organizing_question", "quote": "What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?" }, { "dep": "CAP", "locus": "iptc-metawatch-aio-20261029, analysis s1–2", "quote": "What the monitor measures is the erasure of credit in the publishing pipeline; the composition carries the instrument and leaves out its reading." }, { "dep": 725, "locus": "header, Relation", "quote": "Extension and completion, not substitution or critique" }, { "dep": 725, "locus": "Canonical Claim", "quote": "Existing provenance frameworks address the artifact (C2PA / Content Credentials) and the corpus (Data Provenance Initiative, EU AI Act transparency provisions, W3C PROV)." }, { "dep": 725, "locus": "§3 preamble", "quote": "This packet does not claim that contemporary frameworks fail." }, { "dep": 1443, "locus": "§6.1", "quote": "These are **complementary rather than competing**" } ] }, "E_F": { "type": "C (public entity: a monitor, a public service of the IPTC, with its open run data)", "definition": "the IPTC's free, open monitor that checks every month whether more than 500 news publishers in 122 countries keep the credits, captions and rights information embedded in their photographs (Exif, IPTC Photo Metadata in IIM and XMP, C2PA Content Credentials), scoring creator, caption, copyright and credit line; runs from 2026-06-03, introduced at the IPTC Photo Metadata Conference (post of 8 September 2026), announced 5 October 2026", "claims": [ "F1", "F21", "F5", "F6", "F28", "F7", "F19", "F26", "F3", "F8", "F34", "F23", "F20", "F9", "F10", "F14" ] }, "E_A": { "definition": "the same monitor, in the provenance census record and the archive's deposits: a monitor in the media lineage that tests whether the provenance carried in the lead photograph of a news article (creator, credit, copyright, caption, the data-mining preference, Content Credentials; embedded Exif, IPTC IIM and XMP and C2PA manifests) survives publication through a news site's pipeline, announced 5 October 2026; its carriers in the artifact dimension of provenance, which verifies the file at its creation and does not reach the lineage of meaning beyond it; read at the composition layer by the Capture Registry as an instrument composed without its reading", "claims": [ "PE-01", "PE-02", "PE-04", "PE-05", "PE-06", "PE-08", "PE-12", "O725-01", "O725-03", "O725-05", "O725-07", "O1444-01", "CAP-1-10" ], "defining_papers": [ 725, 1409, 1443, 1444, 729 ], "defining_records": [ "provenance census record (census.json rows[slug == 'iptc-metawatch'], rendered aggregators/iptc-metawatch/index.html, https://www.provenanceerasure.org/aggregators/iptc-metawatch/)", "Capture Registry iptc-metawatch-aio-20261029 (OBS-7f18ba03c974)" ] }, "rho": { "value": "extends", "status": "read from the census record, the capture record and the deposits that bear on the class (§1.2a); #725, the packet that defines the archive's dimensions of provenance, states its relation to the artifact frameworks as 'Extension and completion, not substitution or critique'", "statement": "the archive reads E_F as the entity and adds senses, mechanisms and limits on the field's own object: the artifact dimension its carriers occupy and what that dimension does not reach (the lineage of meaning, the composition layer); the trust anchor of Content Credentials (a device's testimony) beside content derivation; the archive's own embedding of the same fields and its membrane against their stripping; the census record's typing of object, carrier, unit and transformation; and the capture's observation of the composition at the address", "claims": [ "O725-01", "O725-03", "O725-04", "O725-05", "O725-07", "O1443-01", "O1444-01", "O1409-04", "R1409-01", "PE-04", "PE-06", "PE-08", "CAP-1-04", "CAP-1-10" ], "guard": "ρ = extends claims an addition and no more: no archive claim contradicts a field claim; the census record's dating (PE-12) is qualified by the field's earlier dates and composed beside them under P_coh; #725's artifact-layer category is applied to Content Credentials and IPTC AI metadata, which #725 names, and not extended to Exif", "considered": [ { "value": "constructs", "set_aside": "the archive does not read the monitor as made by receiving texts" }, { "value": "revises", "set_aside": "the entity is not the archive's own; the capture's note on the record's date qualifies the record, not the entity" } ] }, "translation": [ { "lineage": "what it is: a free, open monthly monitor of whether news publishers keep embedded photo metadata", "field_claims": [ "F1", "F21" ], "received": "F1 (B1, announcement, standfirst ¶1): \"The IPTC has launched Metawatch , a free, open monitor that checks every month whether more than 500 news publishers in 122 countries keep the credits, captions and rights information embedded in their photographs.\"; F21 (B2, overview, opening): \"Metawatch tracks how often major news publishers preserve embedded photo metadata (Exif, IPTC Photo Metadata (in both original IIM format and newer XMP format), and C2PA) on the images they publish. We crawl a curated list of publishers monthly and score the photographs they serve.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-01, PE-02, PE-14", "archive_claims": [ "PE-01", "PE-02", "PE-14" ] }, { "lineage": "the method: the lead photograph of up to 20 articles from each of 508 publishers, scored on the 4 Cs", "field_claims": [ "F5", "F6", "F28" ], "received": "F5 (B1, 'What Metawatch does' ¶1 s1–2): \"Metawatch checks every month: does the photo metadata survive publication? On the first of each month our well-behaved crawler visits 508 news publishers in 122 countries, takes up to 20 recent articles from each, and reads the lead photograph of every article.\"; F6 (B1, 'What Metawatch does' ¶1 s3): \"It checks each image for Exif, IPTC Photo Metadata (in both IIM and XMP form) and C2PA Content Credentials, and scores how each site carry the fields that matter most: creator, caption, copyright and credit line (the “4 Cs”).\"; F28 (B4, per-field page, ¶2): \"The \"scored\" badge marks the four fields that contribute to a site's overall score (the \"Four Cs\" of news photo provenance); the others are tracked for context but don't affect the score\"", "receiving_text": "—", "translation": "untranslated: composed as received beside CAP-1-01, PE-04, PE-05, PE-06, PE-07, PE-10", "archive_claims": [ "CAP-1-01", "PE-04", "PE-05", "PE-06", "PE-07", "PE-10" ] }, { "lineage": "open data, cadence and the operator", "field_claims": [ "F7", "F19", "F26" ], "received": "F7 (B1, 'What Metawatch does' ¶2): \"The crawler is deliberately light: about 40 to 60 requests per publisher per month, honouring robots.txt and keeping no article text or image files. How it works is documented in full, and every run is published as open data under CC BY 4.0, so anyone can check our numbers or ask their own questions.\"; F19 (B1, closing ¶): \"Metawatch automatically publishes new results on the first of every month.\"; F26 (B2, footer): \"Metawatch · A project of the International Press Telecommunications Council . Data licensed CC BY 4.0 . … Publishers may opt out by emailing office@iptc.org .\"", "receiving_text": "—", "translation": "untranslated: composed as received beside CAP-1-02, PE-03, PE-11", "archive_claims": [ "CAP-1-02", "PE-03", "PE-11" ] }, { "lineage": "the transformation tested: credit lost between camera and reader", "field_claims": [ "F3", "F4" ], "received": "F3 (B1, 'Credits are lost between camera and reader' (heading and ¶2)): \"Credits are lost between camera and reader … In practice, most of it is gone by the time a reader sees the picture. Content management systems re-encode images, content delivery networks resize them, and optimisation tools discard anything that looks like unnecessary bytes.\"; F4 (B1, 'Credits are lost between camera and reader' ¶3): \"When an image is copied, shared or collected by an AI crawler, the embedded metadata is often the only record of where it came from and on what terms it may be used.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-08", "archive_claims": [ "PE-08" ] }, { "lineage": "predecessors: IMATAG 2018 and the IPTC prototype crawler of 2019", "field_claims": [ "F8" ], "received": "F8 (B1, 'What Metawatch does' ¶3): \"Metawatch builds on IMATAG’s 2018 State of Image Metadata study and IPTC’s own prototype crawler from 2019 , presented at the 2019 Photo Metadata Conference . This service is different in that we now measure every month, so we can compare trends over time.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-13, PE-15, PE-17", "archive_claims": [ "PE-13", "PE-15", "PE-17" ] }, { "lineage": "dates: runs from June, a September showing, the October announcement", "field_claims": [ "F23", "F32", "F34", "F27", "F20" ], "received": "F23 (B2, overview, 'How this run’s top 10 ranked in earlier runs' (chart axis and point titles)): \"How this run’s top 10 ranked in earlier runs … 2026-06-03 2026-07-01 2026-08-01 2026-09-01 2026-10-01 … France: #1 of 26 on 2026-06-03 — score 22.8, 10 publishers\"; F32 (B5, dateline and ¶1 s1): \"Sep 8 2026 … Last Thursday, the photo metadata industry came together for the 2026 IPTC Photo Metadata Conference.\"; F34 (B5, last ¶ before the videos): \"Lastly, Brendan Quinn appeared again to introduce Metawatch , IPTC’s new public service that monitors real-world usage of metadata in images across the global news industry, tracking IPTC/XMP, C2PA, AI opt-outs and more.\"; F27 (B3, card title and snippet (LinkedIn unreachable)): \"IPTC Publishes Metawatch, Revealing Image Metadata Issues - LinkedIn … Sep 14, 2026 — International Press Telecommunications Council (IPTC) now publishes Metawatch. It crawls news publishers every month and checks what ...\"; F20 (B1, dateline and title): \"Oct 5 2026 … Announcing Metawatch: a monthly check on which news publishers keep photo metadata\"", "receiving_text": "—", "translation": "untranslated: composed as received beside CAP-1-05, CAP-1-06, CAP-1-07, PE-12", "archive_claims": [ "CAP-1-05", "CAP-1-06", "CAP-1-07", "PE-12" ] }, { "lineage": "movement: publishers and countries", "field_claims": [ "F12", "F13" ], "received": "F12 (B1, 'What we found' ¶4): \"USA Today carried no credit metadata when IMATAG measured it in 2019; in September 95% of its lead photographs carried credit, creator and copyright. Les Echos went from 6% to 75%. … Across the 294 publishers we have measured every month since June, the number keeping any metadata rose from 60 to 67. It is early, but the needle can move.\"; F13 (B1, 'Which countries do best' ¶1): \"France tops our October ranking, with an average publisher score of 19.8 out of 100, just ahead of Germany at 19.2. Taiwan enters at third. We rank only countries where we scored more than three publishers, so that one well-run newsroom cannot carry a whole country; 34 countries qualified this month.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside no archive claim (the sense is the field's alone)", "archive_claims": [] }, { "lineage": "the operator: the IPTC and its photo metadata standard", "field_claims": [ "F33", "F35", "F39", "F40", "F41" ], "received": "F33 (B5, ¶1 s3): \"This year we focussed on the industry’s implementation of recent legislation around AI transparency and content provenance, tracking real-world adoption of content transparency technologies by AI engines, news sites, software and services.\"; F35 (B6, tag archive, title and newest post): \"Photo Metadata Archives - IPTC … Oct 5 2026 … Announcing Metawatch: a monthly check on which news publishers keep photo metadata\"; F39 (B8, lead ¶1): \"The International Press Telecommunications Council ( IPTC ), based in London , United Kingdom , is a consortium of the world's major news agencies , other news providers and news industry vendors and acts as the global standards body of the news media.\"; F40 (B8, 'Photo metadata' ¶1–2): \"The IPTC defined a set of metadata properties that can be applied to images, part of a broader standard developed in the early 1990s and known as the IPTC Information Interchange Model (IIM). … The Extensible Metadata Platform (XMP) has largely superseded IIM's image file header structure\"; F41 (B8, 'Photo metadata' ¶3): \"Because of its nearly universal acceptance among photographers — even amateurs — this is by far IPTC's most widely used standard.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-12, PE-20, PE-21, PE-22", "archive_claims": [ "PE-12", "PE-20", "PE-21", "PE-22" ] }, { "lineage": "findings: credit and the scored fields (October 2026)", "field_claims": [ "F9", "F10", "F2", "F22", "F24", "F29" ], "received": "F9 (B1, 'What we found' ¶1): \"In 2018 IMATAG found that 8% of editorial images carried a credit or copyright notice. Applying the same test to our October run gives 7.2%. Whatever else has changed in news publishing since then, keeping the photographer’s credit attached to the photograph has not improved.\"; F10 (B1, 'What we found' ¶2): \"In the October run, 321 of the 425 publishers we could crawl, three out of four kept none of the IPTC fields we score on any image we sampled. Only 11% of the 6,580 images carried any IPTC metadata at all . The field that survives most often is the photographer’s name, on just 7.9% of images; the credit line is on 5.7% and copyright on 5.6%.\"; F2 (B1, announcement, standfirst ¶2): \"The first results show how little has changed since 2018, which publishers have fixed their sites, and why keeping metadata matters more than ever now that AI companies are crawling the web.\"; F22 (B2, overview, run summary): \"Latest run 2026-10-01 Sites crawled 425 Countries 122 Images analysed 6,580 … Mean IPTC score 5.96 … % with any IPTC 11% % with C2PA 0.5%\"; F24 (B2, overview, 'How the scores are distributed'): \"Any average describes almost nobody here: a small group embed metadata thoroughly, and 321 of 425 publishers embed none we can find at all.\"; F29 (B4, per-field page, table rows (Field, Type, Present, Total, Population, Score weight)): \"Creator scored 517 6,514 7.9% 25% … CreditLine scored 373 6,514 5.7% 25% … Copyright scored 348 6,514 5.3% 25% … CaptionDescription scored 324 6,514 5% 25%\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-09", "archive_claims": [ "PE-09" ] }, { "lineage": "where the stripping happens: the publishing pipeline", "field_claims": [ "F31", "F11", "F18" ], "received": "F31 (B4, per-field page, 'What this tells us'): \"Even the best-populated field — Creator at 7.9% — appears on fewer than one in ten images we fetched. The fields most relevant to licensing ( WebStatement , LicensorURL ) are below 3%. The dataset as a whole tells a consistent story: publishers and CDNs are discarding metadata that the photographers and agencies almost certainly embedded upstream.\"; F11 (B1, 'What we found' ¶3): \"It isn’t the CDN’s fault. Images served through Cloudflare, Akamai, CloudFront and Fastly lost their metadata 87% to 95% of the time, but images served with no CDN at all also lost metadata 87% of the time. Stripping appears to happen in the publishing pipeline, which means that publishers can fix it.\"; F18 (B1, 'What publishers can do' ¶1 s1–2): \"The fix is usually a setting, not a project. Most image pipelines strip metadata by default to save a few kilobytes; most can be told to keep it.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-19", "archive_claims": [ "PE-19" ] }, { "lineage": "AI: crawler blocking, the data-mining field, Content Credentials, the AI fields", "field_claims": [ "F15", "F16", "F17", "F30", "F36" ], "received": "F15 (B1, 'AI: a locked front door, an open back door' ¶1–2): \"Of the 505 publishers whose policies we checked, 234 (46%) block at least one AI crawler in their robots.txt. … But robots.txt protects a website, not a photograph. … IPTC Photo Metadata has a field for exactly this: PLUS Data Mining . Only 15 publishers (3.0%) put it on any image we sampled, and it appears on 0.6% of images overall.\"; F16 (B1, 'AI: a locked front door, an open back door' ¶3 s1–2): \"Leaving out IPTC’s own site, 27 of the 6,580 images we analysed carried a C2PA manifest, and all but one were signed by an AI or design tool: OpenAI, Adobe, Canva or Google (the last had a signer we couldn’t read). None came from a camera or a newsroom’s own signing.\"; F17 (B1, 'AI: a locked front door, an open back door' ¶3 s3–4): \"Seven images carried an IPTC Digital Source Type saying they had been edited with generative AI, which is exactly the kind of disclosure the field was designed for. Provenance in news photography is arriving first through the tools that make synthetic images, not through the photojournalism that most needs it.\"; F30 (B4, per-field page, table rows (AI fields)): \"DigitalSourceType tracked 15 6,514 0.2% … AIPromptInformation tracked 0 6,514 0% … AISystemUsed tracked 0 6,514 0%\"; F36 (B6, tag archive, post of 27 November 2025): \"Nov 27 2025 … IPTC Photo Metadata Standard adds new properties for AI-generated content\"", "receiving_text": "—", "translation": "untranslated: composed as received beside O127-01", "archive_claims": [ "O127-01" ] }, { "lineage": "stated limits: access blocked, the crawler's blind spots", "field_claims": [ "F14", "F25" ], "received": "F14 (B1, 'Which countries do best' ¶2 (after the chart)): \"The United States led in September and slipped to fourth in October, but only because two of its best-scoring publishers were out of reach: AP and USA Today began blocking automated access this month. It is a reminder that bot-blocking aimed at AI also shuts out research.\"; F25 (B2, overview, 'How the scores are distributed', note): \"Publishers we reached but got no photograph from are listed separately as no_images rather than scored zero, since that is usually our blind spot rather than their practice.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside CAP-1-08, PE-18", "archive_claims": [ "CAP-1-08", "PE-18" ] }, { "lineage": "reception: the encyclopedia", "field_claims": [ "F37", "F38" ], "received": "F37 (B7, Wikipedia: titles IPTC_Metawatch and Metawatch; full-text search): \"raw wikitext IPTC_Metawatch (action=raw, redirect=no): HTTP 404 … Wikipedia does not have an article with this exact name. … full-text search for \"Metawatch\" IPTC (namespace 0): There were no results matching the query.\"; F38 (B7, Wikipedia: the operator's article, searched for the name): \"operator's article International_Press_Telecommunications_Council (raw wikitext action=raw, HTTP 200; rendered page HTTP 200, saved as B8): the string Metawatch does not occur in either.\"", "receiving_text": "—", "translation": "untranslated: composed as received beside PE-20, PE-21, PE-22", "archive_claims": [ "PE-20", "PE-21", "PE-22" ] } ], "receiving_texts": "equal-terms case: every field claim composed as received, beside the archive claims it stands with" }, "measure": { "rule": "v0.9 §4.10: KO_B sentences surviving in the KO at similarity ≥ 0.95, with positions (computed as apply_v09.py does: difflib.SequenceMatcher ratio, the best KO sentence for each KO_B sentence)", "v0.9": { "surviving": 0, "of": 12, "positions": [ null, null, null, null, null, null, null, null, null, null, null, null ] }, "opening_run": { "rule": "v0.9 §5.10 (equal-terms case): the field-only KO's sentences as the KO's opening run in their own order", "breach": false }, "blocks": { "rule": "v0.9 §4.1 (equal-terms and mixed cases): the KO does not open with the field as a block or close with the archive as one; sentences typed by the ledgers of the claims they cite (F field-only, A archive-only, M both)", "sequence": "MMAMMMAMFFMAMFMAAFMFAAAMAAAAAM", "field_only_head": 0, "archive_only_tail": 0, "breach": false }, "max_similarity": [ 0.3, 0.305, 0.336, 0.131, 0.409, 0.204, 0.265, 0.163, 0.36, 0.214, 0.328, 0.084 ], "ko_sentence_1_max_similarity_to_KO_B": 0.3 }, "homonyms": { "names": [ "MetaWatch" ], "basis": "The census record carries no disambiguation field; its negative tags keep the monitor apart from the IPTC's 2019 social-media test and from a C2PA verifier (PE-13, PE-14). No card is a homonym. Wikipedia's only article under the name is 'MetaWatch', a discontinued smartwatch brand of Meta Watch Ltd. (Strata and Frame, 2012; B7-MetaWatch-homonym.wiki), and the web searches for the LinkedIn card returned the same smartwatch (makezine, techcrunch, ablogtowatch): a distinct entity, never a sense of the name.", "distinct_entities": [ "MetaWatch (smartwatch brand, Meta Watch Ltd.; Wikipedia: MetaWatch)", "the IPTC (the operator)", "the IPTC Photo Metadata Standard (the carrier the monitor tests)", "the IPTC's 2019 social-media photo metadata test (census row iptc-photo-metadata-tests, of which the census makes Metawatch a part)", "IMATAG's 2018 State of Image Metadata study (a predecessor)", "C2PA conformance (census neighbour c2pa-conformance)", "github.com/iptc/metawatch (the monitor's source repository)" ], "neighbours": "Census relations: part_of iptc-photo-metadata-tests; neighbour c2pa-conformance. No /non row exists for either at build time (datasets/negative-of-the-negative/v2/rows/ holds none); if one is built, it is the neighbour. The MMRS row data-provenance-explorer (datasets/negative-of-the-negative/v2/rows/data-provenance-explorer.json) shares #725's dimensions (its corpus dimension; this row's artifact dimension).", "substitutes": { "T": [] }, "register": { "address_1": { "slug": "iptc-metawatch-aio-20261029", "obs_id": "OBS-7f18ba03c974" } } }, "notes": [ "One address, Google AI Overview (expanded), signed out, incognito, 2026-10-29: iptc-metawatch-aio-20261029 (OBS-7f18ba03c974, ADDR-d50977993169, AXN:0ACF.CAPTURE.🔩🟤◀️⛵⏫🌻), six cards, 123 words in the answer body. A NEW address; the census record landed the same day and no card cites it (CAP-1-12).", "The dates (the task's note): two cards date the monitor's public appearance to September 2026 and the census record dates it by the 5 October announcement. Fetched: the IPTC post (B5, https://iptc.org/news/iptc-photo-metadata-conference-2026-videos-are-now-available/, published 2026-09-08T12:35:00+00:00) says the 2026 Photo Metadata Conference was held 'Last Thursday' (the Thursday before 8 September 2026 is 3 September) and that 'Lastly, Brendan Quinn appeared again to introduce Metawatch , IPTC’s new public service that monitors real-world usage of metadata in images across the global news industry, tracking IPTC/XMP, C2PA, AI opt-outs and more' (F32, F34); the conference videos are said to be public on the event page. The LinkedIn post (B3) could not be found or fetched; its card alone says 'Sep 14, 2026 — International Press Telecommunications Council (IPTC) now publishes Metawatch. It crawls news publishers every month and checks what ...' (F27). The monitor's own overview dates its runs from 2026-06-03 (then 07-01, 08-01, 09-01, 10-01; F23), and the announcement itself counts '294 publishers we have measured every month since June' and gives USA Today's September figure (F12). So: runs since June 2026, shown publicly at the conference in early September (reported 8 September), announced 5 October.", "Wikipedia: no article for the entity: IPTC_Metawatch and Metawatch return HTTP 404 (raw wikitext with redirect=no, and rendered), neither is a redirect, and the full-text search for '\"Metawatch\" IPTC' returns no results (B7). The bare search returns 'MetaWatch', a smartwatch brand (homonym). The operator's article (International_Press_Telecommunications_Council, B8) exists and does not name Metawatch. Two Wikipedia requests answered 429 and were retried after a pause.", "Fetching: every reachable page saved verbatim with curl on 2026-10-29 between 17:09 and 17:12 UTC, raw and text with sha256 in field.json. All five reachable cards are the operator's pages (iptc.org, metawatch.iptc.org), served as static HTML. Card URLs: B1, B2 and B4 by the cards' titles on the operator's sites (B2 and B4 linked from each other's navigation); B5 by its title in the IPTC news archive for September 2026; B6 by the WordPress tag-archive title; B3 not found (field.json records the tries). Card 6's date (22 October 2026) is the newest post in the page's menu, not the tag archive's newest post (5 October).", "Own pages: the census record read one source, the announcement, which is card 1; it is carried once, as a card, and the census's saved copy (sha256 0a7fea35…, equal to the record's) sits beside the fresh fetch as B1-census.html/.txt. The fresh fetch differs in raw hash (page furniture); the article body is identical in the two texts. The record's url (metawatch.iptc.org) is card 2. No census source has basis third_party.", "The archive subset: the string pass (non_traverse.py, config panel/configs/iptc-metawatch.json) returned 17 D, 3 R and 92 O candidates in 37 deposits; no deposit names Metawatch (every D candidate matches the operator's acronym). Reading admitted 19 deposits from the string pass and 3 from the hop (164 hop candidates): 14 with claims (#725, #1409, #1443, #1444, #729, #499, #615, #621, #127, #833, #1003, #95, #204, #1432) and 8 as instances under them (#1190, #1369, #1386, #50, #1175, #121, #1194, #1188); 17 candidate deposits not admitted, with reasons. Hop candidates without the entity's or the class's strings were rejected on a string screen and title, not read whole.", "String-pass defect (reported, not fixed): sentences are cut at 900 characters, so #725's disambiguation table lost its 'IPTC AI metadata' row (O725-07, found by reading).", "Defects and out-of-date fields in the provenance census record (reported, not fixed): (a) founded and lifecycle.detail read 'announced 5 October 2026', and version_and_time has only 'announced': the record's own source shows monthly measurement 'since June' and a September figure (B1 F12), the monitor's overview dates runs from 2026-06-03 (B2 F23), and the IPTC's post of 8 September reports its introduction at the Photo Metadata Conference (B5 F34); 'founded' conflates the announcement with the start. (b) unchecked lists 'the Metawatch site itself and its published run data': the site is now read (B2, B4) and agrees with the record's retention figures (425 crawled, 6,580 images, 321 with none); it adds a figure the record does not carry, copyright on 5.3% of 6,514 images (B4 F29) against the announcement's 5.6% (B1 F10). (c) count '508 news publishers in 122 countries' is the number visited; 425 were crawlable in the October run (B1 F10; B2 'Sites crawled 425'), and the overview's country chart counts 120 countries (B2). (d) The record's one source is keyed 'iptc-photo-metadata-tests--metawatch' and saved under that prefix (sources/iptc-photo-metadata-tests--metawatch.*), the parent row's slug, not 'iptc-metawatch--…' as the addendum's path pattern expects. (e) cadence 'monthly, on the first of each month': the first run is dated 2026-06-03 (B2).", "Defects in the capture (reported, not fixed): (a) cite_list marks all six cards rel 'third_party', though five are the operator's own pages (iptc.org, metawatch.iptc.org) and only the LinkedIn post is a third party. (b) The reading's 'a monitor three weeks old' counts from the 5 October announcement; the field dates runs from June and a public showing in early September. (c) findings[2] carries the September showing 'unchecked against the posts themselves': the IPTC post is now checked (B5) and confirms it; the LinkedIn post remains unread.", "Delta, beyond the capture's findings: T's list of what is checked drops C2PA Content Credentials, which the announcement and the overview both name (F6, F21); and 'over 500 news publishers' is the visited count, without the 425 that could be crawled.", "Ledgers unaudited (§3.8: one extractor). KO 30 sentences, every field claim (41) and archive claim (63) cited; P body 337 words; KO_B 12 sentences, none surviving at ≥ 0.95 (max 0.409)." ], "composition_v09": { "source": "this row (composed directly; no rebuild/negative-of-the-negative/v09/iptc-metawatch.json)", "composer": "Claude (Opus 5.5), subagent, 2026-10-29", "defining_material_read": [ { "what": "provenance census record, row", "file": "/home/claude/fleet/provenance-erasure/data/provenance-census/census.json (rows[slug == 'iptc-metawatch'], organizing_question, schema_note)", "read": "whole" }, { "what": "provenance census record, its saved source", "file": "/home/claude/fleet/provenance-erasure/data/provenance-census/sources/iptc-photo-metadata-tests--metawatch.txt", "read": "whole" }, { "what": "Capture Registry entry", "file": "data/EA-WG-CAPTURES-01.json (entries[slug == 'iptc-metawatch-aio-20261029'])", "read": "whole" }, { "dep": 725, "file": "data/texts/AXN-0273-text.md", "read": "the passages on the dimensions, C2PA and IPTC (§0, §1.4, §3.1, the disambiguation table)" }, { "dep": 1409, "file": "data/texts/AXN-0592-text.md", "read": "the paragraphs naming IPTC, C2PA and metadata stripping (paras 44, 49, 81, 98, 104, 130, 205)" }, { "dep": 1443, "file": "data/texts/AXN-05CC-text.md", "read": "§6.1" }, { "dep": 1444, "file": "data/texts/AXN-05CE-text.md", "read": "the incumbency ring" }, { "dep": 729, "file": "data/texts/AXN-027C-text.md", "read": "the three-layer table and §8.7" }, { "what": "the candidate sentences of every other admitted or rejected deposit, with their paragraphs", "file": "datasets/negative-of-the-negative/v2/traversal/iptc-metawatch/candidates-*.jsonl", "read": "each candidate with its paragraph" } ], "cuts": [], "notes": "equal case; KO 30 sentences, all 41 field and 63 archive claims cited; P body 337 words; KO_B 12 sentences, none surviving at ≥ 0.95" }, "field_by_origin": { "cards": [ "B1", "B2", "B3", "B4", "B5", "B6" ], "own_pages": [], "own_pages_as_cards": [ "B1", "B2" ], "census_third_party": [], "wikipedia": [ "B7", "B8" ], "unreachable": [ "B3" ], "title_only": [ "B3" ], "script_rendered": [], "wikipedia_state": "no article: 'IPTC Metawatch' and 'Metawatch' are absent (raw wikitext HTTP 404 with redirect=no; rendered page HTTP 404 'Wikipedia does not have an article with this exact name'); neither is a redirect; the full-text search for '\"Metawatch\" IPTC' returns no results; the bare search finds only 'MetaWatch', a discontinued smartwatch brand (a homonym). The operator's article, International Press Telecommunications Council, exists (HTTP 200) and does not contain the string 'Metawatch'.", "sources": [ { "id": "B1", "origin": "card", "role": "Overview card 1", "card": "IPTC — Announcing Metawatch: a monthly check on which news publishers keep ... - IPTC", "url": "https://iptc.org/news/announcing-iptc-metawatch/", "kind": "Overview card (own page; the one source the provenance census record read)", "surfaced_by_T": [ { "slug": "iptc-metawatch-aio-20261029", "card": 1 } ], "files": { "B1.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B1.html", "sha256": "23d67ed30137cda56cf594ad64e48fb780a6f08953a8c4348e4ee4bf671ff0e5" }, "B1.txt": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B1.txt", "sha256": "18f7fcf5c0e6a366a6eb131047d629a6229a11caabe3bad3788d645e76766626" }, "B1-census.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B1-census.html", "sha256": "0a7fea35f38f83bbc3a4f2807ea580ed054e661b774a5055703b693632f5da3d" }, "B1-census.txt": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B1-census.txt", "sha256": "f16eb60c2c8bb21914b1efe5646594ef867f8d9968c2ac7c00df902b144a7f90" } }, "fetched": { "at": "2026-10-29T17:09:58Z", "http": 200, "url": "https://iptc.org/news/announcing-iptc-metawatch/", "raw": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B1.html", "raw_sha256": "23d67ed30137cda56cf594ad64e48fb780a6f08953a8c4348e4ee4bf671ff0e5", "text": [ "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B1.txt" ], "text_sha256": "18f7fcf5c0e6a366a6eb131047d629a6229a11caabe3bad3788d645e76766626", "tries": [ { "at": "2026-10-29T17:09:58Z", "url": "https://iptc.org/news/announcing-iptc-metawatch/", "http": 200, "effective_url": "https://iptc.org/news/announcing-iptc-metawatch/", "error": null } ], "census_copy": { "url": "https://iptc.org/news/announcing-iptc-metawatch/", "read": "2026-10-29", "http": "200", "sha256_recorded": "0a7fea35f38f83bbc3a4f2807ea580ed054e661b774a5055703b693632f5da3d", "sha256_of_copy": "0a7fea35f38f83bbc3a4f2807ea580ed054e661b774a5055703b693632f5da3d", "match": true, "copied_from": "/home/claude/fleet/provenance-erasure/data/provenance-census/sources/iptc-photo-metadata-tests--metawatch.html.gz (and .txt)" } }, "card_title": "Announcing Metawatch: a monthly check on which news publishers keep ... - IPTC", "card_snippet": "Oct 5, 2026 — The IPTC has launched Metawatch, a free, open monitor that checks every month whether more than 500 news publishers in 122 countries keep the ...", "card_note": null, "names_operator": "yes ('IPTC' in the saved text)", "names_archive": "no (none of the Crimson Hexagonal Archive, Alexanarch, Lee Sharks, machinemediation, provenanceerasure, EA-WG-CAPTURES-01 in the saved text, card title and snippet)", "note": "The IPTC's announcement, posted 5 October 2026. URL identified by the card's title (the page's is 'Announcing Metawatch: a monthly check on which news publishers keep photo metadata - IPTC') and confirmed by the snippet's opening sentence in the saved text. It is also the entity's own page that the provenance census record cites (census.json rows[slug == 'iptc-metawatch'].sources['iptc-photo-metadata-tests--metawatch'], read 2026-10-29, http 200, sha256 0a7fea35f38f83bb…): carried once, as a card (the own page is surfaced by T). The census's saved copy is copied beside the fresh fetch as B1-census.html (gunzipped from sources/iptc-photo-metadata-tests--metawatch.html.gz; its sha256 equals the census's recorded sha256) and B1-census.txt (the census's own text extraction). The fresh fetch's HTML differs in hash (WordPress page furniture); the article body from the dateline 'Oct 5 2026' to the closing 'Categories' is identical in the two extracted texts (7,710 characters, whitespace-normalised). Quotes are checked against B1.txt." }, { "id": "B2", "origin": "card", "role": "Overview card 2", "card": "IPTC — Overview — Metawatch - IPTC", "url": "https://metawatch.iptc.org/", "kind": "Overview card (the monitor's own site, home; the census record's url)", "surfaced_by_T": [ { "slug": "iptc-metawatch-aio-20261029", "card": 2 } ], "files": { "B2.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B2.html", "sha256": "4a9a9fb3a2a1ae5a097dfc1e0197c2e68e516b4ad66a1bb47d80ecbc06b9b730" }, "B2.txt": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B2.txt", "sha256": "0214693d56a73dc918d9b3ddd5c12f17f351c257eb57c8bcbfff3b580f8db194" } }, "fetched": { "at": "2026-10-29T17:09:58Z", "http": 200, "url": "https://metawatch.iptc.org/", "raw": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B2.html", "raw_sha256": "4a9a9fb3a2a1ae5a097dfc1e0197c2e68e516b4ad66a1bb47d80ecbc06b9b730", "text": [ "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B2.txt" ], "text_sha256": "0214693d56a73dc918d9b3ddd5c12f17f351c257eb57c8bcbfff3b580f8db194", "tries": [ { "at": "2026-10-29T17:09:58Z", "url": "https://metawatch.iptc.org/", "http": 200, "effective_url": "https://metawatch.iptc.org/", "error": null } ] }, "card_title": "Overview — Metawatch - IPTC", "card_snippet": "Metawatch tracks how often major news publishers preserve embedded photo metadata (Exif, IPTC Photo Metadata (in both original IIM format and newer XMP format),", "card_note": null, "names_operator": "yes ('IPTC' in the saved text)", "names_archive": "no (none of the Crimson Hexagonal Archive, Alexanarch, Lee Sharks, machinemediation, provenanceerasure, EA-WG-CAPTURES-01 in the saved text, card title and snippet)", "note": "Metawatch's overview page, the census record's url field (https://metawatch.iptc.org/), which the census lists as unchecked ('the Metawatch site itself and its published run data'). Served as static HTML (Astro); the text keeps the SVG chart titles, which carry the run dates. The card's snippet is the page's opening sentence." }, { "id": "B3", "origin": "card", "role": "Overview card 3", "card": "LinkedIn·Paul Melcher — IPTC Publishes Metawatch, Revealing Image Metadata Issues - LinkedIn", "url": null, "kind": "Overview card (unreachable)", "surfaced_by_T": [ { "slug": "iptc-metawatch-aio-20261029", "card": 3 } ], "files": {}, "fetched": { "unreachable": true, "tries": [ { "at": "2026-10-29, 17:00–17:10 UTC (not logged to the second)", "tool": "WebSearch", "query": "Paul Melcher LinkedIn \"IPTC Publishes Metawatch\"", "result": "no LinkedIn post returned (metawatch.iptc.org pages, Melcher profiles and kaptur.co pages)" }, { "at": "2026-10-29, 17:00–17:10 UTC (not logged to the second)", "tool": "WebSearch (extended)", "query": "linkedin.com Paul Melcher Metawatch IPTC crawls news publishers every month", "result": "profiles (linkedin.com/in/melcher/, linkedin.com/in/brendanquinn/) and the IPTC pages; no post" }, { "at": "2026-10-29, 17:00–17:10 UTC (not logged to the second)", "tool": "WebSearch", "query": "\"Metawatch\" \"Revealing Image Metadata Issues\"", "result": "no match" }, { "at": "2026-10-29, 17:00–17:10 UTC (not logged to the second)", "tool": "WebSearch (extended)", "query": "\"now publishes Metawatch\" International Press Telecommunications Council", "result": "no match (Wikipedia IPTC pages; the MetaWatch smartwatch)" }, { "at": "2026-10-29, 17:00–17:10 UTC (not logged to the second)", "tool": "WebSearch", "query": "site:linkedin.com/posts melcher metawatch", "result": "only the MetaWatch smartwatch (a homonym)" }, { "at": "2026-10-29, 17:00–17:10 UTC (not logged to the second)", "tool": "curl", "url": "https://www.linkedin.com/pulse/iptc-publishes-metawatch-revealing-image-metadata-issues-paul-melcher", "http": 200, "result": "redirected to https://www.linkedin.com/top-content/?trk=article_not_found (no such article at the guessed slug)" }, { "at": "2026-10-29, 17:00–17:10 UTC (not logged to the second)", "tool": "curl", "url": "https://www.linkedin.com/in/melcher/", "http": 301, "result": "profile redirect (sign-in wall); activity not readable signed out" }, { "at": "2026-10-29, 17:00–17:10 UTC (not logged to the second)", "tool": "curl", "url": "https://www.bing.com/search?q=%22IPTC+Publishes+Metawatch%22", "http": 200, "result": "no result for the phrase" } ], "note": "The card carries no URL (the paste gives Google redirect tokens only) and the post could not be found by its title and site; a LinkedIn post URL carries an activity id that cannot be derived from the title. Its title and snippet stand as its only text (F27). The exact times of the WebSearch tries were not logged to the second; all were made between 17:00 and 17:10 UTC on 2026-10-29." }, "card_title": "IPTC Publishes Metawatch, Revealing Image Metadata Issues - LinkedIn", "card_snippet": "Sep 14, 2026 — International Press Telecommunications Council (IPTC) now publishes Metawatch. It crawls news publishers every month and checks what ...", "card_note": "unreachable: title and snippet only", "names_operator": "yes ('International Press Telecommunications Council (IPTC)' in the snippet)", "names_archive": "no (title and snippet)", "note": "Paul Melcher's LinkedIn post, dated by its card 14 September 2026. One of the two cards that date the monitor's public appearance to September 2026." }, { "id": "B4", "origin": "card", "role": "Overview card 4", "card": "IPTC — Per-field breakdown - Metawatch - IPTC", "url": "https://metawatch.iptc.org/fields/", "kind": "Overview card (the monitor's own site, per-field page)", "surfaced_by_T": [ { "slug": "iptc-metawatch-aio-20261029", "card": 4 } ], "files": { "B4.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B4.html", "sha256": "320d791c70043eb150607bc6a984c2204cf3f250dcd2bc77f263d09f2fc7ca18" }, "B4.txt": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B4.txt", "sha256": "7776927a7a2be141bc0158f68c39f13106e38825de6489695069175ec4ae61d9" } }, "fetched": { "at": "2026-10-29T17:09:59Z", "http": 200, "url": "https://metawatch.iptc.org/fields/", "raw": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B4.html", "raw_sha256": "320d791c70043eb150607bc6a984c2204cf3f250dcd2bc77f263d09f2fc7ca18", "text": [ "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B4.txt" ], "text_sha256": "7776927a7a2be141bc0158f68c39f13106e38825de6489695069175ec4ae61d9", "tries": [ { "at": "2026-10-29T17:09:59Z", "url": "https://metawatch.iptc.org/fields/", "http": 200, "effective_url": "https://metawatch.iptc.org/fields/", "error": null } ] }, "card_title": "Per-field breakdown - Metawatch - IPTC", "card_snippet": "Metawatch — tracking image metadata across news publishers worldwide.", "card_note": null, "names_operator": "yes ('IPTC' in the saved text)", "names_archive": "no (none of the Crimson Hexagonal Archive, Alexanarch, Lee Sharks, machinemediation, provenanceerasure, EA-WG-CAPTURES-01 in the saved text, card title and snippet)", "note": "Metawatch's per-field breakdown, linked from the overview's navigation ('Fields'); title 'Per-field breakdown — Metawatch'; the card's snippet is the page's meta description." }, { "id": "B5", "origin": "card", "role": "Overview card 5", "card": "IPTC — Watching AI platforms, news publishers and real-world C2PA - IPTC", "url": "https://iptc.org/news/iptc-photo-metadata-conference-2026-videos-are-now-available/", "kind": "Overview card (operator page: the conference report)", "surfaced_by_T": [ { "slug": "iptc-metawatch-aio-20261029", "card": 5 } ], "files": { "B5.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B5.html", "sha256": "a2176a9721211134bf01bd1278dd23acdda0db3513f31d818964060c448d0f96" }, "B5.txt": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B5.txt", "sha256": "c5bb8d7509c13bacde9cdbff72b2167651d6eead8ad6d41c317b79e2e8b0d7fa" } }, "fetched": { "at": "2026-10-29T17:10:00Z", "http": 200, "url": "https://iptc.org/news/iptc-photo-metadata-conference-2026-videos-are-now-available/", "raw": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B5.html", "raw_sha256": "a2176a9721211134bf01bd1278dd23acdda0db3513f31d818964060c448d0f96", "text": [ "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B5.txt" ], "text_sha256": "c5bb8d7509c13bacde9cdbff72b2167651d6eead8ad6d41c317b79e2e8b0d7fa", "tries": [ { "at": "2026-10-29T17:10:00Z", "url": "https://iptc.org/news/iptc-photo-metadata-conference-2026-videos-are-now-available/", "http": 200, "effective_url": "https://iptc.org/news/iptc-photo-metadata-conference-2026-videos-are-now-available/", "error": null } ] }, "card_title": "Watching AI platforms, news publishers and real-world C2PA - IPTC", "card_snippet": "Sep 8, 2026 — Lastly, Brendan Quinn appeared again to introduce Metawatch, IPTC's new public service that monitors real-world usage of metadata in images ...", "card_note": null, "names_operator": "yes ('IPTC' in the saved text)", "names_archive": "no (none of the Crimson Hexagonal Archive, Alexanarch, Lee Sharks, machinemediation, provenanceerasure, EA-WG-CAPTURES-01 in the saved text, card title and snippet)", "note": "The IPTC's post 'Watching AI platforms, news publishers and real-world C2PA – IPTC Photo Metadata Conference 2026 videos are now available', published 2026-09-08T12:35:00+00:00 (article:published_time; modified 12:43:06), found in the IPTC news archive for September 2026 (https://iptc.org/news/2026/09/) by its title and confirmed by the snippet's sentence ('Lastly, Brendan Quinn appeared again to introduce Metawatch') in the saved text. The post dates the conference 'Last Thursday'." }, { "id": "B6", "origin": "card", "role": "Overview card 6", "card": "IPTC — Photo Metadata Archives - IPTC", "url": "https://iptc.org/news/tag/photo-metadata/", "kind": "Overview card (operator page: the 'Photo Metadata' tag archive)", "surfaced_by_T": [ { "slug": "iptc-metawatch-aio-20261029", "card": 6 } ], "files": { "B6.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B6.html", "sha256": "4afb0a05b1a4f8fe5b37129b9f3a4b8bae44b42524ce884ba93462e481cd7032" }, "B6.txt": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B6.txt", "sha256": "b1633287a8889a7e0e0f5b212df54da9450db7129ebafa8fdd573a886822e35e" } }, "fetched": { "at": "2026-10-29T17:10:01Z", "http": 200, "url": "https://iptc.org/news/tag/photo-metadata/", "raw": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B6.html", "raw_sha256": "4afb0a05b1a4f8fe5b37129b9f3a4b8bae44b42524ce884ba93462e481cd7032", "text": [ "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B6.txt" ], "text_sha256": "b1633287a8889a7e0e0f5b212df54da9450db7129ebafa8fdd573a886822e35e", "tries": [ { "at": "2026-10-29T17:10:01Z", "url": "https://iptc.org/news/tag/photo-metadata/", "http": 200, "effective_url": "https://iptc.org/news/tag/photo-metadata/", "error": null } ] }, "card_title": "Photo Metadata Archives - IPTC", "card_snippet": "Oct 22, 2026 — The IPTC has launched Metawatch, a free, open monitor that checks every month whether more than 500 news publishers in 122 countries keep the credits, captions ...", "card_note": null, "names_operator": "yes ('IPTC' in the saved text)", "names_archive": "no (none of the Crimson Hexagonal Archive, Alexanarch, Lee Sharks, machinemediation, provenanceerasure, EA-WG-CAPTURES-01 in the saved text, card title and snippet)", "note": "The IPTC news archive for the tag 'Photo Metadata' (page title 'Photo Metadata Archives - IPTC', the card's title). The card's date, 22 October 2026, is the date of the newest post in the page's 'Latest' menu (the Autumn Meeting report); the archive's newest tagged post is the Metawatch announcement of 5 October 2026, whose opening sentence is the card's snippet." }, { "id": "B7", "origin": "wikipedia", "role": "Wikipedia: the entity", "card": "Wikipedia — IPTC Metawatch / Metawatch (no article)", "url": "https://en.wikipedia.org/wiki/IPTC_Metawatch", "kind": "Wikipedia title (no article)", "surfaced_by_T": [], "files": { "B7.wiki": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B7.wiki", "sha256": "ab5b734ed1436ef217e239ae39f1f2a5b18cda9318f6059961eb7d949f6ad31b" }, "B7.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B7.html", "sha256": "e8dfe552afbe33e9cf40318c1808b552b04556a60312daf87219e7cc58ce304d" }, "B7-Metawatch.wiki": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B7-Metawatch.wiki", "sha256": "e30d400fbf5f8f495835de1674b6fba0f4ebb4cc4a1c1f579b2c3398e04ff7b1" }, "B7-search.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B7-search.html", "sha256": "5315a0b6d6fd6838103ef92f461762bd83ff19189234ef510e61315e45e92f68" }, "B7-search-bare.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B7-search-bare.html", "sha256": "cc59513dc46b805403374ec52e2cff749e555187369b34cc99694f58f94cf55a" }, "B7-MetaWatch-homonym.wiki": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B7-MetaWatch-homonym.wiki", "sha256": "8f958b83312b8caed86090c6c154f342af9c60f730ad0e38599e0f2f94080e5d" }, "B7.txt": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B7.txt", "sha256": "8d4106a54ed94b0845e0e6846ba3a359e3ba7b1f431a6d8856e142ec4fa03c25" } }, "fetched": { "log": [ { "at": "2026-10-29T17:10:50Z", "url": "https://en.wikipedia.org/w/index.php?title=IPTC_Metawatch&action=raw&redirect=no", "http": "404" }, { "at": "2026-10-29T17:10:58Z", "url": "https://en.wikipedia.org/wiki/IPTC_Metawatch", "http": "404" }, { "at": "2026-10-29T17:11:06Z", "url": "https://en.wikipedia.org/w/index.php?title=Metawatch&action=raw&redirect=no", "http": "404" }, { "at": "2026-10-29T17:11:13Z", "url": "https://en.wikipedia.org/w/index.php?search=%22Metawatch%22+IPTC&title=Special:Search&profile=advanced&fulltext=1&ns0=1", "http": "200" }, { "at": "2026-10-29T17:11:21Z", "url": "https://en.wikipedia.org/w/index.php?search=%22Metawatch%22&title=Special:Search&profile=advanced&fulltext=1&ns0=1", "http": "429" }, { "at": "2026-10-29T17:11:31Z", "url": "https://en.wikipedia.org/w/index.php?title=MetaWatch&action=raw&redirect=no", "http": "200" }, { "at": "2026-10-29T17:12:13Z", "url": "https://en.wikipedia.org/w/index.php?search=%22Metawatch%22&title=Special:Search&profile=advanced&fulltext=1&ns0=1", "http": "200" } ], "text": [ "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B7.txt" ], "text_sha256": "8d4106a54ed94b0845e0e6846ba3a359e3ba7b1f431a6d8856e142ec4fa03c25", "note": "Two requests answered 429 and were retried after a pause (the bare 'Metawatch' search and the operator's raw wikitext); the log keeps every response. B7.txt is a summary of the HTTP codes and notices, written from the saved responses." }, "card_title": null, "card_snippet": null, "card_note": "not surfaced by T", "names_operator": "no (the responses are 404s and a search page)", "names_archive": "no", "note": "No article for the entity: IPTC_Metawatch and Metawatch return HTTP 404 (raw and rendered), neither is a redirect, and the full-text search for '\"Metawatch\" IPTC' finds nothing. The bare search finds 'MetaWatch', a discontinued smartwatch brand (Meta Watch Ltd.), a homonym (raw wikitext saved as B7-MetaWatch-homonym.wiki); it is recorded under homonyms and not ledgered as a claim on the entity." }, { "id": "B8", "origin": "wikipedia", "role": "Wikipedia: the operator", "card": "Wikipedia — International Press Telecommunications Council", "url": "https://en.wikipedia.org/wiki/International_Press_Telecommunications_Council", "kind": "Wikipedia article (the operator's; Metawatch not named)", "surfaced_by_T": [], "files": { "B8.wiki": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B8.wiki", "sha256": "c9111b64b71f2a9c3035b8324ec6ae04b93eb421281cb484167e1e51e2cd440e" }, "B8.html": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B8.html", "sha256": "65a1179436e9871107011ec6a2aec35ead1726f33a2815233c5764cc6df253ec" }, "B8.txt": { "path": "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B8.txt", "sha256": "cb0c0b3b92c372759ec4f71ae267abe0b941a3d06c9cee0dcae9857e42848ff3" } }, "fetched": { "log": [ { "at": "2026-10-29T17:11:38Z", "url": "https://en.wikipedia.org/w/index.php?title=International_Press_Telecommunications_Council&action=raw", "http": "429" }, { "at": "2026-10-29T17:11:47Z", "url": "https://en.wikipedia.org/wiki/International_Press_Telecommunications_Council", "http": "200" }, { "at": "2026-10-29T17:12:28Z", "url": "https://en.wikipedia.org/w/index.php?title=International_Press_Telecommunications_Council&action=raw", "http": "200" } ], "text": [ "datasets/negative-of-the-negative/v2/intake/iptc-metawatch-20261029/B8.txt" ], "text_sha256": "cb0c0b3b92c372759ec4f71ae267abe0b941a3d06c9cee0dcae9857e42848ff3", "note": "B8.txt is the rendered article body (mw-parser-output), scripts, styles and reference markers removed." }, "card_title": null, "card_snippet": null, "card_note": "not surfaced by T", "names_operator": "yes ('International Press Telecommunications Council', 'IPTC')", "names_archive": "no", "note": "The operator's article exists (HTTP 200); neither its wikitext nor its rendered page contains the string 'Metawatch'. Admitted as the encyclopedia's account of the operator, as the data-provenance-explorer row admitted the operator's title." } ] } }