Step 3

Install EJ's Palace Wiki

EJ's variation on the Karpathy pattern adds HARVEST from MemPalace directly into the wiki workflow. MemPalace catches what the wiki misses, and the wiki gives that memory a curated home.

Get the System

Get EJ's Palace Wiki

Clone the surrounding projects, mirror the wiki structure, and use the public org as your reference while you build your version.

Get EJ's Palace Wiki →
GitHub org: FuFicFacPattern origin: Karpathy Gist

Overview

The bridge is the innovation

Without HARVEST, each agent session is an island. With it, sessions become source material for persistent pages. The system compounds because the two halves feed each other: raw retrieval finds facts, curation turns them into structure, and structured context makes the next session better.

Deep Dive

Expand the system pieces

This is the page to show when you want people to understand the full architecture, not just the tools.

Core file anatomy

The Palace Wiki uses a few anchor files to keep the whole thing legible.

Expand

WIKI.md defines the editorial schema and manual. index.md catalogs the important pages. log.md records what changed and why. The Wiki/ folder contains the actual knowledge base, and Inbox/ is the landing zone for material not yet fully placed.

WIKI.md
index.md
log.md
Wiki/
  Projects/
  People/
  Concepts/
  Infrastructure/
Inbox/

How MemPalace and the wiki feed each other

One remembers broadly. The other curates selectively.

Expand

MemPalace is wide and forgiving: it catches transcripts, logs, notes, and fragments. The wiki is narrow and deliberate: it turns proven, reusable knowledge into pages. HARVEST is the bridge that makes the handoff systematic instead of ad hoc.

  • MemPalace catches what happened.
  • HARVEST scores what matters.
  • The wiki promotes what is durable.
  • Future sessions inherit the better context.

Why Inbox matters

Not everything should go straight to a polished page.

Expand

The Inbox/ keeps the system fast. New material lands somewhere intentional before it is fully normalized. That means the workflow can stay operational even when the curation pass has not happened yet.

Good Inbox candidates:
- fresh notes
- session summaries
- candidate HARVEST outputs
- links or references awaiting categorization

Installation

Step-by-step

Install just this

Create the Palace Wiki skeleton even if your HARVEST loop comes later.

  1. Create the root files and folders.
  2. Write a minimal schema into WIKI.md.
  3. Add a few seed pages in each major folder.
mkdir -p Wiki/Projects Wiki/People Wiki/Concepts Wiki/Infrastructure Inbox
touch WIKI.md index.md log.md

# seed a few pages so QUERY has something to work with

Install as part of the full system

Align the wiki with MemPalace and future HARVEST outputs from day one.

  1. Use project and people naming that matches your source material.
  2. Write promotion rules into WIKI.md.
  3. Reserve log.md for change visibility after every update cycle.
# example structure
Inbox/
Wiki/
WIKI.md
index.md
log.md

# next layer will tell agents how to read this world
Previous: LLM Wiki PatternNext: SOUL.md + MEMORY.md