Maintaining an organizational knowledge graph with an LLM and event sourcing
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. At Arkency, I had a feeling that some things slip away from us too from time to time. Weekly calls, ad-hoc meetings, our book clubs, Slack discussions, GitHub mentions, e-mail inbox - we could use some support in organizing all those signals.
- ▪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.
- ▪At Arkency, I had a feeling that some things slip away from us too from time to time.
- ▪Weekly calls, ad-hoc meetings, our book clubs, Slack discussions, GitHub mentions, e-mail inbox - we could use some support in organizing all those signals.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,649 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Arkency Blog |
| Canonical URL | https://blog.arkency.com/maintaining-an-organizational-knowledge-graph-with-an-llm-and-event-sourcing/ |
| Publication time | Wed, 12 Aug 2026 16:56:43 +0000 |
| Retrieval time | 2026-08-12T17:11:37.332Z |
| Last seen | 2026-08-12T17:11:37.332Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Kc1SpzpRTSJp · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Piotr Jurewicz August 11, 2026 improve this article rails event store llm ai Maintaining an organizational knowledge graph with an LLM and event sourcing … and check why 5600+ Rails engineers read also this 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. At Arkency, I had a feeling that some things slip away from us too from time to time. Weekly calls, ad-hoc meetings, our book clubs, Slack discussions, GitHub mentions, e-mail inbox - we could use some support in organizing all those signals. Then Ruby Community Conference 2026 happened in March.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Arkency Blog.
Discussion
0 commentsMore from Arkency Blog
