Keeping teams on one AI harness
The question behind the question When a team asks "how do we keep everyone on the same setup," what they're really asking for is the thing every other part of their stack already has: one answer to what are we running, who's on it, and when did it change. Package managers gave them that for dependencies. The instructions, skills and permissions steering their AI agents still run on folklore, and that's configuration that writes code into their repos every day.
- ▪The question behind the question When a team asks "how do we keep everyone on the same setup," what they're really asking for is the thing every other part of their stack already has: one answer to what are we running, who's on it, and when
- ▪Package managers gave them that for dependencies.
- ▪The instructions, skills and permissions steering their AI agents still run on folklore, and that's configuration that writes code into their repos every day.
Opening excerpt (first ~120 words) tap to expand
The question behind the question When a team asks "how do we keep everyone on the same setup," what they're really asking for is the thing every other part of their stack already has: one answer to what are we running, who's on it, and when did it change. Git gave them that for code. Package managers gave them that for dependencies. The instructions, skills and permissions steering their AI agents still run on folklore, and that's configuration that writes code into their repos every day. Give it the same machinery. Version it, pin it, distribute it by pull request, and measure adoption instead of asserting it. That's the whole answer, and it's boring on purpose. The manifest spec is open at github.com/baselane-sh/harness.json.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at baselane.
Discussion
0 commentsMore from baselane
