Interop: shared knowledge base → Egregore memory/
Direction: Copy from this Mapmakers knowledge base into the private Egregore memory repo (the-mapper-s-ego-memory, memory/ in the-mapper-s-ego). Destinations must stay the standard Egregore memory/ layout — add no nonstandard top-level folders.
Repositories: this Mapmakers-Knowledgebase · Egregore: egregore.json → memory_repo.
A publications export is separate — see PUBLICATION-AND-RELEASE.md.
Path map (this repo → memory/)
| Shared KB source (this tree) | Egregore memory/ destination | Notes |
|---|---|---|
3 - Knowledge/patterns/*.md | knowledge/patterns/*.md | Copy/merge; add private frontmatter in memory as needed. |
| Decision in shared KB | knowledge/decisions/YYYY-MM-DD-topic.md | DEVELOPMENT.md |
3 - Knowledge/… findings | knowledge/findings/… | |
0 - Housekeeping/Guides/* or long writeups | artifacts/… or knowledge/patterns/* | One canonical home. |
2 - Projects/* | projects/*.md | |
1 - People/*.md (humans) | Summarize to people/{github}.md as needed | No duplicate personas/ tree in memory/. |
4 - Guild/ops/personas/* (agent packs) | Avoid a separate ops/ tree in Egregore — distil into people/{github}.md or a pattern note. | |
infrastructure (if you add) | infrastructure/ | No secrets. |
| — | handoffs/, wraps/, quests/, meetings/, research/ | Egregore-native; private record stays in memory. |
How to pull in
- Copy from this clone into
the-mapper-s-ego-memory/… - Fix frontmatter per Egregore subfolder.
- Skills (
/save,/add, …) remain the app’s interface. - Optional:
source: Mapmakers-Knowledgebase/<path>in the private file.
What not to do
- Do not symlink this whole repo into
memory/. - Do not use
personas/folders inmemory/. - Shared → Egregore: keep content appropriate for
memory/when you copy; redact or trim private detail and off-bundle link targets the same way you would on a publish pass (Publication doc).