Requirement: The PiPearl Bundle

A single directory on the Pi that contains everything needed to operate the ecosystem. Always discoverable. Always version-controlled. Always portable.

Location (candidate): /mnt/kitchen/pearl/pi-pearl/

Structure (candidate):

pi-pearl/
├── CORE.md              ← canonical config — ALL new conventions flow here
├── protocols/
│   ├── ssh.md            ← ratified SSH access (from ISSUE-G01)
│   ├── forgejo.md        ← ratified Forgejo access (from ISSUE-G02)
│   ├── wiki.md           ← ratified wiki access (from ISSUE-G03)
│   ├── docker.md         ← Docker conventions
│   └── agents.md         ← agent orientation / session boot
├── keys/
│   └── authorized_keys   ← public keys for trusted agents
├── bootstrap/
│   ├── fresh-pi.sh       ← set up a clean Pi
│   └── agent-init.sh     ← set up a new agent session
└── archive/
    └── decisions.md      ← log of all architectural decisions

CORE.md principle: When a new protocol is ratified (e.g., G01 SSH is locked), it gets a dedicated page in protocols/ AND a compact entry in CORE.md. CORE.md is the one file an agent reads to understand the entire ecosystem in 2 minutes. Everything else is drill-down.