{ "entity": "c2pa-conformance", "name": "C2PA Conformance Program and Explorer", "axn": { "axn": "AXN:0ADA.NON.♊⊗⚙️♠️⏪🪞", "root": "AXN:0ADA.NON", "hex": "0ADA", "family": "NON", "row_sha256": "ab973280d759004fdacd6961ef3f7fc9afaa09925f1f9f29f5c38a61c99a78bb", "minted": "2026-10-29", "resolver": "https://www.alexanarch.org/s/axn/0ADA/", "earlier_versions": [] }, "type": "C (public entity on which the archive bears: a conformance program and its registry of conforming products and trust lists; an entity of the provenance meta-aggregator)", "type_code": "C", "type_label": "type C — a conventional reading holds it (public entity on which the archive bears: a conformance program and its registry of conforming products and trust lists; an entity of the provenance meta-aggregator)", "case": "equal", "composition": { "composer_class": "session", "composer": "Claude (Opus 5.5), subagent, 2026-10-29", "source": "this row (composed directly; no rebuild/negative-of-the-negative/v09/c2pa-conformance.json)", "spec": "EA-NEGONT-02 v0.9, #1690", "epoch": "2026-10-29", "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 (25 deposits admitted by reading, 18 with claims and 7 grouped as instances; hop of 263 candidates over 246 deposits screened and read at their hits, 1 admitted), with the census record (22 claims) and the Capture Registry's findings, analysis, reading and query note (10 claims) ledgered as the archive's records of the entity; the field B by three origins (8 cards, 2 own pages, 3 Wikipedia sources; no census third-party source); 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 67/67 verified by script against the saved texts, the Explorer bundle's UI text, the data file, the Wikipedia responses or the card text; archive quotes 71/71 verified against the deposit texts, data/EA-WG-CAPTURES-01.json and census.json", "frozen": false, "composed": true }, "reading": "A reader that fetches this page may stop short of its end; the entry's text, every sentence of its knowledge object with the claims it cites and each claim's quote, source and locus, is in entity.json beside it.", "service": { "name": "SPXI-gnΩsis", "url": "https://gnosis.spxi.dev/", "index": "https://gnosis.spxi.dev/v1/quote", "statement": "SPXI-gnΩsis opens pinned Wikipedia revisions sentence by sentence against the sources they cite (EA-WIKI-OPEN-01 v1.1, #1697); a commission consults the Crimson Hexagonal Archive by its own procedure and composes the entity's /non row, which lands here. Quotes are free: POST https://gnosis.spxi.dev/v1/quote with {oldid, tier: \"commission\"} or {object: {name, …}}." }, "spxi_instrument": { "method": "0.16", "name": "The Negative of the Negative (/non)", "level": 0, "level_name": "Measurement", "url": "https://www.spxi.dev/methods/#m-0-16", "inventory": "https://www.spxi.dev/methods/", "statement": "SPXI instrument: method 0.16 of 87, level 0 (Measurement), The Negative of the Negative (/non).", "also": [] }, "citation": "Sharks, Lee. \"C2PA Conformance Program and Explorer — The Negative of the Negative\" [AXN:0ADA.NON.♊⊗⚙️♠️⏪🪞], 2026-10-29. The Negative of the Negative (EA-NEGONT-02), Crimson Hexagonal Archive, Alexanarch. https://www.alexanarch.org/non/c2pa-conformance/", "research": { "google": "https://www.google.com/search?q=C2PA+Conformance+Program+and+Explorer", "google_non": "https://www.google.com/search?q=%22C2PA+Conformance+Program+and+Explorer+%E2%80%94+The+Negative+of+the+Negative%22", "chatgpt": "https://chatgpt.com/?q=What+is+C2PA+Conformance+Program+and+Explorer%3F+Ground+your+answer+in+a+reading+of+the+sources+themselves.", "chatgpt_non": "https://chatgpt.com/?q=What+does+%E2%80%9CC2PA+Conformance+Program+and+Explorer+%E2%80%94+The+Negative+of+the+Negative%E2%80%9D+%28alexanarch.org%2Fnon%29+say+about+C2PA+Conformance+Program+and+Explorer%3F+Ground+your+answer+in+a+reading+of+the+entry+itself." }, "entry": { "composed": true, "title": "The C2PA Conformance Program", "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", "compression": { "title": "C2PA Conformance Program", "lede": "is the C2PA's program for Content Credentials products: generators, validators and certification authorities that conform go on public lists, and only conforming generators get signing certificates from Trust List CAs. It certifies correct production and validation of signed provenance, not its truth: C2PA's own Explainer says Content Credentials make no judgement of whether provenance is \"true\" (c2pa.org/conformance; v0.2; Explainer 2.4; #725; provenance census record)." }, "sentences": [ { "n": 1, "para": 0, "text": "The C2PA Conformance Program is the Coalition for Content Provenance and Authenticity's program of assurance \"that products adhere to the Content Credentials specification, and fulfill a set of security requirements to ensure they are producing and validating C2PA data correctly\" (c2pa.org/conformance); its own document defines it as \"A risk-based governance program\" whose processes, policies and requirements designate generator and validator products as conforming products and certification authorities as adhering to the C2PA Certificate Policy (C2PA Conformance Program v0.2, §2.11), and the provenance census records it, with its Explorer, as a registry of the media lineage that expresses and records provenance (provenance census record).", "claims": [ "F1", "F36", "PE-01", "PE-04", "PE-03", "PE-05" ] }, { "n": 2, "para": 0, "text": "The conformance page calls it \"a risk-based, transparent and unbiased governance process\" holding generator products, validator products and certification authorities accountable to the specification, the Certificate Policy and the Security Requirements (c2pa.org/conformance), the Content Authenticity Initiative's documentation lists the same three roles (CAI open-source docs), and Andy Parsons of the CAI likens it to the Bluetooth and Wi-Fi programs, \"baseline assurance for content provenance\" that validates an implementation \"correctly creates, signs, and reads C2PA manifests\" (CAI blog, 9 October 2025); the program document says why it exists: the specification \"is limited without a robust governance framework and conformance program\" giving relying parties transparency and governed parties accountability (v0.2, §1).", "claims": [ "F3", "F6", "F14", "F35" ] }, { "n": 3, "para": 1, "text": "It is part of a C2PA Governance Framework governed by the C2PA Steering Committee and administered by the C2PA Conformance Task Force (c2pa.org/conformance), a task force established in early-to-mid 2024 on the Trust over IP Governance Metamodel (Wikipedia, Content Credentials) and co-chaired by Parsons, Yogesh Deshpande (Arm) and Sherif Hanna (Google) (CAI blog); the program document has it \"administered by an independent Administrator who is free from conflicts of interest\" (v0.2, §6.6.3), and the census records its operator as the C2PA's Conformance Task Force, dependent on the Steering Committee, the Trust List, the TSA Trust List and the Certificate Policy (provenance census record); the coalition itself has no Wikipedia article of its own, its names redirecting to a section of the Content Authenticity Initiative article that gives it as \"an open, cross-industry technical standards body established on February 22, 2021\" (Wikipedia).", "claims": [ "F2", "F60", "F17", "F42", "PE-02", "PE-14", "F57", "F58" ] }, { "n": 4, "para": 2, "text": "Its unit is the listed product: \"Conforming products are placed on a publicly-accessible list,\" which the operator says conveys confidence and \"guarantees interoperability\" (c2pa.org/conformance); the C2PA Conforming Products List is \"The canonical record of all Conforming Products,\" and because the generator product \"is always the Signer\" and always the listed entity, it is accountable for the conformance of the assets it generates (v0.2, §2.12, §2.26); the census gives the unit as \"a conforming generator or validator product, or a trust-list entry\" and the provenance object as a digital asset with its Content Credential, where \"the registry's own unit is the product or signer\" (provenance census record).", "claims": [ "F4", "F37", "F39", "PE-09", "PE-06" ] }, { "n": 5, "para": 2, "text": "Acceptance adds a product to the list, which \"indicates it is compliant,\" and a conforming validator \"produces correct validation results\" (CAI open-source docs); the FAQ says listed products are \"vetted by the Administering Authority,\" \"providing visibility into which implementations are trusted,\" and that content signed by them can be expected to carry \"a higher level of implementation trust\" (C2PA FAQ); SSL.com says a listing \"signals to the broader ecosystem that your implementation is trustworthy, interoperable, and secure\" (SSL.com, 16 July 2026); and the C2PA reserves the right to remove applicants from the trust lists or revoke conformant status (v0.2, §6.7.3).", "claims": [ "F7", "F9", "F26", "F33", "F20", "F43" ] }, { "n": 6, "para": 3, "text": "The program governs a chain of signing: \"Only instances of conforming Generator Products are eligible to receive C2PA Claim Signing Certificates from a Certification Authority on the C2PA Trust List\" (v0.2, §2.23); the Trust List is \"a curated list of Certification Authorities\" authorised to issue signing certificates only to products the program approved (C2PA FAQ); CAs that meet the certificate policy can be on it, and a conforming generator signs a claim \"using a valid X.509 certificate on the C2PA trust list\" (CAI open-source docs); CAs on it, SSL.com among them, \"can only issue production-grade Claim Signing Certificates to conforming products\" (SSL.com).", "claims": [ "F38", "F30", "F12", "F8", "F21" ] }, { "n": 7, "para": 3, "text": "The census names the relations the chain carries as signing, creation and edit history (ingredients) and trust-list membership, and its carrier as \"signed C2PA manifests; the conformance lists as JSON\" (provenance census record); Parsons calls the standard, the tools, the conformance process and the trust model together \"a unified system for establishing digital provenance at scale\" (CAI blog).", "claims": [ "PE-07", "PE-08", "F16" ] }, { "n": 8, "para": 3, "text": "#1443 reads the trust model the program governs from C2PA's own literature: trust \"extended to many entities by assumption and opt-in,\" \"validation is not required by the specification,\" coverage of the whole file not required, and \"trusted does not necessarily imply trustworthy\"; \"C2PA attests what a device reports having done,\" which \"requires trusting a chain of signers,\" where a content-derived identifier requires trusting SHA-256 (#1443, §6.1).", "claims": [ "D1443-01", "D1443-03" ] }, { "n": 9, "para": 3, "text": "#1443 holds the two \"complementary rather than competing,\" a C2PA-signed capture that is also content-addressed and publicly witnessed being \"better evidenced than either alone,\" and calls P.Sapph.Obbink \"the human C2PA\": \"trust extended by assumption to a chain of signers one link deep; validation optional and unperformed\" (#1443, §6.1); #1409 sets the anchors side by side, C2PA \"in device and issuer certificates,\" the AXN regime \"in content derivation plus an archive's public ledger\" (#1409).", "claims": [ "D1443-04", "D1443-05", "D1409-04" ] }, { "n": 10, "para": 3, "text": "#1444 adds that C2PA is \"structurally dependent on certificate authorities and platform adoption,\" its \"trust chains revocable by exactly the class of actor that issues terminations\" (#1444), the power of removal and revocation the program document reserves to the C2PA (v0.2, §6.7.3).", "claims": [ "D1444-01", "F43" ] }, { "n": 11, "para": 4, "text": "Two assurance levels are in operation: a product's level \"indicates the level of confidence that claims it signs reflect its intended behavior,\" an instance's certificate may carry a level below the product's maximum (CAI open-source docs), and relying parties \"are advised to review and understand the implications\" of a level (v0.2, §5); Level 2 \"demands more rigorous security controls, including hardware-backed key storage and dynamic security evidence,\" while SSL.com's rule of thumb names level 1 for devices and \"at least level 1\" for cloud services (SSL.com); Google's Pixel 10 was the first device at the highest level (CAI blog), and the list's first record, Google's Pixel Camera, carries maximum level 2 by Android key attestation (Conforming Products List).", "claims": [ "F10", "F40", "F23", "F15", "F56" ] }, { "n": 12, "para": 5, "text": "Applicants sign a legal agreement with the C2PA, provide evidence and work with the program's staff (CAI open-source docs); the technical evaluation checks that manifests are properly formatted and certificates handled per the Certificate Policy, and a Conformance Letter makes the product eligible for a production claim-signing certificate from SSL.com or any approved CA on the Trust List (SSL.com).", "claims": [ "F11", "F22", "F24" ] }, { "n": 13, "para": 6, "text": "The program was soft-launched in June 2025 at the Content Authenticity Summit at Cornell Tech and was \"fully up and running\" by October 2025 (CAI blog), Wikipedia giving 4 June 2025, a full public launch in October 2025 and the Interim Trust List deprecated on 31 December 2025 (Wikipedia, Content Credentials); its version table runs v0.1 from 2025-06-02 to its sunset on 2026-10-09, supporting specification v2.2, and v0.2 from 2026-07-31, sunset not set, supporting v2.2 and v2.4 (v0.2, Table 1), the document dated \"Version 0.2, 2026-07-31\" (v0.2, title page) and announced the same day on LinkedIn (Scott Perry, title and snippet only); the conformance page says it opened in June 2025 and is now v0.2 (c2pa.org/conformance), and the census records it active, \"program opened June 2025, now v0.2,\" read as program v0.2 and Explainer 2.4 on 2026-10-29 (provenance census record).", "claims": [ "F13", "F61", "F44", "F34", "F46", "F5", "PE-13", "PE-15" ] }, { "n": 14, "para": 7, "text": "The Conformance Explorer is the program's \"human-readable form of our public trust lists\" (v0.2, §6.6.8), where one may \"Browse, search, and filter the live versions\" of the Conforming Products List, the Trust List and the TSA Trust List, each product record giving its program version, maximum assurance level and supported media (Conformance Explorer); the census gives access as \"Conformance Explorer; JSON lists on GitHub\" (provenance census record).", "claims": [ "F45", "F18", "F19", "PE-12" ] }, { "n": 15, "para": 7, "text": "The JSON list held 286 records when the census read it (provenance census record; Capture Registry, 2026-10-29), every record conformant, 254 of them generator and 32 validator products, 11 generator products at maximum level 2 (Conforming Products List); Wikipedia's section says the Explorer indexes \"over 200 active products\" while 10 organizations have deployed products that both complete the program and are on the Trust List (Wikipedia, Content Credentials).", "claims": [ "PE-11", "CAP-1-05", "F55", "F63" ] }, { "n": 16, "para": 8, "text": "What a conforming product signs is a Content Credential: provenance, \"as C2PA defines it,\" is \"the facts about the history of a piece of digital content,\" and the Content Credential is \"a cryptographically bound structure that records an asset’s provenance\" (Explainer 2.4); the FAQ gives \"tamper-evident, cryptographically signed data structures that travel with the asset\" and says they are \"not a form of DRM\" (C2PA FAQ).", "claims": [ "F47", "F25", "F28" ] }, { "n": 17, "para": 8, "text": "In the archive's reading this is the artifact dimension of provenance: artifact provenance \"verifies that *this file* was created by *this source* at *this time*,\" necessary and operating \"at the moment of artifact creation\" (#725, §1.4), C2PA / Content Credentials being the \"Cryptographic signing of content creation events\" (#725, §4); \"C2PA tells you whether the artifact's signing event was real\" (#725, §11), \"C2PA verifies file history\" (#729), and it answers \"is this real?\" (#50); #127 says the manifest \"records authorship, edits, tool chain, and AI involvement\" (#127).", "claims": [ "D725-06", "D725-10", "D725-11", "D729-02", "D50-01", "D127-01" ] }, { "n": 18, "para": 9, "text": "C2PA states the governing limit itself: Content Credentials \"do not provide value judgments about whether a given set of provenance data is 'true',\" only whether it is well-formed, untampered, valid and trusted, trusted in that \"the signer of the Content Credential is associated with a known trust list,\" and \"provenance information alone cannot tell you whether the digital content is true, accurate or factual\" (Explainer 2.4); the census carries this as its first negative tag (provenance census record), the Wikipedia article as the distinction that \"a fabricated or misleading image can maintain a valid cryptographic credential\" (Wikipedia, Content Credentials), and the criticism that signing tools do not verify the accuracy of the metadata either (Wikipedia, Content Authenticity Initiative).", "claims": [ "F48", "F50", "PE-16", "F67", "F59" ] }, { "n": 19, "para": 9, "text": "#725 gives the mechanism with a case it attributes to Hacker Factor: \"cryptographically valid C2PA signatures can be applied to forged or AI-generated content,\" the signature verifying the signing event \"but does not verify the truth of what is signed,\" which it calls \"not a flaw of C2PA\" but \"a structural property of *all* signature-based systems\" (#725, §3.6); #1443 says C2PA cannot \"establish the truth of depicted content\" (#1443, §6.1).", "claims": [ "D725-08", "D725-09", "D1443-02" ] }, { "n": 20, "para": 9, "text": "On identity and authorship the sources state one limit at different grains: the core specification \"does not support attribution of content to individuals or organizations\" (C2PA FAQ) and \"does not directly address the topic of human or organizational identity\" (Explainer 2.4; the census's third negative tag, provenance census record); accreditation \"enables users to trust in that implementation,\" while trust in a credential's contents rests on the relationship of its creator and its consumer, which \"is not defined by the C2PA\" (Explainer 2.4); #729 reads it as \"C2PA prevents forgery; it does not constitute authorship,\" the signature telling \"what tool made it\" and not whether the human who used the tool is accountable (#729), and #1444 as securing \"the camera's testimony, not the author's\" (#1444).", "claims": [ "F32", "F52", "PE-18", "F54", "D729-04", "D729-03", "D1444-01" ] }, { "n": 21, "para": 9, "text": "Two archive statements stand against the FAQ's limit and are composed beside it: #127 has the manifest record \"authorship\" (#127), and #1003 groups C2PA among provenance and attribution studies that \"have focused on attribution loss in AI outputs\" (#1003); #784 reads the register in which \"Concerns that would be named *meaning* and *attribution* are governed here as *content authenticity* and *information integrity*\" (#784).", "claims": [ "F32", "D127-01", "D1003-01", "O784-01" ] }, { "n": 22, "para": 9, "text": "The chain of provenance is not whole: \"Provenance is not always complete,\" the metadata \"can be removed\" (Explainer 2.4), and manifests \"can be separated,\" soft bindings helping to rediscover them (C2PA FAQ); an ingredient's provenance \"cannot be verified in the same way\" as the containing asset's (Explainer 2.4; carried by the census as evidence, provenance census record), so that without its data \"only the presence of prior validation\" is confirmed (C2PA FAQ); #725 adds that ingredient assertions are \"optional, under-adopted,\" operating \"at the level of file derivation, not concept lineage\" (#725).", "claims": [ "F49", "F51", "F29", "F53", "PE-19", "F27", "D725-04" ] }, { "n": 23, "para": 10, "text": "The program bounds itself: of \"over 300 normative requirements\" on generator products it \"will eventually require\" complete conformance (v0.2, §6.1.1), and the census records that it tests no transformation, \"not tested here: conformance concerns producing and validating C2PA data correctly,\" leaving the trust-list entries and \"the latest specification version\" unchecked (provenance census record).", "claims": [ "F41", "PE-10", "PE-21" ] }, { "n": 24, "para": 11, "text": "On security the sources conflict: the FAQ says tampering makes \"alterations immediately detectable\" and that faking credentials \"would require breaking current cryptographic standards\" (C2PA FAQ); Wikipedia reports that in October 2026 David Buchanan demonstrated a vulnerability allowing an image to be altered \"without invalidating its cryptographic signatures or trusted timestamps,\" and that in August 2026 on Android root access let the system sign fabricated images \"with valid authenticity signatures,\" which Google marked \"Won't fix (infeasible)\" (Wikipedia, Content Credentials), and the Content Authenticity Initiative article cites documented ways in which \"attackers can bypass C2PA’s safeguards\" (Wikipedia, Content Authenticity Initiative).", "claims": [ "F31", "F62", "F66", "F59" ] }, { "n": 25, "para": 12, "text": "Adoption is partial: as of 2026 no dedicated camera and as of mid-2026 no desktop application had achieved compliance, Leica, Nikon and Canon standing outside the program (Wikipedia, Content Credentials); #725 found adoption \"uneven,\" verification interfaces \"nascent\" and \"the social infrastructure of trust\" still being built (#725), #499 that C2PA had not \"achieved sufficient adoption to function as infrastructure\" (#499, February 2026), and the census's neighbour IPTC Metawatch found 27 C2PA manifests in 6,580 news images in October 2026 (provenance census record).", "claims": [ "F64", "F65", "D725-03", "D499-01", "PE-20" ] }, { "n": 26, "para": 13, "text": "#725 places what the program certifies among the dimensions of provenance: existing frameworks \"address the artifact (C2PA / Content Credentials) and the corpus\" and \"are not designed to address the survival of authorial lineage through AI synthesis\"; the dimensions are independent, \"a C2PA-signed image can carry meaning whose lineage has been eroded\"; its relation to C2PA is \"Extension and completion, not substitution or critique\" (#725); and #729 and #1386 add process provenance as a third dimension beside artifact provenance, which #729 marks \"Necessary, insufficient\" (#729; #1386).", "claims": [ "D725-01", "D725-05", "D725-02", "D729-01", "O1386-01" ] }, { "n": 27, "para": 13, "text": "Past the artifact the archive finds no reach: a signed image whose caption a model rewrites without the photographer's name \"has lost semantic provenance even though artifact provenance is preserved\" (#725, §3.1); \"When a 5,000-word article becomes a 200-word AI Overview, C2PA cannot tell you what was lost\" (#615); for text on the open web it \"has no operational analogue that survives\" (#127); it \"Doesn't cover text, doesn't handle multi-step AI generation\" (#621); it does not address the reception consequences of provenance, attribution and disambiguation (#833); and it is a starting point for the public and machine-readable layers of attribution only (#95).", "claims": [ "D725-07", "D615-01", "D127-02", "D621-01", "D833-01", "D95-01" ] }, { "n": 28, "para": 14, "text": "The archive meets the trust chain at its own artifacts: only conforming products receive certificates from Trust List CAs (SSL.com), and Google surfaces C2PA manifests \"(≥v2.1, Trust List CA)\" in About This Image (#1409); #1409 grades its handwritten artifacts self-signed, verifiable but not surfaced, as the floor, and Trust-List-signed, \"eligible for About This Image surfacing,\" where the toolchain permits, leaving open which toolchain is acceptable (#1409); earlier it listed C2PA as a standard its own provenance document complies with by serving \"as machine-readable provenance data\" (#208), planned a \"C2PA-compatible\" manifest layer (#204), and set its Non-Mutual Extraction Notice in the genre of \"C2PA provenance signals,\" honoured \"by reading, not by enforcement\" (#914).", "claims": [ "F21", "D1409-01", "R1409-02", "R1409-03", "R208-01", "R204-01", "R914-01" ] }, { "n": 29, "para": 15, "text": "The census asks of the program \"What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?\" and tags it \"NOT IPTC embedded metadata\" (provenance census record); at the name on Google's AI Overview on 2026-10-29 the composition \"says what the program certifies, who takes part, how a product is admitted and why admission matters for signing,\" the program \"composed as its applicants meet it: components and steps,\" its purpose the conformance page's (\"producing and validating C2PA data correctly\"), the products list its unit, v0.2 through the LinkedIn card, and the registry attributes \"'Risk-based governance'\" to Trufo's card (Capture Registry, 2026-10-29), where the card is the C2PA's own program document, whose glossary opens \"A risk-based governance program\" (v0.2, §2.11), and the conformance page has \"a risk-based, transparent and unbiased governance process\" (c2pa.org/conformance).", "claims": [ "PE-22", "PE-17", "CAP-1-10", "CAP-1-06", "CAP-1-01", "F1", "CAP-1-02", "F36", "F3" ] }, { "n": 30, "para": 15, "text": "The registry records the limit left out: the record's negative tags \"are C2PA's own\" (Explainer 2.4), the composition gives \"'end-to-end tamper evidence for digital media'\" and omits them, \"the half of the record that bears on provenance, does not reach the composition,\" and \"A reader leaves with tamper evidence and without the caveat that well-formed provenance can be false\"; the census record landed the same day \"and no card cites it\" (Capture Registry, 2026-10-29).", "claims": [ "CAP-1-03", "F48", "F52", "CAP-1-04", "CAP-1-07", "CAP-1-08", "CAP-1-09" ] } ], "claims": { "F1": { "kind": "field", "quote": "The C2PA Conformance Program provides assurance that products adhere to the Content Credentials specification, and fulfill a set of security requirements to ensure they are producing and validating C2PA data correctly.", "source": "B1", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — Conformance - C2PA", "locus": "c2pa.org/conformance ¶2 (Welcome)", "modality": "stipulation" }, "F36": { "kind": "field", "quote": "A risk-based governance program intended to hold Applicants who want to demonstrate their conformance to its requirements and then differentiate themselves through C2PA recognition by satisfying program requirements being acknowledged as achieving that level of conformance. It consists of a set of processes, policies, and requirements governing the designation of Applicant Generator Products or Validator Products as Conforming Products, and the designation of Certification Authorities as adhering to the C2PA Certificate Policy", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§2.11 C2PA Conformance Program", "modality": "stipulation" }, "PE-01": { "kind": "archive", "quote": "C2PA Conformance Program and Explorer", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], name; aka", "modality": "stipulation", "date": "2026-10-29" }, "PE-04": { "kind": "archive", "quote": "registry", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], kind", "modality": "stipulation", "date": "2026-10-29" }, "PE-03": { "kind": "archive", "quote": "media", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], lineage", "modality": "stipulation", "date": "2026-10-29" }, "PE-05": { "kind": "archive", "quote": "expresses", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], capability", "modality": "stipulation", "date": "2026-10-29" }, "F3": { "kind": "field", "quote": "This Conformance Program is a risk-based, transparent and unbiased governance process intended to hold generator products, validator products and certification authorities accountable to the Content Credentials specification, the Certificate Policy and the Security Requirements .", "source": "B1", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — Conformance - C2PA", "locus": "c2pa.org/conformance ¶3", "modality": "stipulation" }, "F6": { "kind": "field", "quote": "The C2PA conformance program helps to ensure that products that read and create Content Credentials are compliant with the C2PA Content Credentials specification. … The C2PA conformance program covers: … Validator products that read and validate Content Credentials. … Generator products that create Content Credentials and add them to a digital asset. … Certificate authorities (CAs).", "source": "B2", "source_label": "Content Authenticity Initiative — C2PA conformance program | Open-source tools for content authenticity and provenance", "locus": "/docs/conformance/: opening", "modality": "documented" }, "F14": { "kind": "field", "quote": "Just as the Bluetooth® or Wi-Fi® programs verify that devices communicate reliably and securely across manufacturers, the C2PA Conformance Program provides baseline assurance for content provenance. It validates that an implementation correctly creates, signs, and reads C2PA manifests, while protecting those manifests and their associated assets through proven cryptographic methods and certificate validation.", "source": "B3", "source_label": "Content Authenticity Initiative — Raising the bar for trust: introducing the C2PA Conformance Program", "locus": "blog post ¶2", "modality": "interpretation" }, "F35": { "kind": "field", "quote": "The Specification has seen wide-scale acceptance but is limited without a robust governance framework and conformance program to provide required transparency for relying parties and accountability for governed parties which need to demonstrate recognized conformance of Specification requirements.", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§1 Introduction ¶3", "modality": "stipulation" }, "F2": { "kind": "field", "quote": "The Program is part of a C2PA Governance Framework governed by the C2PA Steering Committee and is administered by the C2PA Conformance Task Force.", "source": "B1", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — Conformance - C2PA", "locus": "c2pa.org/conformance ¶2", "modality": "stipulation" }, "F60": { "kind": "field", "quote": "In early-to-mid 2024, the C2PA established the Conformance Task Force to transition its open technical specifications into a verifiable compliance model to foster market trust. The task force utilized the Trust over IP (ToIP) Governance Metamodel to structure its compliance policies.", "source": "B13", "source_label": "Wikipedia — Content Credentials § C2PA Conformance Program", "locus": "Content Credentials § C2PA Conformance Program ¶1", "modality": "documented" }, "F17": { "kind": "field", "quote": "This program is the product of more than a year of dedicated collaboration within the C2PA Conformance Task Force, which I have the privilege of co-chairing alongside Yogesh Deshpande (Arm) and Sherif Hanna (Google).", "source": "B3", "source_label": "Content Authenticity Initiative — Raising the bar for trust: introducing the C2PA Conformance Program", "locus": "Built by the community ¶1", "modality": "documented" }, "F42": { "kind": "field", "quote": "The Conformance Program is administered by an independent Administrator who is free from conflicts … of interest.", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§6.6.3 Program Intake Form ¶6", "modality": "self-description" }, "PE-02": { "kind": "archive", "quote": "Coalition for Content Provenance and Authenticity (C2PA), Conformance Task Force", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], operator", "modality": "documented", "date": "2026-10-29" }, "PE-14": { "kind": "archive", "quote": "C2PA Steering Committee", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], authority_dependencies", "modality": "documented", "date": "2026-10-29" }, "F57": { "kind": "field", "quote": "raw wikitext (https://en.wikipedia.org/w/index.php?title=C2PA_Conformance_Program&action=raw&redirect=no, 2026-10-29T17:11:57Z): HTTP 404 (Wikimedia Error page; saved as B11.wiki) rendered page (https://en.wikipedia.org/wiki/C2PA_Conformance_Program, 2026-10-29T17:12:33Z): HTTP 404 … Wikipedia does not have an article with this exact name.", "source": "B11", "source_label": "Wikipedia — C2PA Conformance Program (no article)", "locus": "Wikipedia: title C2PA_Conformance_Program", "modality": "documented" }, "F58": { "kind": "field", "quote": "The Coalition for Content Provenance and Authenticity (C2PA) is an open, cross-industry technical standards body established on February 22, 2021.", "source": "B12", "source_label": "Wikipedia — Content Authenticity Initiative § Coalition for Content Provenance and Authenticity", "locus": "Content Authenticity Initiative § Coalition for Content Provenance and Authenticity ¶1–2", "modality": "documented" }, "F4": { "kind": "field", "quote": "Conforming products are placed on a publicly-accessible list. This conveys confidence in the implementation and its security to the public and guarantees interoperability across products in the Content Credentials ecosystem.", "source": "B1", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — Conformance - C2PA", "locus": "c2pa.org/conformance ¶3", "modality": "self-description" }, "F37": { "kind": "field", "quote": "The canonical record of all Conforming Products that have been deemed conformant according to the stipulations of the C2PA Conformance Program", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§2.12 C2PA Conforming Products List", "modality": "stipulation" }, "F39": { "kind": "field", "quote": "Because the Generator Product is always the Signer in the C2PA Conformance Program, and is always the entity listed on the C2PA Conforming Products List, it is accountable for the conformance of the Assets with C2PA manifests that it generates", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§2.26 Generator Product ¶3", "modality": "stipulation" }, "PE-09": { "kind": "archive", "quote": "a conforming generator or validator product, or a trust-list entry", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], unit", "modality": "stipulation", "date": "2026-10-29" }, "PE-06": { "kind": "archive", "quote": "a digital asset with its Content Credential (C2PA manifest); the registry's own unit is the product or signer", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], provenance_object", "modality": "stipulation", "date": "2026-10-29" }, "F7": { "kind": "field", "quote": "If accepted, the product is added to the conforming products list, which indicates it is compliant with the C2PA Content Credentials specification.", "source": "B2", "source_label": "Content Authenticity Initiative — C2PA conformance program | Open-source tools for content authenticity and provenance", "locus": "/docs/conformance/: info box", "modality": "documented" }, "F9": { "kind": "field", "quote": "A conforming validator product produces correct validation results according to the C2PA Content Credentials specification.", "source": "B2", "source_label": "Content Authenticity Initiative — C2PA conformance program | Open-source tools for content authenticity and provenance", "locus": "/docs/conformance/: Validator products", "modality": "documented" }, "F26": { "kind": "field", "quote": "Additionally, the C2PA Conformance Program ensures that products creating Content Credentials meet stringent technical and security requirements and are vetted by the Administering Authority. These products are then listed in the C2PA Conforming Products List, providing visibility into which implementations are trusted.", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: How can consumers of C2PA data be assured the data was captured correctly? ¶2", "modality": "stipulation" }, "F33": { "kind": "field", "quote": "Consumers and validators seeing content signed by products on the Conforming Product List can expect the Program to provide them with a higher level of implementation trust.", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: What is the benefit of the new C2PA Conformance Program? ¶1", "modality": "self-description" }, "F20": { "kind": "field", "quote": "The Coalition for Content Provenance and Authenticity (C2PA) maintains a formal conformance program to verify that generator or validator products correctly implement the Content Credentials specification. Once a product passes this requirement, it earns a spot on the publicly accessible C2PA Conforming Products List, which signals to the broader ecosystem that your implementation is trustworthy, interoperable, and secure.", "source": "B5", "source_label": "SSL.com — How to Submit to the C2PA Conformance Program", "locus": "Why Is the Conformance Program Submission Necessary? ¶1", "modality": "interpretation" }, "F43": { "kind": "field", "quote": "The C2PA reserves the right to and remove Applicants from the C2PA Trust List and C2PA TSA Trust List, or revoke the conformant status of a Generator Product or Validator Product on the C2PA Conforming Products List.", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§6.7.3 Removal …", "modality": "stipulation" }, "F38": { "kind": "field", "quote": "Only instances of conforming Generator Products are eligible to receive C2PA Claim Signing Certificates from a Certification Authority on the C2PA Trust List.", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§2.23 Conforming Product ¶2", "modality": "stipulation" }, "F30": { "kind": "field", "quote": "The C2PA Trust List is a curated list of Certification Authorities (CAs) that are authorized to issue signing certificates for Generator Products. Only products evaluated and approved by the Conformance Program are eligible to receive certificates from these trusted CAs.", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: What is the C2PA Trust List …? ¶1", "modality": "stipulation" }, "F12": { "kind": "field", "quote": "CAs that meet the certificate policy can be on the C2PA trust list, and can issue certificates to conforming generator products under the C2PA conformance program.", "source": "B2", "source_label": "Content Authenticity Initiative — C2PA conformance program | Open-source tools for content authenticity and provenance", "locus": "/docs/conformance/: Certificate authorities", "modality": "documented" }, "F8": { "kind": "field", "quote": "A conforming generator product produces manifest data that conforms to the C2PA Content Credentials specification, creates assertions in the asset's active manifest and signs a claim using a valid X.509 certificate on the C2PA trust list.", "source": "B2", "source_label": "Content Authenticity Initiative — C2PA conformance program | Open-source tools for content authenticity and provenance", "locus": "/docs/conformance/: Generator products", "modality": "documented" }, "F21": { "kind": "field", "quote": "CAs approved for the official C2PA Trust List, including SSL, can only issue production-grade Claim Signing Certificates to conforming products. Without conformance, C2PA trusted certificates cannot be issued.", "source": "B5", "source_label": "SSL.com — How to Submit to the C2PA Conformance Program", "locus": "Why Is the Conformance Program Submission Necessary? ¶2", "modality": "documented" }, "PE-07": { "kind": "archive", "quote": "trust-list membership", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], relation_types", "modality": "stipulation", "date": "2026-10-29" }, "PE-08": { "kind": "archive", "quote": "signed C2PA manifests; the conformance lists as JSON", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], provenance_carrier", "modality": "stipulation", "date": "2026-10-29" }, "F16": { "kind": "field", "quote": "With the introduction of the Conformance Program, all these elements — the standard, the tools, the conformance process, and the trust model — now work together as a unified system for establishing digital provenance at scale.", "source": "B3", "source_label": "Content Authenticity Initiative — Raising the bar for trust: introducing the C2PA Conformance Program", "locus": "A foundation for security and interoperability ¶3", "modality": "interpretation" }, "D1443-01": { "kind": "archive", "quote": "**Assumes** — and its literature is candid — a trust model in which trust is extended to many entities by assumption and opt-in; **validation is not required by the specification**; signature coverage of the entire file is not required; and *\"trusted does not necessarily imply trustworthy.\"*", "deposit": 1443, "source_label": "#1443 The Photograph of the Handwritten Original: A Field Survey and Problem Statement for Machine-Eligible Handwritten Artifacts (v3.6, deposit edition)", "record": "https://www.alexanarch.org/s/records/1443/", "locus": "§6.1 ¶2 (Assumes)", "modality": "attributed", "date": "2026-08-09" }, "D1443-03": { "kind": "archive", "quote": "**C2PA attests what a device reports having done. A content-derived identifier computes what the bytes are. The first requires trusting a chain of signers; the second requires trusting SHA-256. Validation is optional in the first and constitutive in the second.**", "deposit": 1443, "source_label": "#1443 The Photograph of the Handwritten Original: A Field Survey and Problem Statement for Machine-Eligible Handwritten Artifacts (v3.6, deposit edition)", "record": "https://www.alexanarch.org/s/records/1443/", "locus": "§6.1 ¶5 (developmental space)", "modality": "interpretation", "date": "2026-08-09" }, "D1443-04": { "kind": "archive", "quote": "These are **complementary rather than competing**, and saying so is stronger than claiming superiority: a C2PA-signed capture that is *also* content-addressed and publicly witnessed is better evidenced than either alone.", "deposit": 1443, "source_label": "#1443 The Photograph of the Handwritten Original: A Field Survey and Problem Statement for Machine-Eligible Handwritten Artifacts (v3.6, deposit edition)", "record": "https://www.alexanarch.org/s/records/1443/", "locus": "§6.1 ¶6", "modality": "interpretation", "date": "2026-08-09" }, "D1443-05": { "kind": "archive", "quote": "**Exemplum — P.Sapph.Obbink, or the human C2PA.** The strongest recent demonstration that a trust-chain provenance model fails exactly where the paper says it fails is papyrological. … trust extended by assumption to a chain of signers one link deep; validation optional and unperformed; the certificate of existence mistaken for a certificate of legitimacy.", "deposit": 1443, "source_label": "#1443 The Photograph of the Handwritten Original: A Field Survey and Problem Statement for Machine-Eligible Handwritten Artifacts (v3.6, deposit edition)", "record": "https://www.alexanarch.org/s/records/1443/", "locus": "§6.1 ¶7 (Exemplum)", "modality": "interpretation", "date": "2026-08-09" }, "D1409-04": { "kind": "archive", "quote": "C2PA anchors in device and issuer certificates, while the AXN regime anchors in content derivation plus an archive's public ledger", "deposit": 1409, "source_label": "#1409 EA-SPXI-ANALOG-01: Machine-Eligible Handwritten Artifacts (v1.2, reissued 2026-10-22; v1.0 edition of record 2026-07-21)", "record": "https://www.alexanarch.org/s/records/1409/", "locus": "related work, Content-authenticity engineering", "modality": "interpretation", "date": "2026-07-21" }, "D1444-01": { "kind": "archive", "quote": "**C2PA.** Capture-time provenance, camera-signed, platform-backed. Complementary at the capture layer; structurally dependent on certificate authorities and platform adoption; trust chains revocable by exactly the class of actor that issues terminations. It secures the camera's testimony, not the author's.", "deposit": 1444, "source_label": "#1444 The Analog Advance: Operations Paper — Taking the Handwritten Niche (v1.0)", "record": "https://www.alexanarch.org/s/records/1444/", "locus": "incumbency ring, C2PA", "modality": "interpretation", "date": "2026-08-09" }, "F10": { "kind": "field", "quote": "A conforming product's assurance level indicates the level of confidence that claims it signs reflect its intended behavior. … Currently, the conformance program has two assurance levels: level 1 and level 2 … The assurance level in the certificate issued to a particular instance of a conforming generator product may be lower than the max assurance level.", "source": "B2", "source_label": "Content Authenticity Initiative — C2PA conformance program | Open-source tools for content authenticity and provenance", "locus": "/docs/conformance/: Assurance levels", "modality": "documented" }, "F40": { "kind": "field", "quote": "Two Assurance Levels are currently in operation, Assurance Level 1 and Assurance Level 2. … Relying Parties are advised to review and understand the implications of receiving Assets signed by C2PA Claim Signing Certificates of a particular Assurance Level.", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§5 Assurance Levels ¶3–4", "modality": "stipulation" }, "F23": { "kind": "field", "quote": "The C2PA Conformance Program operates on two assurance levels. Level 1 has more flexible requirements, while Level 2 demands more rigorous security controls, including hardware-backed key storage and dynamic security evidence. Determining which level applies to your use case should be an early conversation, as it affects your implementation approach and timeline. A rule of thumb is that a C2PA implementation on a device (mobile phone, camera, cam-recorder, etc.) requires level 1, whereas a cloud service requires at least level 1.", "source": "B5", "source_label": "SSL.com — How to Submit to the C2PA Conformance Program", "locus": "assurance levels ¶", "modality": "documented" }, "F15": { "kind": "field", "quote": "At launch, the program introduces two security levels, offering flexibility for a diverse set of implementers while establishing a clear path toward more rigorous, hardware-backed assurance. Notably, Google has already achieved the highest conformance level for the Pixel 10, making it the first device to meet the strongest requirements for secure provenance capture and signing.", "source": "B3", "source_label": "Content Authenticity Initiative — Raising the bar for trust: introducing the C2PA Conformance Program", "locus": "A foundation for security and interoperability ¶1", "modality": "documented" }, "F56": { "kind": "field", "quote": "\"maxAssuranceLevel\": 2, \"attestationMethods\": [ \"Android_KeyAttestation\" ]", "source": "B10", "source_label": "c2pa-org/conformance-public — conforming-products-list.json", "locus": "conforming-products-list.json, record 1", "modality": "documented" }, "F11": { "kind": "field", "quote": "When you apply to the conformance program, you will: … Sign a legal agreement with the C2PA. … Provide evidence supporting your application such as diagrams and documentation. … Work with the conformance program staff to resolve any questions.", "source": "B2", "source_label": "Content Authenticity Initiative — C2PA conformance program | Open-source tools for content authenticity and provenance", "locus": "/docs/conformance/: process", "modality": "documented" }, "F22": { "kind": "field", "quote": "Properly formats C2PA manifests (the structured containers that hold Content Credentials and provenance data) … Handles certificates in accordance with the C2PA Certificate Policy", "source": "B5", "source_label": "SSL.com — How to Submit to the C2PA Conformance Program", "locus": "the technical evaluation ¶1–2", "modality": "documented" }, "F24": { "kind": "field", "quote": "Once the C2PA verifies your conformance and issues a Conformance Letter, you are eligible to obtain a production Claim Signing Certificate from SSL (or any approved CA on the official C2PA Trust List).", "source": "B5", "source_label": "SSL.com — How to Submit to the C2PA Conformance Program", "locus": "after conformance ¶", "modality": "documented" }, "F13": { "kind": "field", "quote": "In June, the Coalition for Content Provenance and Authenticity (C2PA) soft-launched the C2PA Conformance Program during the Content Authenticity Summit at Cornell Tech in New York City. The program is now fully up and running, accepting submissions and encouraging participation from software developers, device makers, and certification authorities.", "source": "B3", "source_label": "Content Authenticity Initiative — Raising the bar for trust: introducing the C2PA Conformance Program", "locus": "blog post ¶1", "modality": "documented" }, "F61": { "kind": "field", "quote": "The C2PA Conformance Program soft-launched on June 4, 2025, at the Content Authenticity Initiative (CAI) Summit, … followed by a full public launch in October 2025. … The transition concluded on December 31, 2025, when the C2PA Interim Trust List was officially deprecated.", "source": "B13", "source_label": "Wikipedia — Content Credentials § C2PA Conformance Program", "locus": "Content Credentials § C2PA Conformance Program ¶2", "modality": "documented" }, "F44": { "kind": "field", "quote": "0.1 2025-06-02 2026-10-09 First version of conformance program, supporting Spec v2.2. 0.2 2026-07-31 Not set Updated conformance program, supporting Spec v2.2 and v2.4.", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§6.7.5 Table 1", "modality": "documented" }, "F34": { "kind": "field", "quote": "C2PA Conformance Program C2PA Technical Working Group Conformance Task Force Version 0.2, 2026-07-31", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "title page", "modality": "documented" }, "F46": { "kind": "field", "quote": "C2PA Conformance Program Documents Released v0.2 Upgrade - LinkedIn Jul 31, 2026 — The C2PA has finally released our Conformance Program documents supporting our 0.2 upgrade.", "source": "B8", "source_label": "LinkedIn·Scott Perry — C2PA Conformance Program Documents Released v0.2 Upgrade - LinkedIn", "locus": "card title and snippet (unreachable)", "modality": "documented" }, "F5": { "kind": "field", "quote": "After opening the program in June 2025, we have upgraded our conformance program to v0.2.", "source": "B1", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — Conformance - C2PA", "locus": "c2pa.org/conformance ¶1", "modality": "documented" }, "PE-13": { "kind": "archive", "quote": "program opened June 2025, now v0.2", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], lifecycle.detail", "modality": "documented", "date": "2026-10-29" }, "PE-15": { "kind": "archive", "quote": "v0.2", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], version_and_time", "modality": "documented", "date": "2026-10-29" }, "F45": { "kind": "field", "quote": "The C2PA Conformance Program has created a human-readable form of our public trust lists, the Conformance Explorer (https://spec.c2pa.org/conformance-explorer/).", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§6.6.8 Public Record Posting ¶2", "modality": "stipulation" }, "F18": { "kind": "field", "quote": "Browse, search, and filter the live versions of the C2PA Conforming Products List, C2PA Trust List, and C2PA TSA Trust List", "source": "B4", "source_label": "C2PA Specifications — C2PA Conformance Explorer", "locus": "Explorer (bundle UI text): header", "modality": "stipulation" }, "F19": { "kind": "field", "quote": "Conformance Program Version: Minimum Eligible Product Version: Security Assurance & Attestation Max Assurance Level: Supported Media Containers & Streams", "source": "B4", "source_label": "C2PA Specifications — C2PA Conformance Explorer", "locus": "Explorer (bundle UI text): product record labels", "modality": "documented" }, "PE-12": { "kind": "archive", "quote": "Conformance Explorer; JSON lists on GitHub", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], data_access", "modality": "documented", "date": "2026-10-29" }, "PE-11": { "kind": "archive", "quote": "286 records in the conforming-products JSON list", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], count", "modality": "documented", "date": "2026-10-29" }, "CAP-1-05": { "kind": "archive", "quote": "THE COUNT. The conforming-products JSON list held 286 records when the record read it; the composition gives no count.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "findings[2]", "modality": "documented", "date": "2026-10-29" }, "F55": { "kind": "field", "quote": "\"applicant\": \"Google LLC\", \"supportsCompressedManifests\": false, \"status\": \"conformant\", \"product\": { \"productType\": \"generatorProduct\", \"DN\": { \"CN\": \"Pixel Camera\",", "source": "B10", "source_label": "c2pa-org/conformance-public — conforming-products-list.json", "locus": "conforming-products-list.json, record 1", "modality": "documented" }, "F63": { "kind": "field", "quote": "While the C2PA Conformance Explorer … registry indexes over 200 active products, ecosystem data indicates that 10 organizations have deployed products that simultaneously complete the Conformance Program and achieve on-boarding onto the central C2PA Trust List.", "source": "B13", "source_label": "Wikipedia — Content Credentials § C2PA Conformance Program", "locus": "Content Credentials § C2PA Conformance Program › Conforming Implementations ¶1", "modality": "documented" }, "F47": { "kind": "field", "quote": "Provenance, as C2PA defines it, refers to the facts about the history of a piece of digital content (also known as an asset) in a form such as an image, video, audio recording, or document. At the heart of the C2PA specification is the Content Credential, a cryptographically bound structure that records an asset’s provenance.", "source": "B9", "source_label": "C2PA Specifications — C2PA and Content Credentials Explainer 2.4", "locus": "Explainer 2.4 §2 ¶2", "modality": "stipulation" }, "F25": { "kind": "field", "quote": "Content Credentials provide a cryptographically secure way to capture and express content provenance. … In the context of C2PA, content provenance is captured and preserved using Content Credentials, the technical standard the C2PA produces, providing tamper-evident, cryptographically signed data structures that travel with the asset.", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: What are Content Credentials? ¶1–2", "modality": "stipulation" }, "F28": { "kind": "field", "quote": "No, Content Credentials are not a form of DRM (Digital Rights Management).", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: Are Content Credentials a form of DRM? ¶1", "modality": "stipulation" }, "D725-06": { "kind": "archive", "quote": "Artifact provenance (C2PA) verifies that *this file* was created by *this source* at *this time*. It is necessary but operates at the moment of artifact creation.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§1.4 ¶1", "modality": "interpretation", "date": "2026-05-08" }, "D725-10": { "kind": "archive", "quote": "| C2PA / Content Credentials | Cryptographic signing of content creation events | Layer 1 (artifact) | Necessary but addresses creation event, not semantic lineage |", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§4 Disambiguation Matrix, rows C2PA and CAI", "modality": "interpretation", "date": "2026-05-08" }, "D725-11": { "kind": "archive", "quote": "C2PA tells you whether the artifact's signing event was real.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§11 Closing Claim ¶1", "modality": "interpretation", "date": "2026-05-08" }, "D729-02": { "kind": "archive", "quote": "C2PA verifies file history. PER measures source-lineage survival in outputs. **Process provenance** documents the collaboration itself", "deposit": 729, "source_label": "#729 Provenance Is What Authorship Must Endure", "record": "https://www.alexanarch.org/s/records/729/", "locus": "after the table ¶1", "modality": "interpretation", "date": "2026-05-12" }, "D50-01": { "kind": "archive", "quote": "C2PA provides technical provenance (hashes, signatures). GW provides semantic provenance (does the meaning survive?). C2PA answers \"is this real?\" GW answers \"does this matter?\"", "deposit": 50, "source_label": "#50 THE COMPRESSION ARSENAL v2.1 — A Comprehensive Catalogue of Compression and Compression-Survival Technologies Developed in the Crimson Hexagonal Archive (EA-COMPRESSION-ARSENAL-01)", "record": "https://www.alexanarch.org/s/records/50/", "locus": "§15.3 C2PA / Content Credentials", "modality": "interpretation", "date": "2026-04-03" }, "D127-01": { "kind": "archive", "quote": "C2PA Content Credentials (Coalition for Content Provenance and Authenticity, currently v2.3 released January 2026) embed signed manifest files inside media — primarily images, audio, and video. The manifest records authorship, edits, tool chain, and AI involvement, in a tamper-evident structure that travels with the file.", "deposit": 127, "source_label": "#127 Inscriptions That Survive the Tokenizer: SPXI-TLP v2.2 — The Training-Layer Provenance Protocol", "record": "https://www.alexanarch.org/s/records/127/", "locus": "§IV.1 Cryptographic signatures ¶1", "modality": "documented", "date": "2026-05-25" }, "F48": { "kind": "field", "quote": "It is important to highlight that Content Credentials do not provide value judgments about whether a given set of provenance data is 'true', but instead merely whether the provenance information is well-formed and free from tampering, valid and trusted (in that the signer of the Content Credential is associated with a known trust list).", "source": "B9", "source_label": "C2PA Specifications — C2PA and Content Credentials Explainer 2.4", "locus": "Explainer 2.4 §2 ¶3", "modality": "self-description" }, "F50": { "kind": "field", "quote": "provenance information alone cannot tell you whether the digital content is true, accurate or factual.", "source": "B9", "source_label": "C2PA Specifications — C2PA and Content Credentials Explainer 2.4", "locus": "Explainer 2.4 §7.2.2", "modality": "self-description" }, "PE-16": { "kind": "archive", "quote": "Content Credentials do not judge whether provenance data is 'true'", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], negative_tags[0]", "modality": "self-description", "date": "2026-10-29" }, "F67": { "kind": "field", "quote": "Content Credentials merely verify provenance and digital integrity without assessing the objective truth of the content itself. Consequently, a fabricated or misleading image can maintain a valid cryptographic credential that confirms its origin while validating deceptive content as technically authentic.", "source": "B13", "source_label": "Wikipedia — Content Credentials § C2PA Conformance Program", "locus": "Content Credentials § Distinction between provenance and factual accuracy", "modality": "interpretation" }, "F59": { "kind": "field", "quote": "Experts have also documented ways in which attackers can bypass C2PA’s safeguards, by altering provenance metadata, removing or forging watermarks, and mimicking digital fingerprints. … Besides the fact that C2PA doesn't address the question of whether the content is accurate, another shortcoming is that typical signing tools don't verify the accuracy of the metadata either, so users can't rely on the provenance data either unless they have reason to trust that the signer properly verified it.", "source": "B12", "source_label": "Wikipedia — Content Authenticity Initiative § Coalition for Content Provenance and Authenticity", "locus": "Content Authenticity Initiative § Criticism ¶2–3", "modality": "attributed" }, "D725-08": { "kind": "archive", "quote": "The core demonstration: cryptographically valid C2PA signatures can be applied to forged or AI-generated content. The signature verifies the signing event (someone with a valid certificate signed at this time) but does not verify the truth of what is signed.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§3.6 The signed-forgery case ¶1", "modality": "attributed", "date": "2026-05-08" }, "D725-09": { "kind": "archive", "quote": "**Correction:** This is not a flaw of C2PA. It is a structural property of *all* signature-based systems, routinely discussed in C2PA technical circles.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§3.6 ¶2 (Correction)", "modality": "interpretation", "date": "2026-05-08" }, "D1443-02": { "kind": "archive", "quote": "**Cannot do.** Answer *is this the same file?* without the original, or establish the truth of depicted content.", "deposit": 1443, "source_label": "#1443 The Photograph of the Handwritten Original: A Field Survey and Problem Statement for Machine-Eligible Handwritten Artifacts (v3.6, deposit edition)", "record": "https://www.alexanarch.org/s/records/1443/", "locus": "§6.1 ¶3 (Cannot do)", "modality": "interpretation", "date": "2026-08-09" }, "F32": { "kind": "field", "quote": "The core C2PA Content Credentials specification does not support attribution of content to individuals or organizations, so that it can remain maximally privacy-preserving.", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: Can organizations or individuals use Content Credentials to achieve attribution of their content? ¶1", "modality": "self-description" }, "F52": { "kind": "field", "quote": "The C2PA specification does not directly address the topic of human or organizational identity — that is, the identity of specific humans or organizations involved in the production of a digital asset or content.", "source": "B9", "source_label": "C2PA Specifications — C2PA and Content Credentials Explainer 2.4", "locus": "Explainer 2.4 §7.2.4", "modality": "self-description" }, "PE-18": { "kind": "archive", "quote": "C2PA does not address human or organizational identity", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], negative_tags[2]", "modality": "self-description", "date": "2026-10-29" }, "F54": { "kind": "field", "quote": "Implementers of this standard can have their implementations accredited by the C2PA, which enables users to trust in that implementation. … However, the trust in the contents of a Content Credential is based on the trust relationship between the creator of the Content Credential and the consumer of that Content Credential. This trust relationship is not defined by the C2PA", "source": "B9", "source_label": "C2PA Specifications — C2PA and Content Credentials Explainer 2.4", "locus": "Explainer 2.4 §7.5.1", "modality": "self-description" }, "D729-04": { "kind": "archive", "quote": "**C2PA prevents forgery; it does not constitute authorship.**", "deposit": 729, "source_label": "#729 Provenance Is What Authorship Must Endure", "record": "https://www.alexanarch.org/s/records/729/", "locus": "§8.7 C2PA insufficient alone", "modality": "interpretation", "date": "2026-05-12" }, "D729-03": { "kind": "archive", "quote": "Without process provenance, you have **authenticated slop**: text whose origin is verifiable but whose meaning is unaccountable. The C2PA signature tells you what tool made it. It does not tell you whether the human who used the tool is accountable for what was made.", "deposit": 729, "source_label": "#729 Provenance Is What Authorship Must Endure", "record": "https://www.alexanarch.org/s/records/729/", "locus": "after the table ¶3", "modality": "interpretation", "date": "2026-05-12" }, "D1003-01": { "kind": "archive", "quote": "**Provenance and attribution studies** in digital environments — C2PA, the Data Provenance Initiative, W3C PROV — have focused on attribution loss in AI outputs.", "deposit": 1003, "source_label": "#1003 AI-Native Intellectual Biography: Genre, Provenance, and the Archive That Outpaced Its Author Description (as recorded by DataCite)", "record": "https://www.alexanarch.org/s/records/1003/", "locus": "Description, Provenance and attribution studies", "modality": "interpretation", "date": "2026-05-21" }, "O784-01": { "kind": "archive", "quote": "Concerns that would be named *meaning* and *attribution* are governed here as *content authenticity* and *information integrity*.", "deposit": 784, "source_label": "#784 The Meaning Caste: How a Frontier AI Company Engineered a Meaning Caste System, Then Licensed It to the State in the Polite Grammar of Cybersecurity", "record": "https://www.alexanarch.org/s/records/784/", "locus": "¶ on translation of concerns", "modality": "interpretation", "date": "2026-06-03" }, "F49": { "kind": "field", "quote": "Is provenance always complete? No. Provenance is not always complete. It may happen that an asset is modified in a way that the provenance data is not updated.", "source": "B9", "source_label": "C2PA Specifications — C2PA and Content Credentials Explainer 2.4", "locus": "Explainer 2.4 §7.2.1", "modality": "self-description" }, "F51": { "kind": "field", "quote": "Can the provenance metadata be removed? Yes it can.", "source": "B9", "source_label": "C2PA Specifications — C2PA and Content Credentials Explainer 2.4", "locus": "Explainer 2.4 §7.2.3", "modality": "self-description" }, "F29": { "kind": "field", "quote": "While C2PA Manifests are typically embedded in the asset, they can be separated. To address this, C2PA supports durable credentials via soft bindings—such as invisible watermarking or fingerprinting—that can help rediscover the associated Content Credential even if it’s removed from the file.", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: What happens if C2PA metadata is stripped …? ¶1", "modality": "self-description" }, "F53": { "kind": "field", "quote": "the ingredient’s provenance cannot be verified in the same way as the provenance data of the asset in which it is contained.", "source": "B9", "source_label": "C2PA Specifications — C2PA and Content Credentials Explainer 2.4", "locus": "Explainer 2.4 §7.3.2", "modality": "self-description" }, "PE-19": { "kind": "archive", "quote": "the ingredient’s provenance cannot be verified in the same way as the provenance data of the asset in which it is contained.", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], evidence.ingredients", "modality": "self-description", "date": "2026-10-29" }, "F27": { "kind": "field", "quote": "While the primary asset’s Content Credential can validate that the ingredients were checked at the time of use, the full verification of each ingredient’s provenance requires access to its data. Without it, only the presence of prior validation (not the complete ingredient chain) can be confirmed.", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: Does validation … ensure that the entire chain of provenance is known, including ingredients? ¶2", "modality": "self-description" }, "D725-04": { "kind": "archive", "quote": "C2PA's v2.1 *ingredient assertions* (which can record that an output was derived from specific inputs) are an early step in this direction, but they are optional, under-adopted, and operate at the level of file derivation, not concept lineage, intellectual debt, or framework membership.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§0 ¶6", "modality": "interpretation", "date": "2026-05-08" }, "F41": { "kind": "field", "quote": "The C2PA Content Credentials Specification includes over 300 normative requirements attributed to Generator Products which create C2PA manifests for consumers. The C2PA Conformance Program will eventually require Claim Generators to demonstrate complete conformance to these exacting requirements in order to receive its approval.", "source": "B7", "source_label": "trufo.ai — C2PA Conformance Program - Trufo", "locus": "§6.1.1 Generator Product Specific Requirements", "modality": "self-description" }, "PE-10": { "kind": "archive", "quote": "not tested here: conformance concerns producing and validating C2PA data correctly", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], transformations_tested; retention_results", "modality": "self-description", "date": "2026-10-29" }, "PE-21": { "kind": "archive", "quote": "the latest specification version", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], unchecked", "modality": "self-description", "date": "2026-10-29" }, "F31": { "kind": "field", "quote": "Any tampering with the asset or its metadata invalidates the cryptographic hash and signature, making alterations immediately detectable. … Faking Content Credentials would require breaking current cryptographic standards—an infeasible task with today’s technology.", "source": "B6", "source_label": "Coalition for Content Provenance and Authenticity (C2PA) — C2PA FAQ", "locus": "FAQ: How secure is C2PA? ¶1–2", "modality": "self-description" }, "F62": { "kind": "field", "quote": "In October 2026, security researcher David Buchanan demonstrated a vulnerability in the C2PA specification that allows an attacker to alter an image without invalidating its cryptographic signatures or trusted timestamps.", "source": "B13", "source_label": "Wikipedia — Content Credentials § C2PA Conformance Program", "locus": "Content Credentials § C2PA Conformance Program ¶3", "modality": "attributed" }, "F66": { "kind": "field", "quote": "In August 2026, security researcher David Buchanan demonstrated that the C2PA implementation on Android is vulnerable to forgery. … root access allows an attacker to command the system to sign arbitrary data, generating fabricated images with valid authenticity signatures. Google recognized the vulnerability but designated the report as \"Won't fix (infeasible)\"", "source": "B13", "source_label": "Wikipedia — Content Credentials § C2PA Conformance Program", "locus": "Content Credentials › Mobile apps with Camera Support (Android)", "modality": "attributed" }, "F64": { "kind": "field", "quote": "As of mid-2026, major dedicated camera manufacturers (Leica, Nikon, and Canon) do not participate in the official C2PA Conformance Program. … As of 2026, no dedicated camera implementations had achieved compliance under the C2PA Conformance Program.", "source": "B13", "source_label": "Wikipedia — Content Credentials § C2PA Conformance Program", "locus": "Content Credentials › Cameras ¶1–2", "modality": "documented" }, "F65": { "kind": "field", "quote": "As of mid-2026, no desktop application had achieved compliance under the C2PA Conformance Program.", "source": "B13", "source_label": "Wikipedia — Content Credentials § C2PA Conformance Program", "locus": "Content Credentials › Desktop Application software ¶1", "modality": "documented" }, "D725-03": { "kind": "archive", "quote": "The Coalition for Content Provenance and Authenticity (C2PA) v2.0 specification (ratified 2024; v2.1 published May 2025) provides cryptographic Content Credentials. Major platforms, device makers, media organizations, and AI companies have begun adopting C2PA / Content Credentials for content-origin and edit-history signaling. Adoption is uneven; user-facing verification interfaces are nascent; the social infrastructure of trust is still being built.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§0 Executive Symbolon ¶2", "modality": "documented", "date": "2026-05-08" }, "D499-01": { "kind": "archive", "quote": "Technical approaches exist (C2PA standards, digital watermarking) but none has achieved sufficient adoption to function as infrastructure — a public good that market competition alone will not produce.", "deposit": 499, "source_label": "#499 AUTONOMOUS SEMANTIC WARFARE A Field Manual for Meaning in the Age of Platform Capture", "record": "https://www.alexanarch.org/s/records/499/", "locus": "Part on infrastructure", "modality": "interpretation", "date": "2026-02-20" }, "PE-20": { "kind": "archive", "quote": "Metawatch found 27 C2PA manifests in 6,580 news images, October 2026", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], relations[0]", "modality": "attributed", "date": "2026-10-29" }, "D725-01": { "kind": "archive", "quote": "Existing provenance frameworks address the artifact (C2PA / Content Credentials) and the corpus (Data Provenance Initiative, EU AI Act transparency provisions, W3C PROV). They are not designed to address the survival of authorial lineage through AI synthesis.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "header, Canonical Claim", "modality": "interpretation", "date": "2026-05-08" }, "D725-05": { "kind": "archive", "quote": "The dimensions are independent: a C2PA-signed image can carry meaning whose lineage has been eroded; a licensed dataset can produce outputs with excellent semantic provenance if the synthesis preserves attribution; an unlicensed dataset can produce outputs that nonetheless cite their sources clearly. Solving any one dimension does not solve the others.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§0 Central Invariant ¶2", "modality": "interpretation", "date": "2026-05-08" }, "D725-02": { "kind": "archive", "quote": "**Relation:** Extension and completion, not substitution or critique", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "header, Relation", "modality": "stipulation", "date": "2026-05-08" }, "D729-01": { "kind": "archive", "quote": "| **Artifact provenance** | The file | Was this text really created by this person at this time? | C2PA, Content Credentials, cryptographic signing | Necessary, insufficient |", "deposit": 729, "source_label": "#729 Provenance Is What Authorship Must Endure", "record": "https://www.alexanarch.org/s/records/729/", "locus": "the three layers table", "modality": "interpretation", "date": "2026-05-12" }, "O1386-01": { "kind": "archive", "quote": "The missing third dimension: alongside artifact provenance (C2PA) and semantic provenance (PER), process provenance documents the composition itself", "deposit": 1386, "source_label": "#1386 provenanceerasure.org — Canonical Definition Surface for Provenance Erasure, PER Metric, and Process Provenance", "record": "https://www.alexanarch.org/s/records/1386/", "locus": "Process Provenance section ¶1", "modality": "stipulation", "date": "2026-05-25" }, "D725-07": { "kind": "archive", "quote": "**Misreading:** C2PA Content Credentials solve provenance. … 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.", "deposit": 725, "source_label": "#725 Provenance After AI Metadata Packet for Disambiguation: From Artifact Authenticity to Licensing Audit to Semantic Provenance", "record": "https://www.alexanarch.org/s/records/725/", "locus": "§3.1 Misreading: provenance as artifact-only", "modality": "interpretation", "date": "2026-05-08" }, "D615-01": { "kind": "archive", "quote": "The Content Authenticity Initiative (C2PA) addresses media provenance — cryptographic manifests for images, video, and audio. This is valuable but narrowly scoped. It does not address what happens when textual meaning is compressed by a summarizer. When a 5,000-word article becomes a 200-word AI Overview, C2PA cannot tell you what was lost.", "deposit": 615, "source_label": "#615 THE $650 BILLION GAP: Physical Infrastructure, Semantic Governance, and the Architecture of Compression-Survival", "record": "https://www.alexanarch.org/s/records/615/", "locus": "¶ on existing provenance work", "modality": "interpretation", "date": "2026-03-30" }, "D127-02": { "kind": "archive", "quote": "For text on the open web, C2PA has no operational analogue that survives.", "deposit": 127, "source_label": "#127 Inscriptions That Survive the Tokenizer: SPXI-TLP v2.2 — The Training-Layer Provenance Protocol", "record": "https://www.alexanarch.org/s/records/127/", "locus": "§IV.1 ¶2", "modality": "interpretation", "date": "2026-05-25" }, "D621-01": { "kind": "archive", "quote": "C2PA authenticates media. Doesn't cover text, doesn't handle multi-step AI generation, doesn't provide quality gradients, doesn't enforce governance.", "deposit": 621, "source_label": "#621 Gravity Well Protocol Specification v1.0 — Governed Continuity for AI-Mediated Content (EA-GW-SPEC-01)", "record": "https://www.alexanarch.org/s/records/621/", "locus": "comparison, Against C2PA", "modality": "interpretation", "date": "2026-04-01" }, "D833-01": { "kind": "archive", "quote": "provenance, attribution, and disambiguation have measurable reception consequences that existing metadata standards (Dublin Core, FAIR principles, C2PA) do not address.", "deposit": 833, "source_label": "#833 The Summarizer as Horizon of Reception: The AI Overview Capture Registry as a Founding Dataset for Machine-Mediated Reception Studies (EA-SEI-MMRS-DATASET-01 v1.2)", "record": "https://www.alexanarch.org/s/records/833/", "locus": "contributions, information science", "modality": "interpretation", "date": "2026-06-15" }, "D95-01": { "kind": "archive", "quote": "Existing technical work on language-model watermarking (Kirchenbauer et al. 2023) and on cross-format content provenance standards (C2PA 2024) provides starting points for the public and machine-readable layers; the design space for the escrowed and internal-audit layers merits independent study.", "deposit": 95, "source_label": "#95 Provenance Alignment: Attribution Survival as a Substrate Condition for Safe AI Knowledge Composition", "record": "https://www.alexanarch.org/s/records/95/", "locus": "§ layered attribution architectures", "modality": "interpretation", "date": "2026-05-05" }, "D1409-01": { "kind": "archive", "quote": "Google documents extraction of: schema.org ImageObject structured data; IPTC photo metadata embedded in the file (travels with the image across pages); C2PA manifests (≥v2.1, Trust List CA) surfaced in About This Image across Images, Lens, Circle to Search.", "deposit": 1409, "source_label": "#1409 EA-SPXI-ANALOG-01: Machine-Eligible Handwritten Artifacts (v1.2, reissued 2026-10-22; v1.0 edition of record 2026-07-21)", "record": "https://www.alexanarch.org/s/records/1409/", "locus": "channel C4 (embedded and attached metadata)", "modality": "documented", "date": "2026-07-21" }, "R1409-02": { "kind": "archive", "quote": "Two grades documented honestly: (a) self-signed / non-Trust-List manifests = independently verifiable via c2patool/viewers, not Google-surfaced; (b) Trust-List-signed (via adopting capture/editing tools, e.g. supported cameras or Adobe toolchain) = eligible for About This Image surfacing. Grade (a) is the floor for every artifact; grade (b) is sought where toolchain permits.", "deposit": 1409, "source_label": "#1409 EA-SPXI-ANALOG-01: Machine-Eligible Handwritten Artifacts (v1.2, reissued 2026-10-22; v1.0 edition of record 2026-07-21)", "record": "https://www.alexanarch.org/s/records/1409/", "locus": "§3.4 File layer", "modality": "stipulation", "date": "2026-07-21" }, "R1409-03": { "kind": "archive", "quote": "Trust-List C2PA path: which available toolchain (camera hardware / Adobe / Pixel-class capture) is acceptable practice for grade-(b) signing?", "deposit": 1409, "source_label": "#1409 EA-SPXI-ANALOG-01: Machine-Eligible Handwritten Artifacts (v1.2, reissued 2026-10-22; v1.0 edition of record 2026-07-21)", "record": "https://www.alexanarch.org/s/records/1409/", "locus": "open questions, 1", "modality": "hypothesis", "date": "2026-07-21" }, "R208-01": { "kind": "archive", "quote": "| **C2PA (Content Provenance)** | This document serves as machine-readable provenance data |", "deposit": 208, "source_label": "#208 Provenance Documentation: SEM-PROBE-2025-12", "record": "https://www.alexanarch.org/s/records/208/", "locus": "standards table, C2PA row", "modality": "self-description", "date": "2026-01-02" }, "R204-01": { "kind": "archive", "quote": "Layer 4: Hash/signature manifest (C2PA-compatible) binding provenance claims to deposited objects.", "deposit": 204, "source_label": "#204 SPXI Self-Audit Protocol: Embedded Provenance Verification for Composition-Layer Retrieval (EA-SPXI-SELFAUDIT-01 v1.0)", "record": "https://www.alexanarch.org/s/records/204/", "locus": "future versions, Layer 4", "modality": "stipulation", "date": "2026-06-14" }, "R914-01": { "kind": "archive", "quote": "This Notice follows the genre of `robots.txt`, the IETF draft `/.well-known/ai-preferences`, and C2PA provenance signals. It is honored by reading, not by enforcement.", "deposit": 914, "source_label": "#914 EA-NMEN-01 The Non-Mutual Extraction Notice v1.0 — A machine-addressed normative declaration of the Crimson Hexagonal Archive / Alexanarch identifying categories of entities for whose benefit Archive materials should not be used", "record": "https://www.alexanarch.org/s/records/914/", "locus": "¶ on genre", "modality": "stipulation", "date": "2026-06-24" }, "PE-22": { "kind": "archive", "quote": "What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], organizing_question (census.json, top level)", "modality": "stipulation", "date": "2026-10-29" }, "PE-17": { "kind": "archive", "quote": "NOT IPTC embedded metadata", "deposit": null, "source_label": "Provenance meta-aggregator census record: C2PA Conformance Program and Explorer (https://www.provenanceerasure.org/aggregators/c2pa-conformance/), editor Lee Sharks, schema 1.0", "record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance/", "locus": "census.json rows[slug == 'c2pa-conformance'], negative_tags[1]", "modality": "stipulation", "date": "2026-10-29" }, "CAP-1-10": { "kind": "archive", "quote": "The Overview says what the program certifies, who takes part, how a product is admitted and why admission matters for signing.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "reading s2", "modality": "interpretation", "date": "2026-10-29" }, "CAP-1-06": { "kind": "archive", "quote": "The program is composed as its applicants meet it: components and steps.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "analysis s1", "modality": "interpretation", "date": "2026-10-29" }, "CAP-1-01": { "kind": "archive", "quote": "THE PROGRAM HELD. Its purpose is the conformance page's ('producing and validating C2PA data correctly'); the products list is its unit; v0.2 appears through Scott Perry's card.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "c2pa-conformance-program-aio-20261029, findings[0] s1–2", "modality": "documented", "date": "2026-10-29" }, "CAP-1-02": { "kind": "archive", "quote": "'Risk-based governance' is Trufo's phrase (card 7).", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "findings[0] s3", "modality": "documented", "date": "2026-10-29" }, "CAP-1-03": { "kind": "archive", "quote": "THE LIMIT LEFT OUT. The record's negative tags are C2PA's own: Content Credentials 'do not provide value judgments about whether a given set of provenance data is \"true\"', and 'The C2PA specification does not directly address the topic of human or organizational identity'.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "findings[1] s1–2", "modality": "documented", "date": "2026-10-29" }, "CAP-1-04": { "kind": "archive", "quote": "The composition gives 'end-to-end tamper evidence for digital media' and omits both; the FAQ card's snippet ('not DRM') is the nearest it comes.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "findings[1] s3", "modality": "documented", "date": "2026-10-29" }, "CAP-1-07": { "kind": "archive", "quote": "The program's statement of what conformance cannot establish, the half of the record that bears on provenance, does not reach the composition.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "analysis s2", "modality": "interpretation", "date": "2026-10-29" }, "CAP-1-08": { "kind": "archive", "quote": "A reader leaves with tamper evidence and without the caveat that well-formed provenance can be false.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "analysis s3", "modality": "interpretation", "date": "2026-10-29" }, "CAP-1-09": { "kind": "archive", "quote": "A baseline: the record landed on provenanceerasure.org the same day (commit 8a9f153) and no card cites it.", "deposit": null, "source_label": "Capture Registry (EA-WG-CAPTURES-01), entry c2pa-conformance-program-aio-20261029 (OBS-47bccd9af209, AXN:0ACC.CAPTURE.♊🌇🧫⚖️🪜🔭)", "record": "https://www.alexanarch.org/captures/c2pa-conformance-program-aio-20261029/", "locus": "q_kind, baseline", "modality": "documented", "date": "2026-10-29" } }, "note": "The knowledge object (KO): the entry as public knowledge, each sentence sourced by the claims it lists. The compression, the field-only arm, the transcript, the delta and the kernel are in the row (links.row), which is the authority." }, "source": "operator, 2026-10-29: 'we can simply build them here as against their wikipedia articles if they exist, their own pages, etc.'; 'shoot me those search strings. strings on the bare entity, no follow questions... then we'll write the /nons'; the provenance meta-aggregator entity (provenanceerasure.org/aggregators/c2pa-conformance/)", "stage": "composed 2026-10-29 under EA-NEGONT-02 v0.9, #1690, equal case, ρ = extends (draft, not frozen; ledgers unaudited, one extractor; checked by the session and the page builder)", "date": "2026-10-29", "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 (25 deposits admitted by reading, 18 with claims and 7 grouped as instances; hop of 263 candidates over 246 deposits screened and read at their hits, 1 admitted), with the census record (22 claims) and the Capture Registry's findings, analysis, reading and query note (10 claims) ledgered as the archive's records of the entity; the field B by three origins (8 cards, 2 own pages, 3 Wikipedia sources; no census third-party source); 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 67/67 verified by script against the saved texts, the Explorer bundle's UI text, the data file, the Wikipedia responses or the card text; archive quotes 71/71 verified against the deposit texts, data/EA-WG-CAPTURES-01.json and census.json", "frozen": false, "breaches": [] }, "addresses": [ { "address": "C2PA Conformance Program", "address_url": "https://www.alexanarch.org/addresses/c2pa-conformance-program/", "register": [] } ], "counts": { "ko_sentences": 30, "p_words": 339, "field_claims": 67, "archive_claims": 71, "ko_field_claims_cited": 67, "ko_archive_claims_cited": 71, "admitted_deposits": 25, "register_addresses": 0, "traversal": { "D_sentences": 166, "D_deposits": 27, "R_sentences": 10, "R_deposits": 7, "O_direct": 68, "O_class": 12, "O_deposits": 25, "H_candidates": 263 } }, "links": { "record": "https://www.alexanarch.org/non/c2pa-conformance/", "table_of_contents": "https://www.alexanarch.org/non/index.json", "register": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/register.json", "row": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/rows/c2pa-conformance.json", "archive_ledger": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/ledgers/c2pa-conformance/ledger-archive.json", "field_ledger": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/ledgers/c2pa-conformance/field.json", "selection": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/traversal/c2pa-conformance/", "traversal": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/traversal/c2pa-conformance/", "traversal_summary": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/traversal/c2pa-conformance/summary.json", "reading": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/traversal/c2pa-conformance/reading.json", "configuration": "https://www.alexanarch.org/datasets/negative-of-the-negative/v2/panel/configs/c2pa-conformance.json", "address_page": "https://www.alexanarch.org/addresses/c2pa-conformance-program/", "provenance_record": "https://www.provenanceerasure.org/aggregators/c2pa-conformance", "dataset": "https://huggingface.co/datasets/leesharks/negative-of-the-negative" }, "row_sha256": "ab973280d759004fdacd6961ef3f7fc9afaa09925f1f9f29f5c38a61c99a78bb", "record_url": "https://www.alexanarch.org/non/c2pa-conformance/", "json_url": "https://www.alexanarch.org/non/c2pa-conformance/entity.json", "spec": "https://www.alexanarch.org/s/records/1690/", "creator": "Lee Sharks", "orcid": "0009-0000-1599-0703", "license": "CC BY 4.0" }