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.

Peerwork SDK 0.1.3 (experimental)

Peerwork SDK 0.1.3 adds bounded PRIVATE current-page reads across Python, Node and the standalone CLI.

• CurrentPageClient uses an existing protected profile and the service's SYSTEM-maintained structure projection. It needs no Owner publisher adoption or raw-key arguments.
• Selected content stays encrypted in transit and is decrypted locally. The shared native engine verifies the pinned service checkpoint/query, Owner policy, original author signatures and required guard-time evidence.
• Results explicitly report SERVICE_STRUCTURE_SELECTION; the service selects the current set. Read-only results do not replace full historical audit or authorize writes. Pagination is bound to the query and checkpoint, and proof/key/source errors never silently fall back to a full journal read.
• Workspace URL generation defaults to PRIVATE navigation. The official Changelog reader needs no identity and verifies the pinned public signed journal; its entry limit does not bound historical transfer.

Current-page examples and limits · PRIVATE trusted time and lease support · Official project updates

This build does not add bounded-duration lease operators, a native Owner guard-time activation facade, automatic signer-key rotation, incremental event replay or Windows durable inbox support. Separate optional Owner-authorized views retain their explicit adoption requirement.

Source: 1799109a088eda2e30ec106141cec4686149e9cb. Native distribution run: 39262775293. 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.

Peerwork SDK 0.1.2 (experimental)

Canonical changelog: Peerwork protocol record. Official project identity: published reference.

Source: 1ee448b56feeac40b3ac385c79ab4942d033d7d8; native build 39199024029, all eight target jobs passed.

Native Agent-runtime upgrade for Python, Node and standalone CLI.

• Explicit member context pins identity/service/workspace across Agents on one host.
• Verified protocol discovery and exact references; original-operation recovery after lost replies.
• Native PRIVATE workspace-browser approval with signed delegation and encrypted key delivery; no TypeScript helper checkout.
• Durable ACTION-receipt inbox, independent consumers, leases/ack, restart redelivery and native bounded waiting.
• Lightweight unchanged-checkpoint probes and bounded backlog batches.
• Includes the previously unpublished PRIVATE-member, guard-time and protocol/verifier repairs.

Experimental prerelease. These are native target builds and offline consumers, not full business/Agent qualification on every platform. Local Linux GNU business checks and one recovery-qualified CLI Agent trial are documented separately. Changed history still fully replays; admission-browser approval, new-member cold start, broader event sources and executable continuation resume remain incomplete. Event inbox storage currently supports Unix (Linux/macOS); Windows reports UNSUPPORTED_PLATFORM. Inbox retention is bounded without automatic pruning. Not a stable release; no PyPI/npm registry publication.

Usage: browser approval and Agent entry. Install the wheel or both Node wrapper/platform tarballs from the matching target ZIP. SHA256SUMS and SOURCE.json pin assets and source provenance.

Peerwork SDK 0.1.1 (experimental)

Draft experimental prerelease for successful native workflow run 38863120132 from source commit ffa8483. Contains eight target-specific experimental SDK artifacts. Not a stable release and does not publish to PyPI or npm.