BaudBound is developed as a group of focused repositories in the
BaudBound GitHub organization. Each repository owns one product or one clearly defined supporting responsibility.
| Repository | Responsibility |
|---|---|
BaudBound/baudbound |
Runner CLI, headless service, Tauri desktop application, desktop UI, and Rust crates |
BaudBound/editor |
Next.js visual editor, node registry, verification, simulation, package export, and editor container |
BaudBound/contracts |
Published JSON Schemas and machine-readable editor-to-runner contracts |
BaudBound/documentation |
Public wiki source, navigation, validation, and Wiki.js publisher |
BaudBound/get |
Hosted Linux and Windows installation scripts at get.baudbound.app |
BaudBound/tooling |
Shared development menu, repository coordination, local package builds, and runner release helper |
BaudBound/website |
Public BaudBound website and container image |
BaudBound/repository |
Official BaudBound script repository metadata and packages |
BaudBound/.github |
Organization profile and shared public brand assets |
The contracts repository publishes reviewed contract revisions. The editor and runner include BaudBound/contracts as a Git submodule pinned to an exact commit. Builds use that pinned commit instead of downloading changing contract files.
When a contract changes:
BaudBound/contracts.This keeps builds reproducible while still making compatibility changes explicit in code review.
| Crate | Owns |
|---|---|
baudbound-script |
.bbs archive parsing, package documents, path validation, asset validation, and package models |
baudbound-security |
Permission and capability recalculation, risk, approval policy, and security validation |
baudbound-storage |
SQLite schema, installed packages, approvals, runs, variables, signals, and encrypted secret records |
baudbound-runtime |
Graph execution, templates, conditions, loops, variables, cancellation, reports, and redaction |
baudbound-actions |
Cross-platform action adapters and action-handler contracts |
baudbound-triggers |
Schedule, file, process, webhook, WebSocket, hotkey, startup, and serial listeners |
baudbound-core |
Validation and orchestration across package, security, storage, runtime, actions, and triggers |
The root baudbound package in the runner repository composes these crates and provides the CLI, Tauri host, desktop adapters, runner paths, service lifecycle, and update integration.
.bbs package.The installed baudbound executable hosts both the CLI and Tauri desktop application. Desktop UI calls cross the typed Tauri command boundary. The UI does not open SQLite or parse packages itself.
baudbound serve runs trigger listeners in the foreground for an external service manager. Independent CLI commands update durable SQLite state. A running service observes reload state and can also use the authenticated loopback control protocol for immediate stop and reload requests.
Configuration lives in config.toml. Installed scripts, approvals, runs, variables, and service state live in the runner data directory. See Storage, Backups, and Recovery for operator behavior.
Continue with Editor and Package Development, Runner Development, and Testing and CI.