Comment by skeledrew
14 days ago
> The database dictates the workflow, hands the LLM a highly constrained task, and runs external validation on the output before the state is ever allowed to advance.
This sounds like where lat.md[0] is headed. Only thing is it doesn't do task constraint. Generally I find the path these tools are taking interesting.
I looked into lat.md. They are definitely thinking in the same direction by using a CLI layer to govern the agent.
The key difference is the state mechanism. They use markdown; I use an AES-encrypted SQLite database.
Markdown is still just text an LLM can hallucinate over or ignore. A database behind a compiled binary acts as a physical constraint; the agent literally cannot advance a task without satisfying the cryptographic gates.
I just dropped the Show HN for it here if you want to check out the architecture: https://news.ycombinator.com/item?id=47601608