# Cerulion Docs

## Docs

- [Claude Code setup](https://docs.cerulion.com/ai-tools/claude-code.md): Configure Claude Code to write and maintain Cerulion documentation using Anthropic's official CLI
- [Cursor setup](https://docs.cerulion.com/ai-tools/cursor.md): Configure Cursor to write and maintain Cerulion documentation with AI-assisted workflows
- [Windsurf setup](https://docs.cerulion.com/ai-tools/windsurf.md): Configure Windsurf's Cascade AI to write and maintain Cerulion documentation
- [Components](https://docs.cerulion.com/cerulion/architecture/components.md): TopicManager, Publisher, and Subscriber — three components that give you dual-transport pub/sub with zero configuration
- [Data Flow](https://docs.cerulion.com/cerulion/architecture/data-flow.md): How data moves through Cerulion — zero-copy local paths, async network paths, and automatic discovery with no manual routing
- [Determinism](https://docs.cerulion.com/cerulion/architecture/determinism.md): Why ROS2 log replay doesn't reproduce behavior, and how Cerulion's deterministic scheduler, zero-copy logging, and controlled replay fix it
- [High Bandwidth Optimization](https://docs.cerulion.com/cerulion/architecture/high-bandwidth.md): Frame budget math: why a 6 MB camera image has the same transport cost as a 24-byte pose — zero-copy transport, observability, and planned stream presets
- [Architecture Overview](https://docs.cerulion.com/cerulion/architecture/overview.md): Dual-transport architecture with sub-microsecond local latency, automatic network fallback, and zero-copy data paths — no configuration required
- [Rust Backend](https://docs.cerulion.com/cerulion/architecture/rust-backend.md): Why Cerulion's Rust backend eliminates segfaults, undefined behavior, and data races at compile time — not in production
- [Scheduling](https://docs.cerulion.com/cerulion/architecture/scheduling.md): Deterministic node execution with explicit triggers — periodic, input, synchronized, and external — no OS thread scheduling, no callback races
- [Transport System](https://docs.cerulion.com/cerulion/architecture/transport-system.md): Automatic transport selection — shared memory for same-host, Zenoh for network — with no configuration required; per-topic TCP/UDP overrides coming soon
- [CLI Commands](https://docs.cerulion.com/cerulion/commands.md): Every workspace, node, graph, and topic command with examples and output
- [Install Cerulion](https://docs.cerulion.com/cerulion/installation.md): Get Cerulion running on your machine in under 2 minutes
- [Cerulion Overview](https://docs.cerulion.com/cerulion/overview.md): High-performance pub/sub middleware for robotics with sub-microsecond latency
- [Publisher & Subscriber](https://docs.cerulion.com/cerulion/pub-sub.md): Wire nodes together with typed topics — ~60 ns local latency, automatic transport, zero config
- [Quickstart](https://docs.cerulion.com/cerulion/quickstart.md): Build a camera-to-display pipeline in under 5 minutes — from scratch or from ROS2
- [Why Cerulion](https://docs.cerulion.com/cerulion/why-cerulion.md): Your middleware is eating 18% of your frame budget. Here's why Cerulion is better in every dimension.
- [Wireformat Messages](https://docs.cerulion.com/cerulion/wireformat-messages.md): ROS2-compatible message types — Image, Twist, Odometry — with zero-copy transport and no type changes
- [Zero-Copy Logging](https://docs.cerulion.com/cerulion/zero-copy-logging.md): Record your robot's behavior without changing it. Zero-copy logging means what you record is what happened.

## Optional

- [Cerulion Website](https://www.cerulion.com)
- [Cerulion Blog](https://blog.cerulion.com)