Consort

Consort keeps AI-written code clean and correct: spec-first and test-driven, driven by a deterministic state machine with human-approval gates and immutable tests. Engineering discipline is no longer left to chance at the whim of a model. Every green is a real test run on a live branch of a real Lakebase database, enforced by contract, not suggestions.

Consort takes its name from the field of music. A *consort* is an ensemble that plays in concert: each musician holds one part, and a conductor keeps them in time. Consort is that, applied to building software. A set of agents each take on one familiar role from the software lifecycle — a spec author, an architect, a DBA, a test strategist, a UX designer, and a navigator/driver pair at the keyboard — while the product owner is the human's own seat (you, or a Human Proxy standing in headless), a deterministic conductor keeps them in sequence, and the human approves every gate. No agent plays another's part.

What Consort builds. Consort builds transactional application backends (an API, and optionally a web UI) on Lakebase, Databricks' serverless, Postgres-compatible OLTP database that branches in about a second. Every git branch is paired with its own Lakebase branch, so each has a real, isolated database and the schema evolves in lockstep with the code. It isn't for the Delta Lakehouse, ETL, analytics, or BI; it's for building app backends on Postgres. See docs/positioning.md for how Consort compares to other spec-first tools.

Quick start

Setting up Consort is easy. Copy the command below and enter it into any terminal window.

Then, run /consort:start in your agent session. Getting started has the prerequisites and a full walkthrough.

Why Consort

AI agents write code fast, but you can't trust that the code is…