Arkency iconArkencyAug 12, 2026 ~1 min source read

Maintaining an organizational knowledge graph with an LLM and event sourcing

Maintaining an organizational knowledge graph with an LLM and event sourcing Organizations are surprisingly good at forgetting. Decisions are made on calls, insights get buried in Slack threads, and a month later no one remembers why things are the way they are.

Share this story

Send the public story page.

Useful takeaways from this story.

Maintaining an organizational knowledge graph with an LLM and event sourcing Organizations are surprisingly good at forgetting.

Decisions are made on calls, insights get buried in Slack threads, and a month later no one remembers why things are the way they are.

Weekly calls, ad-hoc meetings, our book clubs, Slack discussions, GitHub mentions, e-mail inbox.

Building the complete brief

The page is ready to read now. The fuller skim-friendly version will appear here automatically.

The useful part

Maintaining an organizational knowledge graph with an LLM and event sourcing Organizations are surprisingly good at forgetting. Decisions are made on calls, insights get buried in Slack threads, and a month later no one remembers why things are the way they are. Weekly calls, ad-hoc meetings, our book clubs, Slack discussions, GitHub mentions, e-mail inbox.

How it works

  • we could use some support in organizing all those signals.
  • In Kraków, Obie Fernandez showed some parts of his NEXUS system.

Details worth keeping

Then Ruby Community Conference 2026 happened in March. He had already described it on his blog back in January, but the…

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app