What it's for. And what it's up against.
Two ways in. The first is the job you're trying to do; the second is the constraint that makes it hard. Every page below names the plugins it rests on — and the site build refuses to publish a claim no shipping plugin backs.
What are you trying to do?
The job first, the mechanism second. Each of these composes several plugins into one outcome.
An agent can open thirty pull requests an hour. The gate is what decides which of them are safe to merge.
tbzl · forge · fleet · builds · Polyglot Read more →Every repo has a pipeline file nobody fully understands. The build graph already knows what to do — so stop describing it twice.
tbzl · builds · registry · forge Read more →The first day of a new engineer's job should not be a week of installing things that were already installed on someone else's laptop.
workspaces · ws-proxy · Polyglot · depot Read more →Turning agents on is a one-line change. Deciding what they may touch, whose authority they carry, and how you stop them is the actual project.
chat · forge · fleet · Polyglot · mycelium Read more →What are you up against?
Not industries — shapes. A regulated estate and a high-volume monorepo are different problems whatever sector they sit in, and the constraint is what actually decides the architecture.
When every change has to survive an auditor, evidence collection stops being a project and starts being a property of how work already happens.
Compliance · forge · tbzl · depot · builds Read more →Some estates can't send their build plane to a vendor. The whole platform launches into your own AWS account instead.
workspaces · registry · builds · ws-proxy · forge Read more →If the source is the asset, then every tool that touches it is a disclosure decision — including the ones you turned on to go faster.
chat · forge · Polyglot · depot · ws-proxy Read more →At a hundred merges a day, testing everything is too slow and testing the diff is too little. The graph knows which answer is right.
tbzl · builds · registry · forge · depot Read more →Every claim names its plugin.
Each solution above cross-references the features it rests on, and the build fails if one of them isn't shipping. Browse the 14 plugins directly if you'd rather start from the mechanism.