| Persistent markdown wiki | Karpathy's core move is compiled knowledge that accumulates instead of being re-derived each time. | sources/karpathy-llm-wiki-gist/llm-wiki.md:11-13,31-53 | Personal knowledge bases, wiki maintenance, repository knowledge graphs, living documentation |
| Schema, governance, and kinship | A persistent wiki only stays coherent if page structure, relations, and update rules are explicit. | /workspace/repos/jgwill/llms-txt/llms-kinship-hub-system.md:33-69,75-100; /workspace/repos/miadisabelle/mia-awesome-copilot/AGENTS.md:58-107 | documentation schemas, knowledge governance, provenance, graph/ontology maintenance |
| Incremental ingest / query / lint | Karpathy's ingest/query/lint loop already rhymes with PDE + subagent orchestration + verification. | sources/karpathy-llm-wiki-gist/llm-wiki.md:35-53; /src/Miadi/rispecs/skills/rise-pde-session-multi-agents/SKILL.md:11-16,46-50,126-140,188-220; /workspace/repos/miadisabelle/mia-awesome-copilot/plugins/doublecheck/README.md:1-25 | multi-agent orchestration, documentation quality assurance, human-in-the-loop review |
| QMD as search/enrichment substrate | Current local evidence shows QMD already enriches PDE artifacts, but should not yet be treated as the only routing ontology. | /workspace/repos/jgwill/llms-txt/llms-pde.txt:120-152,195-198; /src/Miadi/rispecs/miadi-code/pde/pde-four-questions-pipeline.rispec.md:17-23,42-64,104-128 | semantic retrieval, repo-local search, hybrid BM25/vector wiki search, retrieval evaluation |
| Inquiry-routing and episodic continuity | Karpathy's pattern becomes more powerful when question lineage and answer promotion are preserved across sessions. | /workspace/repos/jgwill/llms-txt/llms-inquiry-routing.md:14-22,44-47,71-79,131-147; /src/Miadi/miadi-code/rispecs/pde-inquiry-routing.spec.md:23-41,67-76; /src/Miadi/rispecs/skills/mcp/04-ceremonial-memory.spec.md:33-41,66-81,89-119 | episodic memory for agents, session continuity, question routing, memory promotion pipelines |
| Kit vs suite packaging | The research needs to land as concrete agent/plugin/skill/package surfaces, not just design language. | /src/Miadi/miadi-code/references/claude/plugins.md:11-17,25-35,173-187,199-212; /src/Miadi/miadi-code/references/claude/sub-agents.md:143-171,181-208; /workspace/repos/miadisabelle/mia-awesome-copilot/plugins/context-engineering/README.md:1-27; /workspace/repos/miadisabelle/mia-awesome-copilot/plugins/structured-autonomy/README.md:1-20 | plugin ecosystems, subagent packaging, developer tool marketplaces, runtime composition |