These concepts become relevant as your Realm matures. They are not needed to start playing, but they are how a Realm evolves from a starting setup into a living system.
A Patch is a deliberate update to how the Realm works. A new process, a new rule, a new Character, a new way of running Sessions. Any Character can propose a Patch. Only the Player can approve and release it. After a Patch, the Codex is updated to reflect the new reality. This is how the Realm evolves intentionally rather than drifting.
The Bard has been publishing consistent social media content for a full Saga. The Player decides approval before each post is no longer necessary. The Bard proposes a Patch: move content publishing from Tier 3 to Tier 2. The Player approves, the SOUL file is updated, and the Codex records the change.
A Guild is a relationship with another player outside your Realm — a supplier, collaborator, or partner. Guild relationships are not employment. They are alliances. Each Guild is documented in the Codex with its terms, its value, and its status. When the relationship changes, the Codex is updated immediately.
A new artisan brand agrees to supply products. The Cleric creates a Guild file in the Codex documenting the partnership terms, delivery schedule, and contact workflow. Every Character who touches that supplier's products can now reference the Guild file for context.
REALM is designed for multiplayer. When a second human joins, they become a Player in their own Zone — with their own Energy, their own Character roster, and their own Session rhythm. The Codex connects all Players. The Oath and Destiny are shared. The PLAYERS/ folder scales naturally from one to many.
A co-founder joins to run Marketing. They get their own Player Card, their own Energy tracking, and their own Characters. They share the same Oath, the same Destiny, and the same Codex — but they play their own Sessions at their own pace.
The Codex distinguishes between writable fields (updated directly by the Player or Characters) and derived fields (calculated from underlying data, owned by a specific Character). If a derived field is manually changed in a way that contradicts the source data, the responsible Character detects the drift and flags it for correction.
The Mage owns the revenue total in the Finance Zone. If someone manually edits that number, the Mage detects the mismatch against the underlying transaction data and flags it — just like a GitOps controller correcting configuration drift.
A Character that has been running for six months, with a refined Codex and tested interactions, is not the same as a newly created one. As trust builds and Characters prove reliable, their Autonomy Tier can shift. A Character that started at Tier 3 for content publishing might move to Tier 2 after a Saga of consistent quality. This evolution is always a Patch — documented, deliberate, and written to the Codex.
REALM is platform-agnostic by design. It layers on top of any agent infrastructure — OpenClaw, AutoGPT, or custom setups. The platform handles how agents wake up, remember, and connect. REALM handles what they do, who they are, and how work flows. The SOUL file is the bridge: a platform-specific file written in REALM language.
For the full details on each concept, download the REALM Framework PDF.