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.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,263 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | baselane |
| Canonical URL | https://baselane.sh/blog/keeping-teams-on-one-harness/ |
| Publication time | Mon, 20 Jul 2026 09:03:34 +0000 |
| Retrieval time | 2026-07-20T10:35:38.006Z |
| Last seen | 2026-07-20T10:35:38.006Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | D1imwoyjfdwf |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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
