Viewing profile — 1st1

potentially. I'm toying with the idea of distributed lat ;)

- makes agent manage it for you in a controlled way - gives agent tools to search and traverse the graph, better than they can with grep - ability to have semantic links into your …

Not really. > Having a CI job that identifies places where the docs have drifted from the implementation seems pretty valuable. Testing with lat isn't about ensuring consistency of…

can you tell me more about what you mean by generative tests for spec conformance?

Docs typically focus on the public api, lat focuses on both public and private impl detail

I don't think this is related in any way.

Read this section, I've just updated it to be more clear, hopefully will answer your question: https://github.com/1st1/lat.md?tab=readme-ov-file#the-idea

One anecdote: I added lat to quickjs codebase and asked questions like "how does quickjs gc circular object graphs" and was able to get an answer in 12 seconds vs 2 minutes without…

I'm working on a blog post and on benchmarks. Here [1] Armin suggested I take something like quickjs, built lat base for it, and compare side by side how, say, claude code works wi…

++ > I suspect there's ways to shrink that context even more. Yeah, I'm experimenting with some ideas on that, like adding `lat agent` command to act as a subagent to search throug…

I think you can have your workflow with lat and it might make it even nicer. Would love feedback from you.

I think it's a great idea and I'm considering building this in lat too. Code embedding models can definitely speed up grepping further, but they still wouldn't help much when you h…

Because lat gives agents more tools and enforces the workflow. Unlike obsidian, lat allows markdown files link into functions/structs/classes/etc too. This saves agents time on gre…

I'm working on making lat hierarchical, e.g. - lat.md # high-level description of the project - frontend/lat.md # frontend-related knowledge - backend/lat.md # details about your b…

Fixed

Good idea. :) https://github.com/1st1/lat.md/commit/da819ddc9bf8f1a44f67f0...

> My concern is scale though. Once you have thousands of nodes the Markdown files themselves become a mess to navigate The agent will update the graph. If you have thousands of nod…

The problem is that for any non-trivial question agents have to grep A LOT to understand the high-level logic expressed in code. In big projects grepping can take minutes some time…

I'm working on a blog post about lat, stay tuned. Yes, it does work and I continue improving it.

The graph can be human-maintained, but the preferred flow is to let agents update 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 to…

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.

Creator 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, …

FWIW polymorphic schema and queries are trivial in Gel https://docs.geldata.com/reference/edgeql/select#polymorphic...