I found having smaller structured markdowns in each folder explaining the space and classes within keeps Claude and Codex grounded even in a 10M+ LOC codebase of c/c++
Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
11–20 of 70 posts
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#12Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#13I definitely agree with the need for this. There's just too much to put into the agents file to keep from killing your context window right off the bat. Knowledge compression is going to be key.
I saw this a couple of days ago and I've been working on figuring out what the right workflows will be with it.
It's a useful idea: the agents.md torrent of info gets replaced with a thinner shim that tells the agent how to get more data about the system, as well as how to update that.
I suspect there's ways to shrink that context even more.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#14So we are reinventing the docs /*/*.md directory? /s I think this is a good idea just don’t really get why would you need a tool around it
One of the things that I've been chewing on lately is the sync problem. Having a CI job that identifies places where the docs have drifted from the implementation seems pretty valuable.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#15At that point why not have an obsidian vault in your repo and get the Agent to write to it?
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#16> "chalk": "^5.6.2", security.md ist missing apparently.
good catch. Makes me wonder if we could feed the Agent with a repository of known vulnerability and security best practices to check against and get ride of most deps. Just ask _outloud_ so to speak.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#17[flagged]
I would say that when you treat your Markdown as the authoritative source, I of course don't get it automated but that is my choice. It takes knowledge of the domain, but when you have deep specific knowledge that is worth so much more than automated updates. I use AI to get the initial MD but then I edit that. Sure it doesn't get auto updated, but I would never trust advice on the fly that got updated based on AI output on the internet.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#18[flagged]
I would say that when you treat your Markdown as the authoritative source, I of course don't get it automated but that is my choice. It takes knowledge of the domain, but when you have deep specific knowledge that is worth so much more than automated updates. I use AI to get the initial MD but then I edit that. Sure it doesn't get auto updated, but I would never trust advice on the fly that got updated based on AI ou…
[flagged]
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#19At that point why not have an obsidian vault in your repo and get the Agent to write to it?
[deleted]
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#20We've been doing this with simple mkdocs for ages. My experience is that rendering the markdown to feel like public docs is important for getting humans to review and take it seriously. Otherwise it goes stale as soon as one dev on the project doesn't care.