Independent use will determine whether Stigmergy provides teams and their LLM agents with a practical shared persistent knowledge base rather than merely a single-user memory tool.
state: expiredheat: lowuncertainty: highknownscott: lowagent-memory knowledge-systemsStigmergy
What is this?
Stigmergy is presented in a Show HN title as a “Karpathy-style LLM wiki” intended to serve a team rather than one person. The supplied results establish the broader need for shared, persistent, governed knowledge that multiple users and agents can access, but provide no direct details about Stigmergy’s implementation, maintainers, adoption, or independent evaluation. Whether it works as organizational memory rather than merely personal agent memory therefore remains an unverified hypothesis.
Why it matters to Scott
Scott already holds and builds the core position that a team’s durable agent memory should be a maintained wiki-graph rather than a single-user transcript store, notably in “Wiki Is the Kernel,” “Institutional Memory,” and dev-wiki. The radar also already tracks this thesis on “Karpathy-style LLM Wikis will gain sustained adoption”; with no implementation details or independent results, Stigmergy is currently another unverified example rather than evidence that extends or challenges it.
ip:framework.wiki-is-the-kernelip:concept.institutional-memoryip:framework.the-index-is-the-data-self-cleaning-wiki-graphdev:project.dev-wikiradar:karpathy-llm-wiki-adoptionradar:concept.agent-memoryradar:concept.knowledge-systems
queries asked of Scott's wikis
- agent-maintained wiki shared across teams
- multi-agent persistent organizational memory
- shared Markdown memory for coding agents
- governance and permissions for agent knowledge
- agent memory versus RAG knowledge base
- independent evaluation of knowledge-system utility
Measured heat
no measured readings yet — the hourly heat pass fills this in
How the heat travelled
no chain yet — the hourly chain pass fills this in
Evidence (1) — ⭐ canonical anchor
Interpretation history
2026-08-27T00:29:55Z
After 48 hours the launch still has no discussion, independent use, or implementation evidence. It has faded as an unvalidated example of Scott’s existing team-wiki thesis, with no reason to keep an active episode open.
2026-08-24T23:31:02Z
The forced re-evaluation found no new usage, implementation detail, or independent validation; Stigmergy remains an unverified example of the existing team-wiki thesis rather than new evidence for it.
2026-08-24T23:28:44Z
grounded: known/low — Scott already holds and builds the core position that a team’s durable agent memory should be a maintained wiki-graph rather than a single-user transcript store
2026-08-24T23:25:10Z
case created — The released GitHub project is a concrete team-oriented agent-memory artifact, but it has not yet attracted independent validation or adoption evidence.
Decision trace
- 08-27 10:29expireAfter 48 hours the launch still has no discussion, independent use, or implementation evidence. It has faded as an unvalidated example of Scott’s existing team-wiki thesis, with no reason to keep an a
- 08-27 10:29alert_silentNo consequential delta occurred and no confirming fact is expected imminently; revive only if independent adoption, architecture details, or team-utility results appear.
- 08-27 10:29alert_routeNo consequential delta occurred and no confirming fact is expected imminently; revive only if independent adoption, architecture details, or team-utility results appear.
- 08-25 09:31repriceThe forced re-evaluation found no new usage, implementation detail, or independent validation; Stigmergy remains an unverified example of the existing team-wiki thesis rather than new evidence for it.
- 08-25 09:31alert_silentNothing consequential changed: the launch remains at one point with no comments or independent evidence, so revisiting it in a briefing would add no value unless adoption, architecture, or team-utilit
- 08-25 09:31alert_routeNothing consequential changed: the launch remains at one point with no comments or independent evidence, so revisiting it in a briefing would add no value unless adoption, architecture, or team-utilit
- 08-25 09:29alert_silentA low-engagement Show HN link establishes that another team-oriented LLM wiki implementation exists, but supplies no implementation details, independent use, or results that extend Scott’s existing th
- 08-25 09:29alert_routeA low-engagement Show HN link establishes that another team-oriented LLM wiki implementation exists, but supplies no implementation details, independent use, or results that extend Scott’s existing th
- 08-25 09:28groundScott already holds and builds the core position that a team’s durable agent memory should be a maintained wiki-graph rather than a single-user transcript store, notably in “Wiki Is the Kernel,” “Inst
- 08-25 09:25createThe released GitHub project is a concrete team-oriented agent-memory artifact, but it has not yet attracted independent validation or adoption evidence.