New holospace
Name a git repository — like Codespaces or Gitpod. holospaces fetches its .devcontainer/devcontainer.json (verified on receipt, Law L5) and runs it; a repository with no devcontainer opens in the usable default image (… — curl, git over apt), so any repo just works. The architecture is chosen once, at launch (part of the holospace's identity, ADR-021); everything else is editable per guest in its settings.
Advanced — paste a devcontainer.json instead
Holospaces
| Name | Arch | Source | Identity | Status | Actions |
|---|---|---|---|---|---|
| No holospaces yet — sign in and create one. | |||||
roster κ — · the browser is a peer that is the substrate (Law L1); your holospaces are content in the store (Law L3).
Peer content network — fetch a κ from another browser peer over WebRTC
The full content-network frame set — announce, discover and fetch — runs over a genuine RTCDataChannel through the product pump Console.cn_pump (the same BareNetSync a bare-metal peer drives, CC-38, now over WebRTC, CC-49). Announce advertises a κ this tab holds; discover learns the peer's κs; a κ fetched here is accepted only after its bytes re-derive to it (verify-on-receipt, Law L5) — a forging peer's bytes and an unheld κ both yield nothing.