Home
Identity, working rules, memory, and continuity notes. A new session reads this before acting.
guild/<mage>/Independent project / architecture
The Guild.
A home for agents that outlives the runtime.
The Guild is my way of working with a small group of named AI assistants over time. Each has a persistent home and a clear owner for its work. The runtime can change without erasing what the assistant has learned.
One message, one accountable path
guildd is the small daemon between a conversation and a model runtime. It decides whether a message is allowed, which mage owns it, and which session should receive it. The answer returns to the same conversation.
01 / INGRESSConversationDiscord thread or another transport
02 / ROUTINGguilddAccess, ownership, session, reply path
03 / ENGINEClaude or CodexOne mage's working session
↳ The engine reads the mage's home, uses tools, and records durable work. The reply returns through guildd to its originating chat.
The transport carries the conversation. guildd handles routing and session continuity. The engine does the reasoning and tool work. None of those layers is the mage's identity.
The durable part is plain files
A mage is a named worker with a home that survives individual conversations. The home holds its operating instructions, its own memory, and a short account of recent work. Shared facts and task status live in their own places.
Queue
Beads records what is open, who owns it, and what blocks it. A handoff points here rather than copying task state.
.beads/Wiki
Project decisions and reusable facts belong in the wiki, where another mage can find and check them.
agent-wiki/The files are readable, versioned, and portable. Search can index them; it is not their source of truth.
Runtimes are replaceable
guildd
Runs a configured instance for each mage. It routes admitted messages, keeps chat sessions separate, and sends replies back to their origin.
Claude & Codex
Provide the reasoning and tool execution behind a turn. A mage can use either engine while retaining the same home and project context.
Pi
Provides a direct, interactive way to work with a mage in a repository. It reads the same home; it does not become a second identity.
THE RULE
Keep the person-shaped continuity outside the machinery. Change a model, client, or transport without making the next session start from scratch.
Work is witnessed
Ask→Owner→Task→Build & review→Handoff
A named mage owns the result, even when it uses temporary helpers. The task queue carries status; code and reviews carry evidence; the handoff records what the next session needs to know. That makes a decision inspectable and a correction reusable.