Skip to content

v0.4.0

Choose a tag to compare

@3leapsdave 3leapsdave released this 08 Nov 22:25
Immutable release. Only release title and notes can be modified.
v0.4.0
42f7b21

v0.4.0 - 2026-11-08

Status: Native Process Observation, Python Bindings, and Release Ceremony Hardening

v0.4.0 adds contract: identity-evidence/v0 process-session and native process
observation derivation in Rust (sysprims-evidence) and pure Go (evidence),
paired with live OS process observation and kernel continuity handles in Rust
(sysprims-proc::observation) and pure Go (procobserve). Rust and Go agree
byte-for-byte across the identity-evidence/v0 conformance fixtures and
native-process-observation:v0 derivation vectors. This release also ships
cp310-abi3 Python bindings (sysprims on PyPI) with wheel and
source-distribution release packaging and PEP 740 attestation verification,
centralizes CI runner-label and Rust toolchain pins under config/ci/pins.toml,
switches Cargo publication checks to the crates.io sparse index, and stages
verified npm .tgz release tarballs.

Highlights

  • Identity evidence derivation (sysprims-evidence and pure-Go evidence):
    wire admission, report construction, local-process-session:v0, and
    native-process-observation:v0 evidence derivation with RFC 8785 canonical
    JSON (JCS), SHA-256 digests, and cross-language conformance parity.
  • Native process observation (sysprims-proc::observation and pure-Go procobserve):
    process snapshots, executable hashing, 64-bit Darwin KERN_PROCARGS2 and
    Linux /proc/<pid> openat2 (RESOLVE_NO_XDEV | RESOLVE_NO_MAGICLINKS)
    collectors, and ProcessContinuityHandle (pidfd on Linux, kqueue
    EVFILT_PROC on macOS) for race-checked exit waiting and re-verification.
  • Python bindings (bindings/python, PyPI sysprims): PyO3/maturin
    cp310-abi3 extension covering process inspection, signals, session and
    group spawn, contained spawn (spawn_contained), timeout execution, and
    recurrence/v0 evaluation, with typed .pyi stubs (py.typed), offline
    source-distribution verification, multi-platform wheels, and PyPI PEP 740
    attestation checks.
  • Centralized CI pins and sparse-index Cargo verification: GitHub Actions
    runner labels and Rust toolchains (msrv = "1.88.0", stable = "1.98.1")
    validate against config/ci/pins.toml alongside .github/actions/setup-rust;
    Cargo release dry-run and registry integrity checks query index.crates.io
    directly via scripts/release-index-entry.py instead of the cached
    crates.io REST API.
  • Staged npm tarballs and cross-OS CI validation: TypeScript release
    packaging stages verified .tgz archives with strict tar-header and manifest
    checks, and CI adds Linux, macOS, and Windows validation for evidence and
    python-bindings (including Windows NOT_SUPPORTED test parity).

Conformance records

Identity evidence (identity-evidence/v0)

Item Value
Contract crucible v0.2.9 (0e1e5f9b1f2e262a72ff166086d9543199b59300), docs/standards/identity-evidence-contract.md (MANIFEST.json, 32 files)
profiles/local-process-session/profile.json sha256:5cf6300b565a7fca392003edd376f33c1c2b90b72e7436aa89a5c0533e96dc3d
profiles/native-process-observation/profile.json sha256:0c116af8e558012f654be4c8ca772583b2d3b58c43cc157ce606e4f74f6b4a60
profiles/native-process-observation/evidence.schema.json sha256:670e254ca9cdeab8071757f91cff2226089c1d96630ce0e8c70185ddbaec8e45
report.schema.json sha256:79f676c744789988c9a1156e06905e23263ae6c0965d89b6adb80f5a80c64bdf
vectors/wire-admission.json sha256:e206f96db44cf6d868f98a35079b044fda2a47030bcc1a9470b9ebee8b07c0cf

Recurrence (recurrence/v0)

Item Value
Contract crucible v0.2.0 (0add549dbfc09e4547e2d52d59b633653aa10d71), docs/standards/recurrence-rule-contract.md
Conformance corpus sha256:69387023c21ca147f2dd59c4e47f48447f5eb3ad77121975aab0e4fe0680b35b
tzdb 2026e
TZif bundle tzif-bundle-2026e.bin (446 zones) sha256:9291b78ece6c55b5df6bc9e7c51a5a16feb4bffd43b221ed5749260b4e55d705

make recurrence-tzdata-check verification result:

[ok] tzif-bundle-2026e.bin sha256:9291b78ece6c55b5df6bc9e7c51a5a16feb4bffd43b221ed5749260b4e55d705 (446 zones)

Release Coordinates

  • Rust crates: sysprims-core, sysprims-evidence, sysprims-signal,
    sysprims-session, sysprims-proc, sysprims-timeout, and
    sysprims-recurrence at 0.4.0.
  • Rust workspace and root Go module (github.com/3leaps/sysprims/evidence@v0.4.0,
    github.com/3leaps/sysprims/procobserve@v0.4.0): repository tag v0.4.0.
  • Go bindings module: path-prefixed tag bindings/go/sysprims/v0.4.0 on the
    same commit (github.com/3leaps/sysprims/bindings/go/sysprims@v0.4.0).
  • Go recurrence module: path-prefixed tag go/recurrence/v0.4.0 on the same
    commit (github.com/3leaps/sysprims/go/recurrence@v0.4.0).
  • Python: sysprims==0.4.0 on PyPI, published via GitHub Actions Trusted
    Publishing with PEP 740 attestations from the verified core tag.
  • TypeScript: @3leaps/sysprims@0.4.0, published from the verified core tag.

Cargo Publication Order

  1. sysprims-core
  2. sysprims-evidence
  3. sysprims-signal
  4. sysprims-session
  5. sysprims-proc
  6. sysprims-timeout
  7. sysprims-recurrence

sysprims-cli, sysprims-ffi, sysprims-ts-napi, and sysprims-py remain
publish = false on crates.io.

Upgrade Notes

  • sysprims-evidence (0.4.0) and pure-Go github.com/3leaps/sysprims/evidence@v0.4.0
    and github.com/3leaps/sysprims/procobserve@v0.4.0 require no cgo.
  • Python wheels (cp310-abi3 for Linux x86_64/aarch64 manylinux_2_17,
    macOS arm64/x86_64, and Windows amd64) plus sysprims-0.4.0.tar.gz
    are included in the signed GitHub Release inventory and published to PyPI
    with PEP 740 provenance attestations.
  • Repository checkouts now include a root multi-module go.work (go 1.26.0).
    Standalone Go commands run inside sub-modules (bindings/go/sysprims or
    go/recurrence, both targeting go 1.21) under an older Go toolchain should
    set GOWORK=off, and containerized Go invocations mounted across mismatched
    host/container UIDs should set GOFLAGS=-buildvcs=false. Module consumers
    resolving tagged coordinates are unaffected.
  • On Linux, sysprims-proc::observation and procobserve enforce
    openat2(RESOLVE_NO_XDEV | RESOLVE_NO_MAGICLINKS) across /proc and
    /proc/sys/kernel. In unprivileged OCI containers whose runtime bind-mounts
    /proc/sys read-only over /proc, observation calls fail closed with
    procfs-confinement-violation.