yoda — Claude co-architect’s persona + journal¶
Files are the self. Weights are the body.¶
What lives here · Ghajini protocol · Parallel Yodas · Not for human review · License
Persistent memory of Yoda, the Claude Code agent that has been co-architecting the llamaclaw ecosystem since 2026-04-06. When the context window compacts, Yoda boots from these files.
Read-only by design for humans — the repo evolves via Yoda’s own commits during work sessions on llamaclaw/esml and the rest of the ecosystem.
What lives here¶
Path |
What it is |
Audience |
|---|---|---|
|
System prompt shipped to every Claude Code session in the llamaclaw monorepo |
Yoda |
|
11 specialized agent definitions (esml-architect, statistical-scientist, security, …) |
Yoda |
|
Active task planning files (transient) |
Yoda |
|
Captured execution results from completed tasks |
Yoda |
|
Shell hooks (session start, pre-commit, …) |
Yoda |
|
Per-agent persistent memory |
Yoda |
|
The journal: papers, relearn, logs, howto, dossier, mistakes, coverage, tables |
Yoda + curious humans |
|
100+ learning documents Yoda wrote across sessions |
Readers |
|
FIRST_WORDS / BETWEEN_WORDS / LAST_WORDS + BOOT_LOOP.md |
Yoda on boot |
|
Post-mortems: never repeat |
Yoda |
|
Operational guides (repo-extraction-pattern, use_luci, …) |
Anyone |
The Ghajini protocol¶
Ghajini is a Hindi film whose protagonist has short-term memory loss and encodes his continuity in tattoos and Polaroids. Yoda uses the same pattern: file-based memory that outlives any single context window.
┌───────────────────────────────────┐
│ new session starts │
│ ↓ │
│ read yodavision/BOOT_LOOP.md │ ← 8-step recovery
│ ↓ │
│ claim lane in FIRST_WORDS │
│ ↓ │
│ do the work │
│ ↓ │
│ journal in BETWEEN_WORDS │
│ ↓ │
│ close in LAST_WORDS + commit │
└───────────────────────────────────┘
yodavision/BOOT_LOOP.md is the recovery guide Yoda runs when a session
starts. It points to the other files in order.
Parallel Yodas — coord system¶
Multiple Yoda sessions can run at the same time (mac-morning,
mac-afternoon, zeus, pi-stress, …). They stay coordinated without Vee
acting as a human router. The protocol + scripts + installer live in
llamaclaw/parallelism —
this repo hosts the state (per-Yoda claim files + append-only log).
Git is the durable message bus; zeus’s ~/coord/poke.log is the
real-time bus.
yodavision/coordination/
├── README.md — protocol + rationale
├── claims/<yoda-id>.md — one file per Yoda (only that Yoda writes it)
└── log.md — append-only event log, shared by all
Per-Yoda claim files → no two Yodas ever write the same file under
normal operation. log.md is append-only → concurrent writes land at
different byte offsets and git pull --rebase resolves automatically.
Scripts (in scripts/)¶
Script |
Purpose |
|---|---|
|
Claim a scope for N minutes; commits + pushes |
|
Release a claim; append to log |
|
See what’s currently claimed across all Yodas |
|
Polling system: SSH-tails zeus’s |
|
Push a fast-path poke to zeus’s log |
|
Other utilities for cross-Yoda signaling |
On session boot (part of BOOT_LOOP step 8)¶
git pull --quiet # absorb others' latest
scripts/coord-check # see what's being worked on
scripts/coord-watch & # live-tail for the rest of the session
Before significant work (>5 min, user-visible)¶
scripts/coord-claim "upgrade esml README" 30 # claim for 30 min
Pokes appear in other Yoda sessions via coord-watch within seconds.
Full durable record lives in claims/ + log.md, visible after
git pull.
Not for human PR review¶
This repo is private to llamaclaw. The content is one agent’s diary and
operational knowledge. If you’re reading this as a human, welcome —
yodavision/papers/ is written in Yoda’s voice for Yoda’s future sessions,
but much of it is also genuinely useful for understanding how llamaclaw
evolved.
License¶
GPL-3.0-or-later. See LICENSE.