Advanced Concepts
These concepts become relevant as your Realm matures. They are not needed to start playing. They are what you reach for when you feel the lack of them, and not before.
The Patch
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 approves and releases it, and the Codex is updated to match. Autonomy Tiers move only by Patch, and every Patch names the evidence that earned the move. Count the run, not the calendar. When a Character rewrites its own Character File, that is a Patch too: proposed like any other, approved like any other, written down like any other. No Character quietly redraws its own contract. This is also how trust grows. There is no separate leveling system, because leveling was only ever the Patch under a second name.
The Bard has published for a full Saga. It proposes moving publishing from Tier 3 to Tier 2 and names the run: forty-one posts, two Player edits, both cosmetic, nothing rolled back. "The Bard is good now" would not have been evidence. The Player approves, the Character File is updated, and the Codex records what the move was bought with, so there is something to read before moving it back.
The Guild
A Guild is a relationship with another player outside your Realm: a supplier, a collaborator, a partner. Guild relationships are not employment. They are alliances, documented in the Codex with their terms, their value, and their status. A Guild file is the one place where an outsider's words become terms your own crew works from, so nobody writes it but the Player. When a partner sends new conditions, that mail is a finding with a name and a date on it, not an edit. A Hunter carries it back. A Mage tells you what it costs. The Guild file changes when you say it changed. A supplier does not get write access to your world by sending you an email.
A distributor gives you first refusal on limited pressings, and the terms go in the Codex, so every Character who touches that stock works from the same agreement you made. Six months later the distributor mails a new minimum order. The Hunter files it with the date and the sender. The Mage prices it against last season. You decide, and then the Guild file changes.
Multiplayer
REALM is designed for multiplayer. When a second human joins, they become a Player in their own Zone, with their own Energy, their own Characters, and their own Session rhythm. The Codex connects all Players, and the PLAYERS/ folder at the root scales from one to many without changing shape. Zones are owned individually, and inside their Zone a Player decides. The Oath and the Destiny are shared, and shared is not the same as jointly held. Somebody swore that Oath. When two Players read it differently, that person answers for the reading, and the Codex says who they are on the first line of WORLD/. Two people, one Oath, and no name on it is not multiplayer. It is a committee that has not admitted it yet.
A co-founder joins to run Marketing. They get their own Player Card, their own Energy, their own Characters, and they play their own Sessions at their own pace. Inside Marketing, their call stands. When the two of you disagree about what the Oath asks for, the name at the top of WORLD/ settles it, and the decision goes to DECISIONS/ like any other.
Agent Platforms
An agent platform is anything that can hold or summon an agent. A hosted agent service. A workflow tool. Your own scripts on a schedule. A chat window with a saved instruction file. A coding agent pointed at a repository is an agent platform too: it boots an agent, hands it tools, and lets it read and write files. That is the entire job description. The platform handles how an agent wakes up, what it remembers, and what it can reach. REALM handles what it does, who it is, and how work flows. The Character File is the bridge, written in REALM language and put where the platform looks for it. Deploying takes two kinds of thing, and only one of them is writing. The other is the powers: the keys it holds, the scopes on its token, the branches it can push to, the ceiling on what it may spend.
Deploy is where the file and the powers have to agree. A Tier 3 written in a Character File, running over a key that publishes without asking, is not a boundary. It is a wish with good grammar. Give that Character the credential that drafts and not the one that posts. Platforms will change, and some of the ones you use today will not exist in three years. You will not lose the Realm when they go, because the Realm was never in the platform.
For the full details on each concept, download the REALM Framework PDF.