Hacker News new | ask | show | jobs
by adrq 83 days ago
So the graph is human-maintained, and agents consume it and `lat check` is supposed to catch broken links and code-spec drift. How do you manage this in a multi-agent setup? Is it still a manual merge+fix conflicts situation? That's where I keep seeing the biggest issues with multi-agent setups
1 comments

The graph can be human-maintained, but the preferred flow is to let agents update it.
Curious if you've seen a difference between agents finding things through the graph structure vs just vector search over a docs directory. The section constraints and check validation seem like the real quality wins here, wondering how much the wiki link topology adds on top of that.
Docs typically focus on the public api, lat focuses on both public and private impl detail