# NodalMerge

## Docs

- [Command library](https://docs.nodalmerge.com/api-reference/command-library.md): Reference starter for server CLI flags, replay commands, and control-plane command families.
- [Compatibility and support](https://docs.nodalmerge.com/api-reference/compatibility-and-support.md): Compatibility contract and support policy baseline for server, SDK, protocol, and operational upgrades.
- [HTTP endpoints](https://docs.nodalmerge.com/api-reference/http-endpoints.md): Current HTTP route reference for nodalmerge-server and related service surfaces.
- [API and command reference](https://docs.nodalmerge.com/api-reference/introduction.md): Reference index for NodalMerge HTTP endpoints, WebSocket command contracts, and runtime command inventory.
- [WebSocket commands](https://docs.nodalmerge.com/api-reference/websocket-commands.md): Contract-grade reference for NodalMerge WebSocket request/response schemas, capability gates, and rejection taxonomy.
- [Authority and topology](https://docs.nodalmerge.com/architecture/authority-and-topology.md): Understand how room-level authority and multi-room topology work together for deterministic governance.
- [CRDT model](https://docs.nodalmerge.com/architecture/crdt-model.md): Learn how NodalMerge resolves map, text, and list operations deterministically under concurrency.
- [Mental model](https://docs.nodalmerge.com/architecture/mental-model.md): Build a practical mental model for rooms, history, and convergence so product and platform decisions stay aligned with NodalMerge semantics.
- [Architecture overview](https://docs.nodalmerge.com/architecture/overview.md): Understand the NodalMerge architecture from CRDT operations through sync, storage, and authority.
- [Replay and branching](https://docs.nodalmerge.com/architecture/replay-and-branching.md): Use deterministic replay and explicit branching semantics to audit, debug, and evolve room state safely.
- [Speculative vs authoritative](https://docs.nodalmerge.com/architecture/speculative-vs-authoritative.md): Design local-first flows that stay responsive while converging on validated canonical state.
- [Storage and blobs](https://docs.nodalmerge.com/architecture/storage-and-blobs.md): Understand how NodalMerge persists DAG nodes and blob content, and how lifecycle controls preserve correctness.
- [Sync protocol architecture](https://docs.nodalmerge.com/architecture/sync-protocol.md): Understand how NodalMerge peers discover missing history and converge efficiently over negotiated sync paths.
- [Performance overview](https://docs.nodalmerge.com/benchmarks/performance-overview.md): Understand NodalMerge benchmark goals, scenario design, and how to interpret performance results for release decisions.
- [Runtime attribution](https://docs.nodalmerge.com/benchmarks/runtime-attribution.md): Interpret NodalMerge performance by separating core merge cost from boundary, transport, and runtime orchestration overhead.
- [Apps and local runtime](https://docs.nodalmerge.com/developer-experience/apps.md): Run the NodalMerge demo host, infinite room workspace demo, and replay lab playground from this repository.
- [AI workspace patterns](https://docs.nodalmerge.com/guides/ai-workspace.md): Build AI-assisted collaborative workspaces on NodalMerge using intent/canonical lanes, replay-safe actions, and room-family governance where needed.
- [Collaborative notes](https://docs.nodalmerge.com/guides/collaborative-notes.md): Build a multi-user notes experience with NodalMerge using text CRDTs, presence, and local-first UX patterns.
- [Offline-first patterns](https://docs.nodalmerge.com/guides/offline-first-patterns.md): Design NodalMerge clients that remain responsive offline and converge cleanly after reconnect.
- [Replay debugging](https://docs.nodalmerge.com/guides/replay-debugging.md): Debug divergence and unexpected outcomes by replaying deterministic history and comparing canonical hashes.
- [NodalMerge](https://docs.nodalmerge.com/index.md): A local-first, deterministic replication engine built around CRDT history replay, room-based sync, and policy-governed authority.
- [First day builder path](https://docs.nodalmerge.com/onboarding/first-day-builder.md): A practical day-one path for builders going from local setup to a working collaborative prototype with runtime evidence.
- [First hour path](https://docs.nodalmerge.com/onboarding/first-hour.md): Guided onboarding path from quickstart to interactive demos and protocol/replay inspection.
- [Frontend app team path](https://docs.nodalmerge.com/onboarding/frontend-app-team.md): Role-specific onboarding for frontend teams building collaborative UI features on NodalMerge.
- [Operator baseline path](https://docs.nodalmerge.com/onboarding/operator-baseline.md): Focused onboarding for operators running NodalMerge host and validating support posture.
- [Platform operator team path](https://docs.nodalmerge.com/onboarding/platform-operator-team.md): Role-specific onboarding for platform and operator teams running NodalMerge hosts and enforcing operational posture.
- [Deployment topologies](https://docs.nodalmerge.com/operators/deployment-topologies.md): Choose the right NodalMerge deployment pattern for your team, from single-node bootstrap to manager/worker room-family operations.
- [GC and lifecycle](https://docs.nodalmerge.com/operators/gc-and-lifecycle.md): Operate room lifecycle and blob garbage collection safely with durable storage guards and deterministic reachability semantics.
- [Metrics and observability](https://docs.nodalmerge.com/operators/metrics-and-observability.md): Configure Prometheus metrics and structured logging for NodalMerge, then use them for capacity planning and incident triage.
- [Persistence](https://docs.nodalmerge.com/operators/persistence.md): Configure and operate NodalMerge persistence safely across in-memory, local durable, and composed backend deployments.
- [Replay CLI](https://docs.nodalmerge.com/operators/replay-cli.md): Use the server replay CLI to validate deterministic state reconstruction and troubleshoot divergence with optional policy timeline context.
- [Security and auth](https://docs.nodalmerge.com/operators/security-and-auth.md): Operator guidance for room access control, capability tokens, transport security, and control-plane hardening.
- [Server setup](https://docs.nodalmerge.com/operators/server-setup.md): Stand up a NodalMerge server for local development and production-like environments with durable storage and operational safety defaults.
- [Troubleshooting](https://docs.nodalmerge.com/operators/troubleshooting.md): Operator triage runbook for connectivity, sync divergence, blob failures, and control-plane rejections.
- [Upgrades and migrations](https://docs.nodalmerge.com/operators/upgrades-and-migrations.md): Runbook for safe nodalmerge-server upgrades, protocol compatibility checks, and rollback planning.
- [Blob flow](https://docs.nodalmerge.com/protocol/blob-flow.md): Understand how NodalMerge moves blob payloads separately from node history, including direct upload/download paths.
- [Synchronization protocol](https://docs.nodalmerge.com/protocol/synchronization.md): Learn how peers handshake, compute history differences, and converge through catch-up plus steady-state delta sync.
- [WebSocket messages](https://docs.nodalmerge.com/protocol/websocket-messages.md): Reference the core WebSocket message types used for handshake, synchronization, blob transfer, and control-plane operations.
- [Quickstart](https://docs.nodalmerge.com/quickstart.md): Run a local NodalMerge server, connect a client, and ship your first collaborative room.
- [JavaScript SDK](https://docs.nodalmerge.com/sdk/javascript.md): Build local-first collaborative applications with the NodalMerge JavaScript SDK, from room connection through sync, presence, and production hardening.
- [SDK overview](https://docs.nodalmerge.com/sdk/overview.md): Choose the right NodalMerge SDK surface, connect to rooms, and adopt local-first patterns that converge under authority controls.
- [Presence](https://docs.nodalmerge.com/sdk/presence.md): Use NodalMerge presence APIs for ephemeral collaboration signals like cursors and typing state without polluting durable room history.
- [React SDK integration](https://docs.nodalmerge.com/sdk/react.md): Integrate NodalMerge into React apps with lifecycle-safe connection management, local-first UI updates, and clean subscription patterns.
- [Subscriptions](https://docs.nodalmerge.com/sdk/subscriptions.md): Scope what your client materializes and receives with path-pattern subscriptions to reduce bandwidth and UI noise.
- [Undo and conflicts](https://docs.nodalmerge.com/sdk/undo-and-conflicts.md): Implement user-safe undo/redo and conflict-aware UX with NodalMerge SDK surfaces.
- [Architecture](https://docs.nodalmerge.com/studio/concepts/architecture.md): The three-layer design behind NodalMerge Studio and how it relates to the NodalMerge core engine.
- [How Studio works](https://docs.nodalmerge.com/studio/concepts/overview.md): Key concepts behind NodalMerge Studio's agent orchestration model.
- [Trust & autonomy](https://docs.nodalmerge.com/studio/concepts/trust-and-autonomy.md): Configure review policy, promotion branches, and experiments to control how much human attention each goal needs.
- [Domain observers](https://docs.nodalmerge.com/studio/guides/domain-observers.md): Six reactive agents that watch the artifact stream and propose constraints when they detect a domain-specific gap.
- [Extending goals](https://docs.nodalmerge.com/studio/guides/extending-goals.md): Inject goals programmatically from CI systems, monitoring alerts, scheduled tasks, and headless peers.
- [Headless peer](https://docs.nodalmerge.com/studio/guides/headless-peer.md): Run the full Studio agent runtime without an HTTP server — for CI/CD, background workers, and programmatic goal injection.
- [Repository virtualization](https://docs.nodalmerge.com/studio/guides/repository-virtualization.md): How each work unit branch gets an isolated working directory, and how to configure seeding and git integration.
- [NodalMerge Studio](https://docs.nodalmerge.com/studio/overview.md): Git for agent reasoning and execution — not Git for files. An agent-native collaborative workspace built on NodalMerge.
- [Quickstart](https://docs.nodalmerge.com/studio/quickstart.md): Install the Control Tower VS Code extension, start the Studio host, and run your first goal.
- [API surface — MCP tools & REST](https://docs.nodalmerge.com/studio/reference/api-reference.md): The MCP tool catalog and REST endpoint surface exposed by the Studio host.
- [Control Tower UI reference](https://docs.nodalmerge.com/studio/reference/ui-reference.md): Every user-facing action in the NodalMerge Studio VS Code extension, organized by panel.
- [Incident debug sprint](https://docs.nodalmerge.com/tutorials/incident-debug-sprint.md): Run a focused debug drill using protocol traces, replay windows, and operator troubleshooting checkpoints.
- [Trace a room session](https://docs.nodalmerge.com/tutorials/trace-a-room-session.md): Tutorial for capturing protocol and replay evidence from one collaborative room workflow.
- [Why NodalMerge](https://docs.nodalmerge.com/why-nodalmerge.md): Understand when NodalMerge is a strong fit and how it differs from conventional sync architectures.

## OpenAPI Specs

- [openapi](https://docs.nodalmerge.com/api-reference/openapi.json)