[flagged]
Lore – Give your coding agent the decisions your team made
11–20 of 63 posts
Re: Lore – Give your coding agent the decisions your team made
#12Bad timing either way epic games release
Different beast — Epic's is version control, this grounds your agent in your team's decisions. Installs as rac either way, so the name's not load-bearing. But yeah, timing's a coincidence... just thought the name was cooler :D
Re: Lore – Give your coding agent the decisions your team made
#13I started building an app with similar goals but with the very different approach. I work on my own coding agent, https://github.com/brainless/nocodo , where I have been trying to build a provenance based engine that will generate or modify prompts to point to the decisions that a team has made. That work is in the branch: feature/praxis_agent_runtime While working on this I figured what if I build a proxy for coding…
I think the proxy angle is genuinely appealing for the reasons you give: team-level, no per-dev install, reshape every agent's context from one place. We went down that exact fork and chose against it (wrote up the reasoning as an ADR if you want it). Instead of intercepting and rewriting prompts/tool_calls, Lore does context-supply + post-edit enforcement.
Two things drove it:
One, a proxy that silently rewrites what the agent sees is hard to audit so you can't review an injection that never lands anywhere, and when it misfires you're debugging an invisible middle layer. We wanted the injected context to be a file in the PR diff (a generated CLAUDE.md/rules file) and the rest to be explicit read tools the agent chooses to call.
Two, and this is the part I'd flag for your index, the hard problem isn't delivery, it's knowing which decision is still current. An index built from git logs + tickets + PRDs is mostly stale or contradictory text; if a call got reversed six months ago, a fuzzy index will happily re-inject the old one. So that's where we spend the complexity budget: typed, human-reviewed decisions where "superseded" is enforced in CI, so the agent never gets handed a ruling you already overturned.
Which is why I think these compose rather than compete. Your proxy is a delivery mechanism; it still needs a trustworthy source for "the decisions this team made." That's what Lore is, and it exports for exactly this — rac export --documents (JSONL) or --graph to feed an index, --agent-rules for the injection layer. Stay fuzzy and convenient at recall, point back at a deterministic source for the part that has to be exactly right. Keen to see where praxis_agent_runtime goes — provenance-first is the right instinct.
Re: Lore – Give your coding agent the decisions your team made
#14Bad timing either way epic games release
Different beast — Epic's is version control, this grounds your agent in your team's decisions. Installs as rac either way, so the name's not load-bearing. But yeah, timing's a coincidence... just thought the name was cooler :D
LLM generated comments go against site guidelines.
Re: Lore – Give your coding agent the decisions your team made
#15Earlier quoted context omitted.
Different beast — Epic's is version control, this grounds your agent in your team's decisions. Installs as rac either way, so the name's not load-bearing. But yeah, timing's a coincidence... just thought the name was cooler :D
LLM generated comments go against site guidelines.
I wrote this, I just spend enough time with LLMs to sound like one
Re: Lore – Give your coding agent the decisions your team made
#16Re: Lore – Give your coding agent the decisions your team made
#17Re: Lore – Give your coding agent the decisions your team made
#18Earlier quoted context omitted.
I wrote this, I just spend enough time with LLMs to sound like one
Yeah every same human would use m-dashes in their sentences — it just makes sense
What? Em-dash is option-shift-hyphen on Mac... it's easy to use them. I used to use them. I even used to grab hair-spaces to place on either side of them, as one should (though that doesn't work on HN).
Re: Lore – Give your coding agent the decisions your team made
#19Seems a bit similar to spec driven development. How does it differ?
Re: Lore – Give your coding agent the decisions your team made
#20Seems a bit similar to spec driven development. How does it differ?
So the line shifts, but I see it as SDD manages the change (spec → tasks → ship, then archive it); Lore holds the durable decisions that every change after it has to respect.
think of it as a layer above SDD and not a competitor, so basically you point your spec tool at the constraints Lore enforces.