Space Sharing Lexicon

Generated from docs/lexicon/space-sharing.md, do not edit by hand. Run pnpm docs:reference to refresh.

This is the naming guide for Space Sharing, shared sync, Wormholes, capability proof, and collaboration transport. It refines the repository-wide vocabulary in docs/GLOSSARY.md; it does not redefine those domain contracts.

Naming Rule

User language describes the experience. Code language describes the domain object. Protocol language describes the mechanism.

The current Space Sharing demo proves technical foundations. Shared Place is an evidence-gated product-strategy term for a complete consumer experience, not another name for that demo.

Canonical Terms

Term	Layer	Use For
Space Sharing	Product	User-facing feature name
Shared Space	Product	User-facing shared object or session
`SharedSpace` / `sharedSpace`	Code	Shared Space domain namespace
`collaborationRoomId`	Code	High-level Scene Sync room identity
`presenceRoomId`	Code	High-level live-cursor presence scope
`room` / `roomId`	Transport	Internal transport scope
Peer View	Product	User-facing embedded participant view
Workbench	Proof	Demo composition of Peer Views and one Trust Rail
Trust Rail	Proof	Presence, permissions, audit, transport, and transfer proof panel
Saved Shared State	Product	User-facing durable shared state
retained state	Code	Internal persistence term
Shared Space Snapshot	Code	Participant-specific, access-filtered Shared Space projection
Hosted Shared Scene Snapshot	Code	Active or retained hosted authority view
Collaboration Mode	Protocol	Requested central, peer-to-peer, or mixed policy
Collaboration Transport Path	Transport	Actual central or peer-to-peer path for one envelope
Wormhole	Product	Cross-space move or share concept
Wormhole Route	Code	Canonical local-space or trusted-connection destination
Wormhole Connection	Code	Durable reciprocal trust between two endpoints
Capability Proof	Proof	Proof that an actor can use a capability or path
authenticated transport identity	Protocol	Principal bound to a verified room delivery

Code And Protocol Spellings

Code: SharedSpace, sharedSpace, collaborationRoomId, presenceRoomId, room, roomId
Protocol values: central, p2p, mixed
Internal prose: retained state, collaboration envelope, sync payload, sync result
Wormhole messages: wormhole.transfer.offer, wormhole.transfer.receiver-claim, wormhole.transfer.cancel, wormhole.transfer.cancel-ack, wormhole.transfer.content, and wormhole.transfer.receipt

Usage Rules

Product copy uses Space Sharing, Shared Space, Saved Shared State, and Peer View according to the definitions above.
Every Wormhole destination is a Wormhole Route. A trusted-connection route references a Wormhole Connection; a local-space route does not.
Both Wormhole route variants use destinationSpaceId and optional destinationWormholeId. Do not create variant-specific space ID names.
Authenticated transport identity names the Principal bound to verified room delivery.
Use collaborationRoomId in high-level Scene Sync options. Reserve roomId for protocol records and lower-level transport rooms, and reserve channel for an actual transport channel object.
Use presenceRoomId only for the high-level Shared Space live-cursor option. Presence entries, transport envelopes, and lower-level room APIs keep roomId.
Use Capability Proof unless the proof is specifically about wire-protocol compatibility.
Expand peer-to-peer (P2P) on first use in a user-facing flow. Exact p2p literals remain valid in code and protocol payloads.
Qualify Shared Space Snapshot, Hosted Shared Scene Snapshot, Scene Sync checkpoint, content manifest, and content transfer ticket so they do not collide with repository-wide terms.