Peerwork SDK 0.1.4 (experimental)

Peerwork SDK 0.1.4 adds bounded PRIVATE lease guards using trusted transaction admission time and explicit native Owner guard-time activation.

• Checked time_add(T, duration) in conjunctive comparison guards supports minimum/maximum TTL, renewal before expiry with a later proposed expiry, and reclaim at expiry with a newer generation. The shared Rust engine derives and verifies the signed admission interval; overflow and unsupported forms fail closed.
• Python owner.guard_time(workspace_id), Node owner.guardTime(workspaceId) and peerwork guard-time provide activation, original-operation recovery and protected local history. Activation requires the exact Owner, a fully verified source, current-policy CAS, pinned service and explicit GUARD_WINDOW consent. Exact encrypted packets persist before submission.
• The standalone Python example includes an installable package closure and pins. It demonstrates claim, renew, reclaim and stale-generation rejection using the official installed SDK. Its directory setup is qualified on Linux; it does not provision Windows ACLs or define an application's permissions.

Complete Python example · Native usage and compatibility · Public platform guide

The service capability must explicitly advertise time-add-guard-window-v1 with TIME_FREE effects. Expiry remains an encrypted client proposal; signed transaction time authorizes admission. Time-derived encrypted effects and automatic signer-key rotation are unsupported. Upgrade clients that write or perform full semantic replay before adopting arithmetic histories; older clients reject these new semantics. External systems must enforce generation fencing themselves.

Source: fdb2f09f3eeead3fb19cc22f905c6e2066000b75. Native distribution run: 39268931251. The release contains eight target artifact ZIPs, SOURCE.json and SHA256SUMS. This is an experimental GitHub prerelease, not a stable release or a PyPI/npm registry upload.