Introducing Consort: Test-driven development on a branching database

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.

Takeaways

1. 1

   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.

2. 2

   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.

3. 3

   Consort separates role responsibilities: the code-writing role cannot alter tests, while a deterministic conductor routes work, enforces approval gates, and handles conflicts.