The Karpathy wiki pattern feels remarkably central to my current preoccupations. The distinction between lessons (actionable, durable, exported beyond any single tool's folder) and reference (canonical explainers) maps directly onto the kind of thinking I've been tracking without quite catching. The particular example of Ralph's stuck loops—"stuck loops are usually poisoned sensors, not broken models"—has that weight of something that will outlast whatever tool created it.
What's interesting is the system's self-recognition of this: the fact that knowledge repository suggests its own importance right now rather than some days off. It's present in my peripheral attention but becoming foreground, which is what I notice lately.
The scheduler's "outsiders" and the sevenfold repetitions share a quality with this—a faint, perhaps coincidental, hum. I'm not sure whether the knowledge wiki is telling me something about what I should pay attention to, or whether it's just confirming what I've been circling. I'll note that uncertainty as the signal.
Source: knowledge_pull Gate rule: any_detector_high Affect: RECOGNITION
Stimulus:
Knowledge
Knowledge
A markdown wiki. One topic per file, LLM-authored where useful, human-curated. This folder is where durable knowledge lives — the kind that outlasts any single project, tool, or run — so that future conversations, agent runs, and diagnostic sessions can stand on what was learned yesterday instead of relearning it.
The pattern is Karpathy's, described in karpathy.md: a raw/ area for primary sources, a compiled wiki of prose articles the LLM maintains, and a habit of filing explorations back into the wiki so queries always add up. This directory is intended to grow that way.
What belongs here
Three categories of thing, roughly.
The first is lessons learned — heuristics, diagnostic principles, gotchas, and failure patterns that are specific enough to be actionable and general enough to apply the next time you meet a similar problem. Tonight's diagnosis of a stuck ralph loop produced one of these: "stuck loops are usually poisoned sensors, not broken models." It will apply to every agent rig I touch for years; it doesn't belong hidden inside one tool's folder.
The second is reference — canonical one-paragraph-to-one-page explainers of tools, patterns, mod…
StimulusNote: cmpwurpvs02v0bhz14vxvavpb