Git for Data:
Software — Code, configurations, tests
Knowledge — Articles, documents, knowledge bases
Research — Datasets, experiments, papers
AI — Prompts, Skills, Agents, configurations
Business — Strategies, workflows, reports
Creative — Designs, content, creative assets
🤖 Made with AI
1
16
腾讯云架构师北京同盟「作译者说」专题访谈
——为什么数据平台越成功,越难以为继?
数据团队不仅要证明自己的工作成果,还要不断证明自身存在的必要性。平台建设、数据治理、技术投入做了很多,却很难清晰地回答:究竟为企业创造了什么价值?
问题究竟出在技术,还是管理数据的方式?
19
Git’s deepest innovation is not just storing commits — it is the workflow around change: branches for parallel exploration, history for traceability, issues and PRs for human collaboration, and a distributed model for global contribution.
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
25
Data is the center of the universe; agents are ephemeral.
In the Agent era:
Software as fixed SaaS becomes redundant.
Agent dynamically synthesizes software capabilities on the fly.
Data & Context remain the only core, enduring asset.
I've actually stopped using the word "harness." I now think in terms of two things: agent runtimes and agent applications.
Agent runtimes should be very small. Their core job is to connect an LLM API to an execution environment. That environment could be a full OS or a language VM, like a JavaScript runtime. Almost all that matters here is robustness. An agent runtime must be able to keep an agent running forever. Literally forever.
Agent applications are everything else. Yes, literally every piece of software in the world.
If software isn't built for agents, they use it through computer use or browser use. These capabilities can be built into the agent runtime or provided by another agent application.
If software is agent-native, agents should be able to use it directly. The experience of an agent using that software—what we call "agent experience"—needs to be carefully designed, at least for now, to make efficient use of both time and tokens.
Another key piece is agent identity. Agent applications should recognize each agent individually, rather than just the browser or computer it's using. This allows each agent's actions to be recorded in detail and audited in real time or after the fact.
Everything we're building at @botiverse follows from this view.
31
As a team building at the intersection of Git + Data + AI, we have to recommend this article.
It’s one of the most worthwhile Git guides we’ve come across — not because everyone needs to become a Git expert, but because understanding Git changes how you think about building.
1
1
74
What if Agents could branch data and run experiments against it? @sspaeti explains here:
ssp.sh/blog/git-for-data-the…
Branch the data
→ Let Agents experiment against it
→ Test on real data
→ Compare results
→ Deploy what works
→ Roll back when needed
1
38
The key idea is not just versioning data.
It’s giving Agents a safe, reproducible environment to experiment against real data — without copying massive datasets every time.
Metadata → zero-copy → delta → full copy
1
19
Want to understand how Git For Data works in practice?
Check out this deep dive by @sspaeti comparing Git-like tools that separate metadata from data:
ssp.sh/blog/git-for-data-too…
It covers:
1. LakeFS
2. Dolt
3. Nessie
4. MotherDuck
5. Neon, Supabase, Bauplan & more
no GitDataAI😂
Branching, isolation, reproducibility and merge are becoming fundamental primitives for data infrastructure — and even more important as AI agents begin to work directly with data.
This is exactly the direction we’re exploring with Git+Data+AI.
Thanks Simon for mapping out!
Engineers care about two things in production, says Ciro Greco from Bauplan: downstream consumers never see corrupted data, and nobody debugs failures under pressure.
His answer is git for data. No job writes to production tables directly.
1
2
65
GitData.AI retweeted
Engineers care about two things in production, says Ciro Greco from Bauplan: downstream consumers never see corrupted data, and nobody debugs failures under pressure.
His answer is git for data. No job writes to production tables directly.
Models are no longer the bottleneck for AI automation. Domain knowledge is.
@TomBlomfield nailed it: Every company’s know-how is trapped in Slack, email, and human memory. To run on AI, businesses don't need another chatbot.
They need a Company Brain. 🧠👇
1
1
82
Undo via Git Revert.
When an Agent makes a mistake or context gets poisoned, you don't re-prompt and pray.
You git revert. One click rolls the Company Brain back to the last known stable state. Deterministic safety guaranteed.
1
9
The race for enterprise AI isn't about training bigger foundation models. It’s about building the operational layer to govern domain knowledge.
Tom Blomfield defined the vision for the Company Brain. @GitDataAI is building its Git-Native OS. 🚀
7











