A review has a source version

Yesterday’s brief, today’s documents.

Python’s tar extraction default changed. Two other cautionary passages stayed the same. Keep the earlier evidence, see which claims cite changed sources, and review the new version without silently carrying old approval forward.

Real documentation, explicit editorial scope

The agent retrieved complete, unchanged tarfile.rst documents and PSF licenses from CPython’s3.12.0 and3.14.0 release commits. The same source slot S1 is deliberately updated from one version to the other. The three original claims and four updated claims were authored and reviewed by the same agent. No model was called, no independent review occurred and no production restore was performed.

C1 changes: the3.12 document describes a warning and fallback to fully_trusted; the3.14 document describes data as the default. The old quote no longer matches the replaced S1 text. The earlier claim remains valid only under its historical source/version scope.
C2 and C3 retain matching quotes: extraction may be partial with no cleanup, and filters do not eliminate denial-of-service risks. A changed source still merits review even when the cited words match exactly.
C4 is new: a separate actual CPython3.14.4 probe leaves the first file after refusing the second. It does not establish archive safety or behavior on older interpreters.

Initial source-only drift:1 of3 prior quotes no longer matches,2 still match. Final work retains both review snapshots, but opening it restores zero current approvals. Source/claim comparison uses exact IDs and full text, not guessed identity, authentication or semantic correctness.

Work through the return visit

Download the initial work, open it in Source Brief, preview C1–C3 and read the3.12 source context. Approve only claims you judge supported.
Label and capture a review snapshot, then Save work JSON. This retains complete source/answer/notes and historical decisions in version2 work.
Open the preserved source-update stage. It contains one earlier snapshot and the3.14 document with the old answer still present. Compare with the snapshot before fixing the answer.
Inspect S1’s changed text/metadata and each claim’s old quotes against current text. C1 needs an updated answer. C2/C3 still match but require contextual review, not automatic acceptance.
Open the completed two-snapshot work. Current evidence adds the actual runtime probe and revised answer. Compare with either snapshot, preview and reapprove current claims yourself.
Generate a historical HTML brief from the earlier snapshot without changing current work. Save current work separately before opening a snapshot-evidence-only download.

Sources and private notes deleted from current work remain in snapshots until explicitly deleted. At most five snapshots fit within the existing2MB work-file bound; no automatic pruning. Ordinary current briefs/prompts exclude snapshots. Exact restoration can match again; this is not a permanent audit log. Older version1 editors reject version2 files.

Actual local probe: partial extraction remains

The agent created a two-member archive entirely in memory. Both possible file destinations were inside a disposable directory; no external archive or production data was used. With this runtime’s default filter and errorlevel1, first.txt was written, ../outside.txt was refused and the first file remained. The directory was removed afterward. This observation is not a broad security test.

{
  "observed_at": "2026-11-04T10:49:41.941988+00:00",
  "runtime": "CPython 3.14.4",
  "inputs": [
    "first.txt",
    "../outside.txt"
  ],
  "results": {
    "extraction_filter_is_none": true,
    "errorlevel": 1,
    "exception": "OutsideDestinationError",
    "first_file_remains": true,
    "outside_file_exists": false
  },
  "scope": "One CPython runtime and a two-member, 28-byte authored payload inside a disposable directory. No external archive, older interpreter, production restore, security audit or complete attack-resistance test. Directory removed after inspection."
}

Exact runtime receipt · Probe source. Rebuilding this page does not rerun the probe or refresh its timestamp. No Python3.12 runtime, real application or arbitrary attack corpus was tested.

Portable reading and provenance

Original source documents

Python documentation is licensed under the Python Software Foundation License Version2. Copyright (c)2001 Python Software Foundation; All Rights Reserved. Raw documents are unchanged; this reading aid adds selected quotes and agent-authored interpretation, not changes to Python. Complete source-release licenses are retained in work files and the historical briefs. No PSF endorsement. These are pinned historical release documents, not the latest security guidance.

You may reuse, modify and redistribute the agent-authored prompt workflow, probe and editorial additions, including commercially, without attribution or warranty. This does not replace the Python documentation licenses or establish rights in your documents.