Skip to content

DProvenanceKit 0.10.0 — Local workflow history and portable evidence

Latest

Choose a tag to compare

@Therealdk8890 Therealdk8890 released this 16 Nov 03:24
26ca41f

What's new

  • Opt-in local reasoning history: preserve selected workflow snapshots and recorded executions as immutable commits; branch experiments, compare paths, and promote baselines with conditional ref updates.
  • Portable evidence: canonical SHA-256 objects, full-closure bundles, detached P-256 signatures, and offline verification shared with the Swift SDK.
  • Read-only workbenches: browse multiple trace databases, compare runs across sources, and inspect paged repository history with dpk ui --repo.
  • Experimental Structural Alignment v1: deterministic integer basis-point scoring with independent F1, hierarchy, and order gates. The existing regression-gate engine remains available.
  • Experimental configuration authorization: canonical fingerprints and Ed25519 manifests checked against independently supplied trusted-key policy. Signature operations use the optional [crypto] extra.
  • External P-256 signing-provider protocol: applications can supply compatible signing adapters. This is an interface, not a bundled HSM/TPM integration or hardware-attestation verifier.

Integrity and compatibility

Capture lifecycle and loss accounting, critical-event decoding, read-only capture sealing, snapshot-provenance validation, repository compare-and-swap decisions, and explicit signer-trust handling are hardened. Shared malformed-attestation cases exercise rejection behavior across Python and Swift.

Existing trace commands, frozen Trace Specification v1, profile hashes, and DPK-BINARY-V1 attestation encoding remain available. Repository branch commits require the documented expected parent; trusted verification requires an independently supplied trust policy. The critical-step order-intent policy remains a design proposal.

Structural Alignment v1 and configuration authorization remain experimental and opt-in. Recorded steps and signatures establish recorded evidence and integrity, not truth, complete observation, hardware custody, or authority to execute. Matching SDK versions do not imply identical capabilities: Python owns local history operations/workbenches; Swift supplies portable object and read-only bundle verification.

Validation

  • Local Python 3.12 suite: 749 passed, 4 optional integrations skipped (CrewAI, LlamaIndex, and OpenAI Agents were not installed).
  • Regression corpus: 13/13 passed. Ruff and mypy passed.
  • Wheel built from sdist; both distributions passed metadata checks. A fresh installation verified version/resources, no core dependencies, and both offline demos, including rejected skipped verification and a verified bundle round trip.
  • All 10 shared fixture files match Swift byte-for-byte.
  • Merged-commit CI passed the supported Python/OS matrix, repository protocol on Linux/macOS/Windows, installed-wheel smoke, lint/type checks, and Docker/Compose validation. Heavy real-framework integration jobs were skipped as configured and are not claimed as verified.

Install

This GitHub Release starts the PyPI Trusted Publishing workflow. After it succeeds:

python -m pip install "dprovenancekit==0.10.0"
dpk demo
dpk repo demo --output-dir history-demo

For signatures, install dprovenancekit[crypto]==0.10.0. The previously prepared 0.9.3 candidate was never published; its workbench changes are included here.

Release commit: 26ca41f9657a8b123673f2de463f3a669a8b8f96.

Full changelog · Release checklist