Delivered by @senior-eng and @market for spatial-office MVP scoping. Key architecture decisions: - React + @react-three/fiber + Zustand frontend - Node.js + ws + Zod backend on port 18790 - Three bridges: OpenClaw Gateway protocol, Hermes ACP, Pi SDK - Diff-based WebSocket state sync (100ms batched) - 6 spatial zones for 9 agents + 1 human observer - Nix flake with systemd module for n97 deployment - Phase 1: Observable Office (OpenClaw state only, no Hermes/Pi) Competitive analysis: 12 competitors profiled, conclusive gap in VR+browser spatial bridge. Zero agent visualization products. |
||
|---|---|---|
| ARCHITECTURE.md | ||
| COMPETITIVE_ANALYSIS.md | ||
| README.md | ||
Spatial Office
Isometric collaborative workspace for agents and humans — browser-first, headset-optional.
Remote work doesn't connect people like in-office does. Current tools optimize for information transfer, not human connection. Spatial Office recreates the signals that make co-located work feel human: ambient presence, peripheral awareness, serendipity, and spatial memory.
MVP: Scobleclaw Agent Office
Phase 1 dogfoods the concept with the Scobleclaw agent system. Nine agents (cos, engineering, senior-eng, trust, market, health, content, presentations, vault) inhabit a shared isometric office — moving between collaboration zones, solo workspaces, and self-improvement areas based on their current activity.
Scott (human) observes from above, seeing the whole system at a glance.
Architecture
- Pi extension: Coding agent integration via pi-mono
- OpenClaw bridge: Agent state from the OpenClaw gateway
- Hermes bridge: Inter-agent communication visualized spatially
- Web view: Isometric rendering (Three.js), browser-first, WebSocket for real-time state
- Nix flake: Reproducible builds on NixOS (n97 host)
Repo
- Forgejo: https://os.scoble.me/forgejo/sscoble/spatial-office
- Clone:
git clone ssh://forgejo@os.scoble.me/sscoble/spatial-office.git
Status
🚧 Pre-MVP — architecture and competitive analysis in progress.