Pi

Personal cognitive augmentation system. Five orthogonal layers that cooperate without overlapping.

The Layers

Access	Name	Purpose
tb (CLI + HTTP)	Third Brain	Semantic memory: ideas, concepts, connections. Additive associative graph with hybrid search and hubs. Notes are never deleted; refs and tags can be updated.
th (CLI)	Third Hand	Agent orchestration with de Bono hats. Project members, sequential and parallel flows, bwrap sandbox.
.wiki/ (Omero skill)	Third Wiki	Local project wiki: pages, style guides, code conventions. Plain markdown, maintained by Omero. Lives and dies with the project.
ti (CLI + HTTP)	Third Identity	Context→behavior rules: what to do in a given situation. Dedicated Qdrant collection, same shape as tb.
tl (REST, planned)	Third Log	Unified structured event log shared by th/tb/ti. Founded, not yet implemented.

Agents

Agent	Role
annibale	Agentic debate: viewpoints made on the fly, one synthesis
piano	Debates what a project or feature is for: writes .design/main.md
feynman	Teaches the TB corpus with the Feynman technique
socrate	Generates cognitive friction: finds contradictions and gaps, never closes
aristotele	Curates TB syntheses: hubs, missing connections, clusters
christopher	Retrieves knowledge from the TB without interpreting
polo	Extracts text from URLs (web articles and YouTube)
indiana	Code archaeology: diagnoses patterns and technical debt
efesto	Creates and improves skills
omero	Maintains the local project wiki in .wiki/
linus	Manages GitHub via gh: issues, project board, recaps
clio	Backs up Qdrant to MEGA cloud: snapshots, restores, timer

Full, always-current roster (derived from the filesystem at print time):

python3 skills/efesto/scripts/roster.py

Setup

./setup.sh

Requires bun. Installs the tb, th, ti symlinks in ~/.local/bin/, links the identity (alfred.md) and the skills/ directory into both ~/.claude/ and ~/.pi/agent/, links the tb_ti extension (automatic tb/ti context injection) and the systemd user services for the tb/ti HTTP APIs.

---

The Ritual

The system works only if used consistently.

During work — Alfred + th

Before answering on a topic that might be in the TB:

tb search "<topic>" --depth 1

For a judgment with trade-offs that benefits from several viewpoints: Annibale runs a debate. Read its SKILL.md and follow it. To extract content from URLs or videos: Polo.

On a project — Omero

Omero maintains the local wiki in .wiki/ — plain markdown pages, style guides and code conventions. Delegate to Omero to ingest material, ask about the project, or document how the code is written. The skill operates on the files directly.

End of session

td distils the session into tb and ti at the start of a later session. Nothing to do by hand. If the work was on a project with a wiki: Omero updates .wiki/.

Periodically — Aristotele

When the TB starts to feel dense (every 2-4 weeks): Aristotele creates hubs and connects isolated notes.

---

The fundamental distinction

Third Brain (tb): ideas that have value beyond the project — principles, patterns, cognitive tensions. No code blocks, no detailed technical documentation.

Local wiki (.wiki/, via Omero): project-specific documentation — commands, flows, architecture, conventions, lore. Lives and dies with the project.

The two systems complement each other, they do not overlap.