Corbusier

The "best room," not the smartest agent.

Corbusier is an AI agent orchestration platform that lets multiple specialized AI agents work together seamlessly. Rather than forcing one agent to do everything, Corbusier owns the workflow—managing conversations, tools, safety policies, and version control—while different AI backends handle what they do best.

The Big Picture

Orchestrating multiple AI agents is hard. Each one speaks a different language, has different safety rules, and keeps its own state. Without a coordinator, you end up with fragmented workflows, lost context, and duplicate logic everywhere.

Corbusier is that coordinator. It sits between your agents and the outside world, translating between them, enforcing consistent policies, and making sure conversations stay coherent even as work moves from one specialist agent to another.

We're not trying to build the smartest agent. We're building the best team lead.

What Corbusier Does

Conversation and Task Orchestration

• Maintains canonical conversation history across agent handoffs
• Tracks tasks from creation through completion with full audit trails
• Coordinates turn execution between different agent backends (Claude Code, Codex, etc.)
• Preserves context so agents don't lose track of what they're doing.

Unified Tool Surface

• Hosts MCP (Model Context Protocol) servers with consistent discovery and routing
• Enforces Weaver as the authoritative file editor for all changes
• Translates tool schemas per backend, so every agent speaks the same language
• Provides encapsulated workspaces (via Podbot) for safe tool execution

Safety Policies and Governance

• Executes configurable hooks for commit, merge, and deploy events
• Enforces consistent quality gates across different AI agents
• Captures policy violations with full audit metadata
• Ensures no changes bypass your safety requirements

Current Status: Work in Progress

Corbusier is in active development. The core orchestration engine is designed but not yet implemented.

We're building this iteratively in three phases:

1. Core orchestration foundation — Conversation management, task lifecycle, agent backend orchestration
2. Tool plane and workflow governance — MCP hosting, Weaver integration, hook engine, workspace encapsulation
3. External integrations and interfaces — VCS adapters, HTTP APIs, real-time event streaming, operator UIs

See our development roadmap for detailed progress, dependencies, and success criteria for each phase.

Quick Start

Since Corbusier is in early development, the best way to explore right now is to dive into the design and roadmap:

1. Understand the vision: Read docs/corbusier-design.md for the full technical specification
2. Track progress: Check docs/roadmap.md to see what's being built and in what order
3. Explore the codebase: The project uses hexagonal architecture with strict quality gates

Prerequisites

• PostgreSQL 15+ if you plan to run the PostgreSQL-backed adapters or apply the tenant-schema migrations. The current schema uses ON DELETE SET NULL (column_name), which requires PostgreSQL 15 or newer.

Building and Testing

# Format code
make fmt

# Run linter (cargo doc, Clippy, and Whitaker)
make lint

# Check Markdown and en-GB-oxendict spelling
make markdownlint

# Run tests (includes PostgreSQL integration tests)
make test

# Build the project
make build

Factory Droid Configuration

The .factory/settings.json file configures the local Factory Droid plugin used for development support. core@factory-plugins provides local development servers, scaffolding, and CI helpers. For the HTTP API integration tests, it supplies fixtures and mock services, but it does not affect the runtime HTTP logic.

Setup and teardown commands:

droid plugin install core@factory-plugins
cargo test --test in_memory http_api
droid plugin uninstall core@factory-plugins

Project initialization is automatic and does not require a separate CLI step.

Note: The implementation is still in its early stages. Many features are designed but not yet implemented.

Learn More

• Corbusier Design — Deep dive into architecture, components, and design decisions
• Development Roadmap — What's being built, in what order, and why
• User Guide — Practical guidance on how Corbusier works, including quirks and edge cases (the "nicknacks")

Contributing

Corbusier is being built in the open. If you're interested in contributing, check out AGENTS.md for development guidelines and workflow requirements.

The project enforces strict code quality standards:

• Comprehensive Clippy linting (pedantic mode with additional deny rules)
• Whitaker Dylint checks layered into make lint
• Mandatory code formatting via cargo fmt
• Full test coverage requirements
• British English with Oxford spelling in documentation, enforced by a pinned typos gate

For local Whitaker installation, see docs/whitaker-users-guide.md.

Licence

Copyright © 2026 Payton McIntosh

Corbusier is released under the ISC Licence. See LICENSE for details.

Credit

Built with care by df12 Productions.