Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lore – Give your coding agent the decisions your team made

github.com

Post reply on HN
Print view View original

31–40 of 63 posts

Re: Lore – Give your coding agent the decisions your team made

#31

Post by kkkuuuuuu »

tcballard wrote: post #8
etoxin wrote: post #5

Earlier quoted context omitted.

Or spec-driven AI development.

Good questions! Lore isn't really competing with CLAUDE.md, it sits under it. A CLAUDE.md (or AGENTS.md, etc) is typically hand-written, untyped, and never checked. Nothing stops it from still telling the agent to do something you reversed six months ago, and nobody validates it in CI. Lore keeps the actual decisions/requirements/designs as typed Markdown in your repo, and rac export --agent-rules generates those rul…

everyone in ur life hates when you send them this claude output garbage

or am i the naive one, replying to a claudebot instance like its a human with thoughts and feelings that might care

Re: Lore – Give your coding agent the decisions your team made

#32

Post by tcballard »

vlindhol wrote: post #30
tcballard wrote: post #3

Author here! Coding agents kept reworking decisions we'd already settled - reviving an approach we ruled out in an ADR, redoing something a requirement already pinned. The context was in the repo; the agent had no current view of it. Lore serves your team's durable knowledge - requirements, decisions, designs, roadmaps, prompts - all as typed Markdown, read-only to Claude Code / Cursor over MCP, so the agent cites yo…

Hi! What I'm not quite getting from a cursory overview of the docs is how does RAC overlay overlapping decisions over each other? My mental model is a Docker overlay filesystem where RAC somehow manages to construct a cohesive view of the entire set of decisions over time, but how does that happen deterministically? Let's say ADR 1 specifies users are unique by e-mail and should be soft-deleted, and ADR 2 says users…

So rac doesn’t merge ADRs or infer that soft-deletes survive… supercession is managed by the status on one ADR saying Superseeded, and the other saying Supersedes. This is enforced by the CI pipelines you can use (GitHub, etc)

I think your example is a bit more of a modelling question, and if soft-delete must outlive the uniqueness decision it should be its own requirement that’s persisted as RAC guarantees the graph stays consistent and current; it doesn’t guess which clause survives — that’s the users call.

Re: Lore – Give your coding agent the decisions your team made

#33

Post by tcballard »

kkkuuuuuu wrote: post #31
tcballard wrote: post #8

Earlier quoted context omitted.

Good questions! Lore isn't really competing with CLAUDE.md, it sits under it. A CLAUDE.md (or AGENTS.md, etc) is typically hand-written, untyped, and never checked. Nothing stops it from still telling the agent to do something you reversed six months ago, and nobody validates it in CI. Lore keeps the actual decisions/requirements/designs as typed Markdown in your repo, and rac export --agent-rules generates those rul…

everyone in ur life hates when you send them this claude output garbage or am i the naive one, replying to a claudebot instance like its a human with thoughts and feelings that might care

I don’t follow - but appreciate the feedback, I’ll improve my comms about Lore / rac-core

Re: Lore – Give your coding agent the decisions your team made

#34

Post by isoprophlex »

tcballard wrote: post #8
etoxin wrote: post #5

Earlier quoted context omitted.

Or spec-driven AI development.

Good questions! Lore isn't really competing with CLAUDE.md, it sits under it. A CLAUDE.md (or AGENTS.md, etc) is typically hand-written, untyped, and never checked. Nothing stops it from still telling the agent to do something you reversed six months ago, and nobody validates it in CI. Lore keeps the actual decisions/requirements/designs as typed Markdown in your repo, and rac export --agent-rules generates those rul…

Please stop posting this self-aggrandizing llm drivel, it makes HN a worse place for learning and interesting discussions

You're either a bot, in which case piss off, or a bot-augmented human, in which case please tone down the bot augmentation and take the time to write less sloppy, more concise remarks

Re: Lore – Give your coding agent the decisions your team made

#36

Post by Cthulhu_ »

tcballard wrote: post #10
philbo wrote: post #9

1. Write ADRs (or get agents to write them) 2. Commit ADRs to git 3. Mention ADRs in AGENTS.md

I agree, that method might work if you are working solo or in a small team - but for organisations the ability to centrally manage and gate this sort of ruleset avoids drift.

You can manage ADRs centrally too, but you'll quickly need a dedicated sub-team / community / tribe / whatever to manage these thing.

Re: Lore – Give your coding agent the decisions your team made

#37

Post by Cthulhu_ »

LoganDark wrote: post #18
watermarkhu wrote: post #16

Earlier quoted context omitted.

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).

Yeah but a regular - is just a single button press, why would I learn this keyboard combination if I never learned how / when to use emdashes in the first place?

Re: Lore – Give your coding agent the decisions your team made

#38

Post by c3z_ »

great approach with dogfooding!

the failure I hit most is not that the agent forgets, it is that it re-opens things the team already closed. So treating ruled-out paths as first-class is the right instinct

quick question why mcp instead of cli tool? I'm mostly building the latter (less context burden), but help me understand your own ADR regarding this

why not both?

also after quick review on your doc I don't see where is ADR portal for humans? some plans for UX or this is inside git repo?

Re: Lore – Give your coding agent the decisions your team made

#39

Post by Cthulhu_ »

watermarkhu wrote: post #16
tcballard wrote: post #15

Earlier 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

Use triple emdashes to look extra sane⸻like this.
Post reply on HN