Codifide Gregario
greh-GAH-ree-oh. In Italian road cycling, the gregario is the rider who works for the team leader. Codifide Gregario is a commercial product that governs a coordinated swarm of AI agents. It is private, in development, and not generally available.
What it is
The free Codifide Direttore harness governs an agent, or several concurrent sessions each in its own git worktree, working one codebase. Codifide Gregario is the separate, private product built on top of it for the next case: coordinated lanes of agents working across many codebases or business entities in parallel, with frozen seam contracts between lanes, per-lane verifiers, merged-state integration verification across the lanes, and a human making the decisions at every gate.
The idea is the same as Direttore’s, applied at a larger scale. Machines do the mechanical work at machine speed. Reviewers challenge it. People decide. The framework behind both is described on the Codifide Direttore page, including what is mechanically enforced and what agents are only instructed to follow. Gregario carries the same honesty standard: where a rule is only a convention, we say so.
Status
- Private and in development. It is not generally available and there is no public download.
- No release date and no pricing are published.
- No outcome data is published. This page makes no claim about results, speed-ups, or savings, because there is no study to support one.
Who it is for
The intended audience is operating partners and engineering leaders who are responsible for several software estates at once, for example a portfolio assembled through acquisitions that needs to be consolidated onto fewer platforms. If you are one engineer who wants governance for your own coding agent, the free Direttore harness is the right place to start.
What it adds beyond the free harness
The public description of the commercial layer is in the harness README. In short, it adds:
- portfolio-scale decomposition of work into parallel lanes;
- frozen seam contracts between lanes;
- per-lane verifiers;
- merged-state integration verification across lanes and entities;
- connectors.
Some of the underlying ideas are already public and free for a single codebase: isolating each concurrent session in its own git worktree, sharding session state, and, if you have a test suite, running it against the merged result. They are described in Running Multiple Sessions Concurrently and in the announcement.
What it does not claim
- It does not claim that you can point a swarm at an estate and have it modernize itself. Every entity has quirks. Discovery and mapping need people who know the business.
- It does not claim that agents can verify their own correctness. Verification is the hard part, and the framework assumes it needs independent checks and a human decision.
- It does not claim to be a compliance certification or a substitute for legal, security, or regulatory review.
How to engage
Codifide is open to conversations with prospective design partners: people who run several software estates and want to talk about whether this approach fits. Nothing is promised in advance. There is no sign-up form and no third-party booking tool. Write to us, say which estate or portfolio you have in mind, and we will reply by email.
Email about Codifide Gregario: info@codifide.com
Other ways to work with Codifide are on the Work with Codifide page.
Informational only. Not legal, medical, regulatory, security, or compliance advice. Provided as is, without warranty. See Notices.