This is exactly what I did earlier this week. There are some available garden management tools out there, but they are very limited, and mostly aimed at larger farm-like situations. I also have a small orchard and a vegetable garden, and a spreadsheet felt almost as much work and less flexible than letting Claude build something bespoke. (Also, I absolutely abhor spreadsheets) Since I didn’t plant everything myself, I even included a feature to make a photo, and ask Claude all the basic questions about it. It then stores all that information into the “knowledge base”. I can add to the same KB manually whenever I buy new seeds or get crops. I’m now letting it work on a visual representation of my yard, so it’s easy to work with. Took me a couple of evenings in total on the cheapest plan (I’m not in a hurry). It helps that I’m a software engineer by trade, which allowed me to make tons of decisions myself, guiding it more strictly. My recommendation to those that are not is to ask it to present you with decisions in a multiple-choice format, with good explanations of each answer. That makes it easier to get started even with little experience.

I’m not sure exactly. It could be related to how the AT protocol also takes account information into federation, but I’m just speculating here

The big added benefit is that its federated using the AT protocol. So while you join a local instance (or, knot), or even set one up yourself, you still get all the benefits that GitHub currently provides around making coding social and discoverable, unlike other alternatives like forgejo. So it’s not doing anything to git itself, but rather the layer on top, the forge