---
title: "Introducing Consort: Test-driven development on a branching database"
description: "Consort is introduced as an open-source agentic development framework for test-driven development on branching Lakebase Postgres databases. It addresses the limitations of mocks, shared staging databases, and risky schema-change ceremonies by bringing integration testing into the inner loop. Its build lane runs red/green/refactor cycles against isolated copy-on-write branches of real data, while versioned migrations keep code and schema changes together and pull-request checks test migrations against fresh branches. Consort organizes work through role-based agents and a deterministic conductor, preserving feature artifacts in dedicated directories and supplying scoped context packages. A VS Code plugin pairs Git and Lakebase branches, while an observability dashboard exposes agent turns and human approval gates; the project is community-supported rather than a bundled platform feature with an SLA."
---

# Introducing Consort: Test-driven development on a branching database

[Databricks](https://yomu.fyi/company/databricks) · Kevin Hartman · Sep 9, 2026

**Type:** Announcement

## Summary

Consort is introduced as an open-source agentic development framework for test-driven development on branching Lakebase Postgres databases. It addresses the limitations of mocks, shared staging databases, and risky schema-change ceremonies by bringing integration testing into the inner loop. Its build lane runs red/green/refactor cycles against isolated copy-on-write branches of real data, while versioned migrations keep code and schema changes together and pull-request checks test migrations against fresh branches. Consort organizes work through role-based agents and a deterministic conductor, preserving feature artifacts in dedicated directories and supplying scoped context packages. A VS Code plugin pairs Git and Lakebase branches, while an observability dashboard exposes agent turns and human approval gates; the project is community-supported rather than a bundled platform feature with an SLA.

## Context

Traditional development workflows treated the database as a rigid monolith, making real-database testing in the inner loop too expensive and encouraging mocks, shared staging, and cautious schema-change ceremonies. The source presents database branching as a way to move integration testing and regression detection earlier in development.

## Approach / What changed

Consort uses Lakebase branching as the foundation for an agentic test-driven build. It separates spec-first design from a build lane, runs tests against live copy-on-write database branches, coordinates specialized roles with a deterministic conductor, stores feature artifacts in dedicated directories, and provides scoped context packages, VS Code integration, observability, and human approval gates.

## Takeaways

- Copy-on-write branching creates isolated branches of a real database in roughly constant time regardless of data size, allowing destructive tests without affecting other team members.
- Versioned migrations let schema changes travel with the code that depends on them; pull-request and merge checks can apply migrations and run the full test suite on fresh branches.
- Consort separates role responsibilities: the code-writing role cannot alter tests, while a deterministic conductor routes work, enforces approval gates, and handles conflicts.

**Tags:** [AI Agents](https://yomu.fyi/topic/ai-agents), [Lakebase](https://yomu.fyi/topic/lakebase), [Open Source](https://yomu.fyi/topic/open-source), [Postgres](https://yomu.fyi/topic/postgres), [Testing](https://yomu.fyi/topic/testing)

- Source: [Databricks](https://www.databricks.com/blog/introducing-consort-test-driven-development-branching-database)
- Source URL: https://www.databricks.com/blog/introducing-consort-test-driven-development-branching-database
- Ingested by Yomu: 2026-09-09T16:05:05.871Z

[Read original post](https://www.databricks.com/blog/introducing-consort-test-driven-development-branching-database)