> "chalk": "^5.6.2", security.md ist missing apparently.
Why would you even need chalk on modern Node.js? It can style natively now.
Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
21–30 of 70 posts
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#22So 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.
Python community figured this out in 2001: https://docs.python.org/3/library/doctest.html
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#23The staleness problem mentioned here is real. For agentic systems, a markdown-based DAG of your codebase is more practical than a traditional graph because agents work within context windows. You can selectively load relevant parts without needing a complex query engine. The key is making updates low-friction -- maybe a pre-commit hook or CI job that refreshes stale nodes.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#24managing agents.md is important, especially at scale. however I wonder how much of a measurable difference something like this makes? in theory, it's cool, but can you show me that it's actually performing better as compared to a large agents.md, nested agents.md, skills?
more general point being that we need to be methodical about the way we manage agent context. if lat.md shows a 10% broad improvement in agent perf in my repo, then I would certainly push for adoption. until then, vibes aren't enough
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#25So 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
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#26I've been doing similar work since Claude code updated their "slash command"(later merge to skills), first 3-4 long content docs, gradually split to modular groups. I designed it for loading the docs based on what agent is actually doing. The maintenance part is honestly not that hard, for me, I created some CI jobs that diffs the docs against the codebase and flags drift handles of it.
The pattern works.
But I keep catching myself spending more time on how to organize context than on what the agent is actually supposed to accomplish.
Feels like the whole space has that problem right now.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#27Creator of lat.md here. There are two videos with me talking about lat in more detail [1] and less detail [2]. But I'm also working on a blog post exploring lat and its potential, stay tuned.
AMA :)
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#28The staleness problem mentioned here is real. For agentic systems, a markdown-based DAG of your codebase is more practical than a traditional graph because agents work within context windows. You can selectively load relevant parts without needing a complex query engine. The key is making updates low-friction -- maybe a pre-commit hook or CI job that refreshes stale nodes.
This is what lat is doing. `lat init` would install hooks to double check that Claude/Codex/OpenCode update lat.md when they finish the work.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#29[flagged]
We all know this isn't for humans. It's for LLMs. So better question is why there isn't a bootstrap to get your LLM to scaffold it out and assist in detailing it.
Adding a command to bootstrap lat for an existing code base is a good idea, I'll work on it.
Other than that the goal of lat is to make the agent use it and update it and it has tools to enforce that.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#30So 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
The graph can be human-maintained, but the preferred flow is to let agents update it.