appendix

Glossary

Words we use, what we mean by them.

Agent SDK — Anthropic’s official integration surface for embedding Claude Code into other applications. Node uses it.

Agentic Printf — The debugging-agent pattern. A specialized agent that hypothesizes about a bug, instruments code with logs, runs the failing path, and reads logs back to diagnose. Named for the historical effectiveness of printf debugging.

Beachhead — A first wedge customer segment chosen for sharp fit. For us, AI-native small teams (Phase 1) and game studios on Perforce (Phase 2 commercial).

Dashboard — The web client. Where directors and members see a project’s Nodes, members, presence, activity feed, and recaps. Renders state; never mutates it.

Director — The new role enabled by AI coworking. The human who steers multiple agentic workstreams without typing most of the code themselves.

Dock — verb. To attach a machine or a user (device) to a project as a Node. The basic act of becoming part of a Manifoldone coworking project.

estelle — The open-source predecessor by sirgrey8209 that proved the SSOT/stateless/display-only architecture for the 1-Pylon case. Manifoldone extends it to multi-Node.

Manifold — math. A space that locally looks Euclidean but globally has structure. The product name comes from this. Each developer’s local environment is a flat patch; the project as a whole is the curved global structure that connects them.

Memory — The project’s shared brain. SaaS-side store (Postgres + objects) that holds members, nodes, Threads, and Recaps in v0.1; promoted prompts, MCPs, and skills in Phase 2+. Was previously called Aerepo (Aether + Repo).

Node — The local daemon. A long-lived process on a machine that owns project state, runs the agent, and talks to VCS. One member can have many Nodes. Was previously called Pylon (a name inherited from estelle).

Pairing code — A 6-character single-use token (10-minute TTL) generated in the Dashboard and consumed by manifoldone dock to register a Node. Issues a long-lived JWT for subsequent Relay connections.

Recap — The one-paragraph summary generated automatically when a Thread ends on a Node. Generated through a Manifoldone-managed LLM gateway so the user’s own Claude tokens are not consumed.

Thread — One CC conversation with its own context history and compaction, modeled as the user-facing unit of work. Replaces “session” everywhere we own (DB schema, wire envelope, dashboard route, CLI status). Concurrency is bounded per-Node by MANIFOLDONE_MAX_CONCURRENT_THREADS (default 3). See the Thread rename amendment.

Relay — The stateless WebSocket router that connects Nodes to Dashboards. Carries presence and activity; holds no durable state.

Same X — The naming pattern for the four product pillars (Same Project, Same Brain, Same Process, Same Output). The repetition is intentional; it underlines that each one is something today’s tooling fails to share.

Soulstream — The open-source Claude Code as a Service project whose HTTP/SSE event vocabulary Manifoldone borrows on the wire.

Vibe Coding — The pattern of working with an AI agent by stating intent and waiting, rather than typing code yourself. Named after the broader “vibe coding” cultural moment.

Vibe PR — A PR whose payload is intent + chat + recap, not just diff. The Manifoldone-native unit of code review.

Worker — Informal English for a machine docked to a project as a Node. Avoid in technical writing — always prefer Node. Kept here only because earlier docs and casual conversation still use it.

Renamed terms (legacy)

These terms appear in earlier drafts and may still surface in old commits or external blog posts. The current names on the right are canonical.