Two passages state 'Latest Python 3 Release - Python 3.15.0', which verifies the version-status component as written in the evidence. The claim's attribution to python.org is not verified: neither supporting source (4edb0b8bd553, 5433ffd2a2ac) is identified as python.org, and the defense itself concedes this gap. The passages also carry no retrieval date, so the present-tense 'latest' status cannot be confirmed as current. The prosecution's point about tension with the October 9, 2026 date is not resolved by the record and is not treated as a contradiction, since the evidence does not establish which status applies.

Missing: Evidence that source 4edb0b8bd553 and/or 5433ffd2a2ac is python.org (domain or URL). A capture or retrieval timestamp showing the 'latest' status at the time of evaluation.

Three passages independently list 'Python 3.15.0 - Oct. 9, 2026', which verifies the date string. The claim's characterization of this date as 'official' is not established: the passages are table-style listings with no indication of a release schedule document, PEP, or announcement, and the source IDs are not identified as authoritative. The claim also omits the 'planned' qualifier that scheduled release dates typically require, and the defense does not address whether the date is current.

Missing: A primary authoritative source (release schedule, PEP, or official announcement) identifying the date as official. Identification of the sources for 4edb0b8bd553, 5433ffd2a2ac, and 6e7e0903d242. Confirmation that the date has not been revised.

The passage shows the text labels 'Download' and 'Release notes' alongside Python 3.15.0, which verifies that these elements appear. It does not show that they are hyperlinks, where they point, or that the page is python.org. The source 6e7e0903d242 is not identified as python.org. The claim's attribution and functional link claims therefore remain unverified.

Missing: The page URL or DOM/markup showing that 'Download' and 'Release notes' are hyperlinks. Their target URLs. Identification of source 6e7e0903d242 as python.org.

Evidence 84cd42d5a890 contains the token 'bugfix' directly after '3.15', which supports the association between Python 3.15 and the value 'bugfix'. However, the passage has no column headers, so reading 'bugfix' as the status field is an inference from layout. The claim also attributes the listing to the python.org stable releases table, but the passage does not name its page or table, and the link rests on source_id 6e7e0903d242, which is not included in the evidence text. No capture date is provided, so it is unclear whether the status is current.

Missing: The labeled table or page content showing a 'Status' column header, confirmation that the source is the python.org stable releases table (including the source_id 6e7e0903d242 content), and a capture date establishing currency.

Evidence 84cd42d5a890 shows the bare string '2026-10-09' in the row following '3.15', 'bugfix', and 'Download'. The value is present, but the passage does not label it as a 'release date'. That interpretation depends on column order, which the passage does not confirm. The evidence also cannot show whether the date is a confirmed release or a projected schedule, and the python.org source attribution is unverified.

Missing: A labeled table with a 'Release date' column header, the PEP 790 content or other authoritative confirmation of the date type, and source verification.

Evidence 84cd42d5a890 contains '2031-10' as the second date value in the row for 3.15. The value is present at month precision. However, the passage does not label it as 'end-of-support'. That reading is inferred from position and general table conventions, which the record does not establish. The PEP 790 reference is not examined, and the source link to the stable releases table is unverified.

Missing: A labeled 'End of support' column or equivalent header in the source, the PEP 790 content confirming the end-of-support milestone, and source verification.

The cited passage shows the string "PEP 790" in the same row as Python 3.15 ("3.15 bugfix Download 2026-10-09 2031-10 PEP 790"), which supports the core association between 3.15 and PEP 790. The claim's other components are not verified. The passage does not show the table heading, so the "stable releases table" label is unconfirmed. The passage also does not show a hyperlink, so "references" in the sense of linking to the PEP is unverified. The snapshot has no capture date.

Missing: A capture of the table heading showing it is the stable releases table, the underlying HTML or link target showing PEP 790 is hyperlinked, and a capture timestamp.

The passage "3.16 pre-release Download 2027-10-06 (planned)" directly maps to the claim that python.org lists Python 3.16 with a status of pre-release. The mapping is exact for the listing and status. However, the claim uses present tense ("lists") without an observation date, and the evidence is a single extracted row from one source with no capture timestamp. Currency of the listing therefore cannot be confirmed from the record.

Missing: A capture timestamp for the observation, and ideally a second independent capture confirming the status.

The passage shows "2027-10-06 (planned)" in the row for Python 3.16, which supports the date value and the planned qualifier. However, the claim states the date as a fixed fact ("is") and omits the planned qualifier that the evidence itself carries. The passage has no column headers, so identifying the date as the release date rather than another schedule milestone is inferred. The snapshot is also undated.

Missing: Column headers showing the date column is the release date, a capture timestamp, and wording that reflects the date is a planned, not confirmed, value.

Both passages state the version 'Python 3.14.8' and the date 'Sept. 30, 2026', which map exactly to the claim's version and date components. The abbreviation 'Sept.' is an unambiguous form of September. The passages are not identical in format ('Python 3.14.8' on one line with the date on the next, versus a hyphen-separated single line), which weakly suggests they are not verbatim copies. However, the passages do not identify their publisher, URL, or retrieval date, so the authority of the source cannot be checked. The evidence also does not establish that the two passages are independent of each other. Finally, the passages do not show what 'released' means here (public availability versus tag or calendar date) or which time zone applies. The core version-and-date match is strong, but the source-quality and independence components are unverified.

Missing: The official python.org release announcement or release page showing the version and date, with URL and retrieval date. Confirmation that the two passages come from distinct publications. A statement of the time zone or the release-date convention used.

Evidence: 4 · Sources: 3 · Verified claims: 0 · Contradictions: 0

Evidence: 3 · Sources: 3 · Verified claims: 0 · Contradictions: 0

Evidence: 6 · Sources: 3 · Verified claims: 0 · Contradictions: 0

No contradictions detected.

Criteria: A specific version number (e.g., X.Y.Z) is identified from python.org's official downloads page or release listings, with the source URL and retrieval date noted. Pre-release, beta, and release-candidate versions are excluded.

Criteria: A calendar date is confirmed from an official Python source, such as the python.org release page, the release announcement, or the Python Developer's Guide release schedule, for the exact version identified in the first subquestion. The date should be cited with its source.

Criteria: The evidence confirms that no newer final (non-pre-release) Python version has been published as of the date checked, using python.org or the Python Developer's Guide. Any newer patch or feature release is identified, or the absence of one is documented with the date of verification.

Limitations

• Search coverage depends on Brave Search results and retrievable public pages
• Certificate metrics measure internal claim-to-evidence integrity, not external truth