claimproofkit 0.1.0__tar.gz → 0.1.1__tar.gz

{claimproofkit-0.1.0/claimproofkit.egg-info → claimproofkit-0.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claimproofkit
-Version: 0.1.0
+Version: 0.1.1
 Summary: Apache-2.0 licensed, evidence-bound claim verification that blocks generated documents whose material claims the supplied evidence does not support. Python implementation of Claim Proof Specification v1, in locked parity with the Swift reference implementation.
 Author: ClaimProofKit
 License-Expression: Apache-2.0
@@ -32,7 +32,7 @@ Dynamic: license-file
 
 ClaimProofKit implements **Claim Proof Specification v1**: it checks whether the material claims in a generated document are supported by supplied evidence, and blocks publication when claims are unsupported or when no material claims can be extracted. It uses only the Python standard library at runtime.
 
-The Swift [ClaimProofKit](https://github.com/Therealdk8890/ClaimProofKit) is the reference implementation. This Python implementation is held in **locked parity** with it through the golden vectors under `conformance/vectors`. Fingerprints, verifier verdicts, and canonical payload bytes are checked across both implementations.
+The Swift [ClaimProofKit](https://github.com/Therealdk8890/ClaimProofKit) is the reference implementation. This Python implementation is held in **locked parity** with it through the golden vectors under \`conformance/vectors\`. Fingerprints, verifier verdicts, and canonical payload bytes are checked across both implementations.
 
 ## License
 
@@ -42,17 +42,17 @@ The Apache-2.0 license applies to the code in this repository; it does not grant
 
 ## Install and test
 
-```sh
+\`\`\`sh
 pip install -e ".[dev]"
 pytest
 python conformance/run_conformance.py
-```
+\`\`\`
 
 ## Verify a document
 
 A document with no extractable material claims is **not** considered safe to publish. A successful verification gate requires at least one claim, and every extracted claim must have an approved verdict. This avoids treating an empty or unrecognized document as verified by vacuous success.
 
-```python
+\`\`\`python
 from claimproofkit import ClaimVerifier, EvidencePassage, SourceType
 
 evidence = [
@@ -67,29 +67,40 @@ report = ClaimVerifier().verify_document(
     "The court denied the request for an extension.", evidence
 )
 assert report.is_safe_to_publish
-```
+\`\`\`
 
-The CLI exposes the same command semantics and exit codes as the Swift binary (0 published, 2 blocked, 3 benchmark gate failed, 64 usage, 65 unreadable input, 73 trace write failed):
+The CLI accepts one input JSON file or a folder of input JSON files. Each JSON file must contain the usual \`document\` string and \`evidence\` array. Folder mode checks top-level \`*.json\` files in filename order, prints a report for every file, and returns a failing exit code if any document is blocked or unreadable. It does not recursively scan subfolders.
 
-```sh
-claimproofkit verify input.json [--provenance trace.json]
+\`\`\`sh
+# Verify one document
+claimproofkit verify input.json
+
+# Verify every JSON document directly inside ./documents
+claimproofkit verify ./documents
+
+# Optional: write one provenance trace per document into ./traces
+claimproofkit verify ./documents --provenance ./traces
+
+# Benchmark a corpus
 claimproofkit benchmark corpus.json [--json]
-```
+\`\`\`
+
+The CLI exposes the same core verification semantics and exit codes as the Swift binary (0 published, 2 blocked, 3 benchmark gate failed, 64 usage, 65 unreadable input, 73 trace write failed). In folder mode, exit code 0 means **every** discovered JSON document passed; 2 means at least one document was blocked; 65 means at least one document could not be read or parsed; 73 means a requested provenance trace could not be written.
 
 ## Working with DProvenanceKit
 
-`claimproofkit.provenance` exports a verification run as a DProvenanceKit-compatible trace, identical to the Swift bridge's output: stable `cpk_*` event vocabulary, canonical payload bytes (Trace Specification v1 §2), lineage edges, and the §5 run fingerprint.
+\`claimproofkit.provenance\` exports a verification run as a DProvenanceKit-compatible trace, identical to the Swift bridge's output: stable \`cpk_*\` event vocabulary, canonical payload bytes (Trace Specification v1 §2), lineage edges, and the §5 run fingerprint.
 
-```python
+\`\`\`python
 from claimproofkit import ProvenanceExporter, VerificationPolicy
 
 trace = ProvenanceExporter().trace(report, VerificationPolicy())
 trace.events_json()    # decodes as [TraceEvent<AnyTraceableEvent>] in Swift DProvenanceKit
 trace.manifest_json()  # full manifest with fingerprints and edges
-```
+\`\`\`
 
 The conformance runner proves the fingerprint against the real Python [dprovenancekit](https://github.com/Therealdk8890/DProvenanceKitPython) package when it is importable: recording the trace through its SQLite store reproduces the bridge's run fingerprint byte-for-byte. The same trace fingerprints identically in Swift ClaimProofKit, Swift DProvenanceKit, and Python dprovenancekit.
 
 ## Changing locked behavior
 
-Specification changes originate in the Swift repo ([`Docs/PROOF_SPEC_V1.md`](https://github.com/Therealdk8890/ClaimProofKit/blob/main/Docs/PROOF_SPEC_V1.md)): bump the spec/verifier version there, regenerate vectors, then re-sync here with `conformance/sync-vectors.sh` and update this implementation to conform.
+Specification changes originate in the Swift repo ([\`Docs/PROOF_SPEC_V1.md\`](https://github.com/Therealdk8890/ClaimProofKit/blob/main/Docs/PROOF_SPEC_V1.md)): bump the spec/verifier version there, regenerate vectors, then re-sync here with \`conformance/sync-vectors.sh\` and update this implementation to conform.

{claimproofkit-0.1.0 → claimproofkit-0.1.1}/README.md

@@ -4,7 +4,7 @@
 
 ClaimProofKit implements **Claim Proof Specification v1**: it checks whether the material claims in a generated document are supported by supplied evidence, and blocks publication when claims are unsupported or when no material claims can be extracted. It uses only the Python standard library at runtime.
 
-The Swift [ClaimProofKit](https://github.com/Therealdk8890/ClaimProofKit) is the reference implementation. This Python implementation is held in **locked parity** with it through the golden vectors under `conformance/vectors`. Fingerprints, verifier verdicts, and canonical payload bytes are checked across both implementations.
+The Swift [ClaimProofKit](https://github.com/Therealdk8890/ClaimProofKit) is the reference implementation. This Python implementation is held in **locked parity** with it through the golden vectors under \`conformance/vectors\`. Fingerprints, verifier verdicts, and canonical payload bytes are checked across both implementations.
 
 ## License
 
@@ -14,17 +14,17 @@ The Apache-2.0 license applies to the code in this repository; it does not grant
 
 ## Install and test
 
-```sh
+\`\`\`sh
 pip install -e ".[dev]"
 pytest
 python conformance/run_conformance.py
-```
+\`\`\`
 
 ## Verify a document
 
 A document with no extractable material claims is **not** considered safe to publish. A successful verification gate requires at least one claim, and every extracted claim must have an approved verdict. This avoids treating an empty or unrecognized document as verified by vacuous success.
 
-```python
+\`\`\`python
 from claimproofkit import ClaimVerifier, EvidencePassage, SourceType
 
 evidence = [
@@ -39,29 +39,40 @@ report = ClaimVerifier().verify_document(
     "The court denied the request for an extension.", evidence
 )
 assert report.is_safe_to_publish
-```
+\`\`\`
 
-The CLI exposes the same command semantics and exit codes as the Swift binary (0 published, 2 blocked, 3 benchmark gate failed, 64 usage, 65 unreadable input, 73 trace write failed):
+The CLI accepts one input JSON file or a folder of input JSON files. Each JSON file must contain the usual \`document\` string and \`evidence\` array. Folder mode checks top-level \`*.json\` files in filename order, prints a report for every file, and returns a failing exit code if any document is blocked or unreadable. It does not recursively scan subfolders.
 
-```sh
-claimproofkit verify input.json [--provenance trace.json]
+\`\`\`sh
+# Verify one document
+claimproofkit verify input.json
+
+# Verify every JSON document directly inside ./documents
+claimproofkit verify ./documents
+
+# Optional: write one provenance trace per document into ./traces
+claimproofkit verify ./documents --provenance ./traces
+
+# Benchmark a corpus
 claimproofkit benchmark corpus.json [--json]
-```
+\`\`\`
+
+The CLI exposes the same core verification semantics and exit codes as the Swift binary (0 published, 2 blocked, 3 benchmark gate failed, 64 usage, 65 unreadable input, 73 trace write failed). In folder mode, exit code 0 means **every** discovered JSON document passed; 2 means at least one document was blocked; 65 means at least one document could not be read or parsed; 73 means a requested provenance trace could not be written.
 
 ## Working with DProvenanceKit
 
-`claimproofkit.provenance` exports a verification run as a DProvenanceKit-compatible trace, identical to the Swift bridge's output: stable `cpk_*` event vocabulary, canonical payload bytes (Trace Specification v1 §2), lineage edges, and the §5 run fingerprint.
+\`claimproofkit.provenance\` exports a verification run as a DProvenanceKit-compatible trace, identical to the Swift bridge's output: stable \`cpk_*\` event vocabulary, canonical payload bytes (Trace Specification v1 §2), lineage edges, and the §5 run fingerprint.
 
-```python
+\`\`\`python
 from claimproofkit import ProvenanceExporter, VerificationPolicy
 
 trace = ProvenanceExporter().trace(report, VerificationPolicy())
 trace.events_json()    # decodes as [TraceEvent<AnyTraceableEvent>] in Swift DProvenanceKit
 trace.manifest_json()  # full manifest with fingerprints and edges
-```
+\`\`\`
 
 The conformance runner proves the fingerprint against the real Python [dprovenancekit](https://github.com/Therealdk8890/DProvenanceKitPython) package when it is importable: recording the trace through its SQLite store reproduces the bridge's run fingerprint byte-for-byte. The same trace fingerprints identically in Swift ClaimProofKit, Swift DProvenanceKit, and Python dprovenancekit.
 
 ## Changing locked behavior
 
-Specification changes originate in the Swift repo ([`Docs/PROOF_SPEC_V1.md`](https://github.com/Therealdk8890/ClaimProofKit/blob/main/Docs/PROOF_SPEC_V1.md)): bump the spec/verifier version there, regenerate vectors, then re-sync here with `conformance/sync-vectors.sh` and update this implementation to conform.
+Specification changes originate in the Swift repo ([\`Docs/PROOF_SPEC_V1.md\`](https://github.com/Therealdk8890/ClaimProofKit/blob/main/Docs/PROOF_SPEC_V1.md)): bump the spec/verifier version there, regenerate vectors, then re-sync here with \`conformance/sync-vectors.sh\` and update this implementation to conform.

{claimproofkit-0.1.0 → claimproofkit-0.1.1}/claimproofkit/cli.py

@@ -1,7 +1,7 @@
 # Copyright 2026 Daniel Kissel
 # SPDX-License-Identifier: Apache-2.0
 
-"""``claimproofkit`` CLI — mirrors the Swift executable's commands and exit codes.
+"""claimproofkit CLI — mirrors the Swift executable's commands and exit codes.
 
 Exit codes: 0 published / gate passed, 2 blocked, 3 benchmark gate failed,
 64 usage, 65 unreadable input, 73 provenance trace write failed.
@@ -12,6 +12,7 @@ from __future__ import annotations
 import json
 import sys
 import time
+from pathlib import Path
 from typing import List, Optional
 
 from .benchmark import BenchmarkCorpus, BenchmarkRunner
@@ -21,9 +22,15 @@ from .report import benchmark_report_json, render_benchmark_markdown, render_rep
 from .verifier import ClaimVerifier
 
 USAGE = """Usage:
-  claimproofkit verify <input.json> [--provenance <trace.json>]
+  claimproofkit verify <input.json|folder> [--provenance <trace.json|trace-folder>]
   claimproofkit benchmark <corpus.json> [--json]
 
+When input is a folder, ClaimProofKit verifies each top-level *.json file in
+filename order. Each JSON file must use the normal single-document input
+schema. All files are processed; the command fails closed if any file is
+unreadable or any report is blocked. With folder input, --provenance names an
+output folder and each trace is written as <input-stem>.trace.json.
+
 --provenance writes a DProvenanceKit-compatible trace manifest of the
 verification run alongside the report.
 
@@ -39,23 +46,28 @@ def _usage(code: int) -> int:
     return code
 
 
+def _read_and_verify(path: str):
+    with open(path, encoding="utf-8") as handle:
+        data = json.load(handle)
+    evidence = [
+        EvidencePassage(
+            id=p["id"],
+            source=p["source"],
+            source_type=SourceType(p["sourceType"]),
+            text=p["text"],
+        )
+        for p in data["evidence"]
+    ]
+    policy = VerificationPolicy()
+    report = ClaimVerifier(policy).verify_document(data["document"], evidence, created_at=time.time())
+    return report, policy
+
+
 def _run_verification(path: str, provenance_path: Optional[str]) -> int:
     try:
-        with open(path, encoding="utf-8") as handle:
-            data = json.load(handle)
-        evidence = [
-            EvidencePassage(
-                id=p["id"],
-                source=p["source"],
-                source_type=SourceType(p["sourceType"]),
-                text=p["text"],
-            )
-            for p in data["evidence"]
-        ]
-        policy = VerificationPolicy()
-        report = ClaimVerifier(policy).verify_document(data["document"], evidence, created_at=time.time())
+        report, policy = _read_and_verify(path)
     except Exception as error:  # noqa: BLE001 - CLI boundary
-        sys.stderr.write(f"claimproofkit: {error}\n")
+        sys.stderr.write(f"claimproofkit: failed to verify {path}: {error}\n")
         return 65
 
     # The report is always emitted, even if the trace write fails afterwards.
@@ -74,6 +86,65 @@ def _run_verification(path: str, provenance_path: Optional[str]) -> int:
     return 0 if report.is_safe_to_publish else 2
 
 
+def _run_verification_folder(folder_path: str, provenance_path: Optional[str]) -> int:
+    folder = Path(folder_path)
+    try:
+        if not folder.is_dir():
+            raise NotADirectoryError(f"not a directory: {folder}")
+        # Snapshot inputs before writing any provenance traces.
+        inputs = sorted(
+            (entry for entry in folder.iterdir() if entry.is_file() and entry.suffix == ".json"),
+            key=lambda entry: entry.name,
+        )
+    except Exception as error:  # noqa: BLE001 - CLI boundary
+        sys.stderr.write(f"claimproofkit: cannot read input folder {folder}: {error}\n")
+        return 65
+
+    if not inputs:
+        sys.stderr.write(f"claimproofkit: no top-level .json documents found in {folder}\n")
+        return 65
+
+    trace_folder: Optional[Path] = None
+    if provenance_path is not None:
+        trace_folder = Path(provenance_path)
+        try:
+            if trace_folder.resolve() == folder.resolve():
+                sys.stderr.write("claimproofkit: provenance output folder must differ from the input folder\n")
+                return 64
+            trace_folder.mkdir(parents=True, exist_ok=True)
+            if not trace_folder.is_dir():
+                raise NotADirectoryError(str(trace_folder))
+        except Exception as error:  # noqa: BLE001 - CLI boundary
+            sys.stderr.write(f"claimproofkit: cannot prepare provenance output folder {trace_folder}: {error}\n")
+            return 73
+
+    results = []
+    for path in inputs:
+        print(f"\n## Document: {path.name}\n")
+        trace_path = str(trace_folder / f"{path.stem}.trace.json") if trace_folder is not None else None
+        results.append((path.name, _run_verification(str(path), trace_path)))
+
+    passed = sum(code == 0 for _, code in results)
+    blocked = sum(code == 2 for _, code in results)
+    unreadable = sum(code == 65 for _, code in results)
+    trace_errors = sum(code == 73 for _, code in results)
+    print(
+        f"\n## Folder summary\n\n"
+        f"Documents: {len(results)} · Safe to publish: {passed} · "
+        f"Blocked: {blocked} · Unreadable: {unreadable} · Trace errors: {trace_errors}"
+    )
+
+    # A folder is successful only when every document passes and every requested
+    # trace is written. Input errors and trace errors must not be hidden by a pass.
+    if trace_errors:
+        return 73
+    if unreadable:
+        return 65
+    if blocked:
+        return 2
+    return 0
+
+
 def _run_benchmark(path: str, as_json: bool) -> int:
     try:
         with open(path, encoding="utf-8") as handle:
@@ -118,6 +189,8 @@ def main(argv: Optional[List[str]] = None) -> int:
                 return _usage(64)
         if path is None:
             return _usage(64)
+        if Path(path).is_dir():
+            return _run_verification_folder(path, provenance)
         return _run_verification(path, provenance)
     if command == "benchmark":
         rest = arguments[1:]
@@ -128,7 +201,10 @@ def main(argv: Optional[List[str]] = None) -> int:
         return _usage(64)
     if len(arguments) == 1:
         # Backward compatibility: a lone path runs verification.
-        return _run_verification(command, None)
+        path = arguments[0]
+        if Path(path).is_dir():
+            return _run_verification_folder(path, None)
+        return _run_verification(path, None)
     return _usage(64)
 
 

{claimproofkit-0.1.0 → claimproofkit-0.1.1/claimproofkit.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claimproofkit
-Version: 0.1.0
+Version: 0.1.1
 Summary: Apache-2.0 licensed, evidence-bound claim verification that blocks generated documents whose material claims the supplied evidence does not support. Python implementation of Claim Proof Specification v1, in locked parity with the Swift reference implementation.
 Author: ClaimProofKit
 License-Expression: Apache-2.0
@@ -32,7 +32,7 @@ Dynamic: license-file
 
 ClaimProofKit implements **Claim Proof Specification v1**: it checks whether the material claims in a generated document are supported by supplied evidence, and blocks publication when claims are unsupported or when no material claims can be extracted. It uses only the Python standard library at runtime.
 
-The Swift [ClaimProofKit](https://github.com/Therealdk8890/ClaimProofKit) is the reference implementation. This Python implementation is held in **locked parity** with it through the golden vectors under `conformance/vectors`. Fingerprints, verifier verdicts, and canonical payload bytes are checked across both implementations.
+The Swift [ClaimProofKit](https://github.com/Therealdk8890/ClaimProofKit) is the reference implementation. This Python implementation is held in **locked parity** with it through the golden vectors under \`conformance/vectors\`. Fingerprints, verifier verdicts, and canonical payload bytes are checked across both implementations.
 
 ## License
 
@@ -42,17 +42,17 @@ The Apache-2.0 license applies to the code in this repository; it does not grant
 
 ## Install and test
 
-```sh
+\`\`\`sh
 pip install -e ".[dev]"
 pytest
 python conformance/run_conformance.py
-```
+\`\`\`
 
 ## Verify a document
 
 A document with no extractable material claims is **not** considered safe to publish. A successful verification gate requires at least one claim, and every extracted claim must have an approved verdict. This avoids treating an empty or unrecognized document as verified by vacuous success.
 
-```python
+\`\`\`python
 from claimproofkit import ClaimVerifier, EvidencePassage, SourceType
 
 evidence = [
@@ -67,29 +67,40 @@ report = ClaimVerifier().verify_document(
     "The court denied the request for an extension.", evidence
 )
 assert report.is_safe_to_publish
-```
+\`\`\`
 
-The CLI exposes the same command semantics and exit codes as the Swift binary (0 published, 2 blocked, 3 benchmark gate failed, 64 usage, 65 unreadable input, 73 trace write failed):
+The CLI accepts one input JSON file or a folder of input JSON files. Each JSON file must contain the usual \`document\` string and \`evidence\` array. Folder mode checks top-level \`*.json\` files in filename order, prints a report for every file, and returns a failing exit code if any document is blocked or unreadable. It does not recursively scan subfolders.
 
-```sh
-claimproofkit verify input.json [--provenance trace.json]
+\`\`\`sh
+# Verify one document
+claimproofkit verify input.json
+
+# Verify every JSON document directly inside ./documents
+claimproofkit verify ./documents
+
+# Optional: write one provenance trace per document into ./traces
+claimproofkit verify ./documents --provenance ./traces
+
+# Benchmark a corpus
 claimproofkit benchmark corpus.json [--json]
-```
+\`\`\`
+
+The CLI exposes the same core verification semantics and exit codes as the Swift binary (0 published, 2 blocked, 3 benchmark gate failed, 64 usage, 65 unreadable input, 73 trace write failed). In folder mode, exit code 0 means **every** discovered JSON document passed; 2 means at least one document was blocked; 65 means at least one document could not be read or parsed; 73 means a requested provenance trace could not be written.
 
 ## Working with DProvenanceKit
 
-`claimproofkit.provenance` exports a verification run as a DProvenanceKit-compatible trace, identical to the Swift bridge's output: stable `cpk_*` event vocabulary, canonical payload bytes (Trace Specification v1 §2), lineage edges, and the §5 run fingerprint.
+\`claimproofkit.provenance\` exports a verification run as a DProvenanceKit-compatible trace, identical to the Swift bridge's output: stable \`cpk_*\` event vocabulary, canonical payload bytes (Trace Specification v1 §2), lineage edges, and the §5 run fingerprint.
 
-```python
+\`\`\`python
 from claimproofkit import ProvenanceExporter, VerificationPolicy
 
 trace = ProvenanceExporter().trace(report, VerificationPolicy())
 trace.events_json()    # decodes as [TraceEvent<AnyTraceableEvent>] in Swift DProvenanceKit
 trace.manifest_json()  # full manifest with fingerprints and edges
-```
+\`\`\`
 
 The conformance runner proves the fingerprint against the real Python [dprovenancekit](https://github.com/Therealdk8890/DProvenanceKitPython) package when it is importable: recording the trace through its SQLite store reproduces the bridge's run fingerprint byte-for-byte. The same trace fingerprints identically in Swift ClaimProofKit, Swift DProvenanceKit, and Python dprovenancekit.
 
 ## Changing locked behavior
 
-Specification changes originate in the Swift repo ([`Docs/PROOF_SPEC_V1.md`](https://github.com/Therealdk8890/ClaimProofKit/blob/main/Docs/PROOF_SPEC_V1.md)): bump the spec/verifier version there, regenerate vectors, then re-sync here with `conformance/sync-vectors.sh` and update this implementation to conform.
+Specification changes originate in the Swift repo ([\`Docs/PROOF_SPEC_V1.md\`](https://github.com/Therealdk8890/ClaimProofKit/blob/main/Docs/PROOF_SPEC_V1.md)): bump the spec/verifier version there, regenerate vectors, then re-sync here with \`conformance/sync-vectors.sh\` and update this implementation to conform.

{claimproofkit-0.1.0 → claimproofkit-0.1.1}/claimproofkit.egg-info/SOURCES.txt

@@ -21,6 +21,7 @@ claimproofkit.egg-info/entry_points.txt
 claimproofkit.egg-info/requires.txt
 claimproofkit.egg-info/top_level.txt
 tests/test_benchmark_metrics.py
+tests/test_cli_folder.py
 tests/test_conformance.py
 tests/test_identity_and_bridge.py
 tests/test_swift_parity_regressions.py

{claimproofkit-0.1.0 → claimproofkit-0.1.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "claimproofkit"
-version = "0.1.0"
+version = "0.1.1"
 description = "Apache-2.0 licensed, evidence-bound claim verification that blocks generated documents whose material claims the supplied evidence does not support. Python implementation of Claim Proof Specification v1, in locked parity with the Swift reference implementation."
 readme = "README.md"
 requires-python = ">=3.9"

claimproofkit-0.1.1/tests/test_cli_folder.py

@@ -0,0 +1,98 @@
+# Copyright 2026 Daniel Kissel
+# SPDX-License-Identifier: Apache-2.0
+
+"""Folder-mode CLI tests."""
+
+import json
+import os
+import subprocess
+import sys
+from pathlib import Path
+
+
+def _write_input(path: Path, document: str) -> None:
+    path.write_text(
+        json.dumps(
+            {
+                "document": document,
+                "evidence": [
+                    {
+                        "id": "order-1",
+                        "source": "Scheduling Order",
+                        "sourceType": "courtRecord",
+                        "text": "The court denied the request for an extension.",
+                    }
+                ],
+            }
+        ),
+        encoding="utf-8",
+    )
+
+
+def _run(folder: Path, *extra: str) -> subprocess.CompletedProcess:
+    env = dict(os.environ)
+    env["PYTHONIOENCODING"] = "utf-8"
+    return subprocess.run(
+        [sys.executable, "-m", "claimproofkit.cli", "verify", str(folder), *extra],
+        capture_output=True,
+        text=True,
+        encoding="utf-8",
+        env=env,
+        check=False,
+    )
+
+
+def test_folder_verification_processes_json_in_filename_order_and_passes(tmp_path: Path):
+    _write_input(tmp_path / "b.json", "The court denied the request for an extension.")
+    _write_input(tmp_path / "a.json", "The court denied the request for an extension.")
+    (tmp_path / "notes.txt").write_text("not an input", encoding="utf-8")
+
+    result = _run(tmp_path)
+
+    assert result.returncode == 0
+    assert result.stdout.index("Document: a.json") < result.stdout.index("Document: b.json")
+    assert "Documents: 2 · Safe to publish: 2 · Blocked: 0" in result.stdout
+
+
+def test_folder_verification_fails_closed_when_any_document_is_blocked(tmp_path: Path):
+    _write_input(tmp_path / "supported.json", "The court denied the request for an extension.")
+    _write_input(tmp_path / "unsupported.json", "The plaintiff filed a second amended complaint.")
+
+    result = _run(tmp_path)
+
+    assert result.returncode == 2
+    assert "Safe to publish: 1 · Blocked: 1" in result.stdout
+    assert "Document: supported.json" in result.stdout
+    assert "Document: unsupported.json" in result.stdout
+
+
+def test_folder_verification_continues_after_unreadable_document(tmp_path: Path):
+    _write_input(tmp_path / "a-good.json", "The court denied the request for an extension.")
+    (tmp_path / "b-bad.json").write_text("{not json", encoding="utf-8")
+    _write_input(tmp_path / "c-good.json", "The court denied the request for an extension.")
+
+    result = _run(tmp_path)
+
+    assert result.returncode == 65
+    assert "Document: c-good.json" in result.stdout
+    assert "Unreadable: 1" in result.stdout
+    assert "failed to verify" in result.stderr
+
+
+def test_folder_verification_rejects_empty_folder(tmp_path: Path):
+    result = _run(tmp_path)
+
+    assert result.returncode == 65
+    assert "no top-level .json documents found" in result.stderr
+
+
+def test_folder_provenance_writes_one_trace_per_input(tmp_path: Path):
+    _write_input(tmp_path / "a.json", "The court denied the request for an extension.")
+    _write_input(tmp_path / "b.json", "The court denied the request for an extension.")
+    trace_folder = tmp_path / "traces"
+
+    result = _run(tmp_path, "--provenance", str(trace_folder))
+
+    assert result.returncode == 0
+    assert (trace_folder / "a.trace.json").is_file()
+    assert (trace_folder / "b.trace.json").is_file()