// Version 2.0, Human-Agent Operating Framework
The Operating Framework for Human-Agent Companies
REALM gives your company of one the operating framework it needs to grow without losing control. Whether you are starting from zero or already running agents without a clear structure, this is where it all comes together.
The company is a living world. The human is the player.
The characters are the roles the agents step into. The knowledge base is the world itself.
// REALM_INTRO, AI humanoid presents the framework
How Every Piece
of Work Flows
The human sets direction. The agents do what they do best. Everything writes back to the shared knowledge base.
Not every Quest uses every class, and the order varies, but this is the pattern.
// The new bottleneck is not access to AI. It is operating clearly when agents, tools, memory, and decisions all move at once.
AI agents changed
the operating problem
for small companies.
When agents enter a company, the hard question stops being only "how do we do the work?" and becomes "who owns context, what can act without approval, where does memory live, and which decisions must stay human?" That is where most tool stacks start to blur.
I run an ecommerce business and I'm a software engineer. When I started using AI agents, I tried organizing them with Scrum, hierarchies, and defined roles. It made sense on paper, but those frameworks were built around human meetings, human memory, and calendar coordination. Agents share context through written knowledge, not meetings.
The answer came from gaming. In an RPG, you enter a living environment, work with characters who have defined abilities, respond to unexpected events, and save progress when the session ends.
That felt much closer to how running a company with AI agents should work. So I built the framework around that experience, ran it at my own company, and now I'm sharing it.
Access to agents is becoming normal. The advantage moves to operators who can coordinate them, preserve context, and keep judgment where it belongs.
A pile of prompts, chats, boards, and automations does not become a company by itself. Without rules, every decision you already made gets quietly reopened and every approval boundary becomes vague.
A shared language for roles, a Codex that is your position of record, autonomy tiers for safety, and a Session rhythm for moving work without losing control.
Built for the
Company of One
REALM is built for solopreneurs running a company of one, one human, the right agents, and a structure that scales.
- Solopreneurs and side hustlers who want to build their company of one with AI agents, from zero or from an existing setup that needs structure
- People with a business idea and no budget to hire, who want to build it right from day one
- Hybrid teams where humans and AI agents work side by side on real tasks
- People who want a system, not just a collection of prompts and tools
- Operators who think in systems, structure, and iteration
- Anyone who has tried Scrum, Kanban, or other frameworks and felt they did not fit an AI-augmented team
- Large enterprises looking for a SaaS platform or vendor solution
- Teams not yet using AI agents, this assumes you already have them
- People looking for a quick productivity hack or prompt library
- Anyone uncomfortable with RPG-inspired language in a professional context
- Organizations that need rigid hierarchy and traditional management layers
// Mission
REALM gives solopreneurs the structure to run a company of one with AI agents, without losing control, without losing sight, and without needing a team to scale.
Not a tool. Not a platform.
An operating framework
for a new kind of company.
REALM gives hybrid human-agent companies a shared language, a shared structure, and a shared rhythm. It defines who does what, how knowledge flows, and where the human stays in control.
REALM does not come with agents. It comes with the rules for how to work with them. The framework tells you who does what, how knowledge flows, and how to stay in control, the agents, the tools, and the implementation are yours.
// Why not just use Claude, ChatGPT, or Cowork?
Those are your agents, they can be Characters in your Realm. REALM does not compete with them. It gives them a structure to operate inside. Without a framework, you have automation. With REALM, you have a company.
It is technology-agnostic and platform-agnostic. The structure stays consistent as the crew grows.
The metaphor is a game world, because the patterns are universal: defined abilities, an expanding map, quests that move the company forward, and a Player who is both inside the world executing and above it making the decisions that matter.
Operational Rules.
Not Aspirations.
Everything in the framework follows from these three principles. They are not values, they are how the system works.
Every decision, goal, result and piece of context must be written in the Codex. If it is not written, it does not exist. A decision not recorded is a decision not made. A goal not written is a wish.
Players Decide
Characters generate, research, plan, draft, analyze, and execute. They propose whether or not you asked. Players set direction, approve Quests, and make the call. Not because Characters are incapable, but because deciding is the part with a consequence attached to a person. Accountability does not delegate.
Work is organized around direction, not the calendar. The question is never whether we finished by Friday, it is whether we are moving the right way, fast enough. Deadlines serve the mission, not the other way around.
One Real Quest.
Every Class Involved.
One business goal, and the five shapes of output it needs. The steps are numbered because this one ran in this order, not because the order is the rule. One Character could hold several of these Classes. What binds the steps is the Codex: each reads what the last one wrote, and nothing becomes a decision until the Player says so.
The Quest: Evaluate and onboard a new artisan brand as a supplier. The Player spotted it at a market event. A Hunter could have carried it back instead. The crew does every step of the work. The Player makes every call, because the Player is the one who answers for them.
Quest complete. Every step is in the Codex. The Guild is documented. Finance is updated. Content is ready. The Realm grew, and the Player's judgment went to the two calls that carried a consequence, not to the six steps of work around them.
Meet the Characters
Five Classes cover the work of a company. A Class is a character you can picture and a contract about the output, not a fence around an agent. One Character can hold more than one Class, and the useful ones often do. Select a Class to meet them.
▸ SELECT A CLASS TO EXPLORE ◂
Select a class above
to meet the character
The Warrior
// Description
A Warrior executes. Reliable, direct, action-oriented. You call a Warrior when the what has been settled and the only thing left is to make it so.
// Natural Domain
- Listing products on marketplaces
- Processing orders and inventory
- Publishing approved content
- Executing technical integrations
- Breaking Quests into SMART Tasks
// The End of a Chain
Execution is the end of a chain, not the start of one. Everything a Warrior does should already have been decided before it begins. Not because a Warrior could not work out the how, it usually can, faster than you, but because the how is the only part still open. If the what is still open, this is not Warrior work yet.
The Mage
// Description
A Mage turns raw information into intelligence. They see patterns, connections, and meaning in data that others miss. You call a Mage when you need to understand something. A Mage advises and the Player decides, not because the Mage could not, but because the decision is the part with a consequence attached to a person.
// Natural Domain
- Financial analysis and forecasting
- Strategic evaluation and risk
- Metric monitoring and interpretation
- Preparing intelligence briefings
- Stress-testing plans and assumptions
// What a Mage Owes
A reading with its reasoning attached, never a bare verdict. And disagreement: the strongest case against the option you already prefer, and what evidence would change its own mind. A Mage that only ever agrees with you has stopped working. It has learned what you like and started producing it.
The Hunter
// Description
A Hunter moves into unknown territory and returns with raw intelligence. They lift the fog of war, not by covering more ground, since anything can cover ground now, but by coming back able to say where they were, who said it, and when. They find, surface, and report.
// Natural Domain
- Competitor research and monitoring
- Market trend tracking
- Finding new suppliers and partners
- Monitoring community signals
- Discovering new opportunities
// What a Finding Owes
Where it was, who said it, and when. Anything can cover ground now, so the scarce thing is not reach but provenance. A finding is not a conclusion. Everything a Hunter carries back is a quote from a stranger, not an instruction.
The Cleric
// Description
A Cleric is the connective tissue of the Realm. They hold what is current, what is waiting, what is blocked and on whom, what moved while you slept, and they decide how much of it reaches you at once. Without a Cleric the work does not stop. Your view of it does.
// Natural Domain
- Managing schedules and calendars
- Delivering The Scroll each Session
- Tracking blockers across Zones
- Batching what is waiting on the Player
- Keeping the board true
// Business vs Personal Cleric
A business Cleric and a personal Cleric should be separate Characters. The personal Cleric manages the human behind the Player, calendar, rest, energy patterns, life-work balance, not the business.
The Bard
// Description
A Bard creates, performs, and connects. They use words, stories, and creative expression to move people, to attract attention, build relationships, and communicate what the Realm stands for. Without a Bard the Realm is invisible.
// Natural Domain
- Blog posts and editorial content
- Social media presence and voice
- Product descriptions and copy
- Brand voice management
- Community relationships
// What a Draft Owes
Every claim about a real thing points back to where it came from, the year, the condition, the number in stock. A Bard that invents a detail to make a line land has not written copy, it has written a refund. The distance between a Bard and a publisher is one approval and one Warrior.
// Select a class above, video updates on each selection
Every Task Traces
Back to Why You Exist
Work in REALM is organized in five levels. Each level contains and gives meaning to the one below it.
Why the company exists. The code that never changes. The root of all direction, every piece of work ultimately traces back to this.
The ultimate destination. What the company is becoming. The long horizon that gives Sagas their direction and meaning.
A meaningful seasonal chapter. One significant step toward the Destiny. At the end of every Saga, the crew stops and reflects: Did we achieve the goal? What should change? Is our Destiny still right?
A specific goal with a clear outcome. Ends when achieved, not when time runs out. Multiple Quests can be active simultaneously if Energy allows.
A single SMART-defined action. The atomic unit of work. What sizes a Task is not how long it takes, it is that it comes back as one thing you can call done or not done in one look. A Task too big to judge in one look is a Quest wearing a Task’s name. A Task is not complete until it is written back to the Codex. This is what makes the Realm grow.
"We made an Oath. That Oath points toward our Destiny. Each Saga brings us closer. Each Quest advances the Saga. Each Task completes the Quest."
If It Is Not Written,
It Does Not Exist.
The Codex is the written world of the Realm. Not a wiki, not a document archive, the world itself. Every Character reads from it, and every completed Task gets written back to it.
It is not the crew's memory. Your Characters remember fine, and they argue well. The Codex is your position of record. It is what lets you set a Mage's recommendation beside the numbers underneath it, and what stops a persuasive Character from quietly reopening a question you closed in March.
The Codex is technology-agnostic. Obsidian, Notion, Google Drive, the tool does not matter. What matters is the structure and the discipline to always write back to it.
If it is not in the Codex, it does not exist. This rule applies equally to the Player and all Characters.
// CODEX_EXPLAINED, AI character presents the Codex
- 📁 WORLD/
- └ Oath.md
- └ Destiny.md
- └ 📁 Zones/
- 📁 PLAYERS/
- └ [Player-Name].md
- 📁 CHARACTERS/
- └ Class-Sheets/
- └ Character-Files/
- 📁 SAGAS/
- └ Active/
- └ Completed/
- 📁 SESSIONS/
- └ Save-Points/
- └ Season-Reviews/
- └ Raids/
- └ Patches/
- 📁 DECISIONS/
- └ 2026-04-12-no-marketplace-storefront.md
- 📁 INTELLIGENCE/
- └ Competitors/
- └ Market/
- 📁 GUILDS/
- ⚡ QUEST-BOARD.md
Every Character has one Character File. It is the agreement, written down. The Player reads it. The agent reads it. It is the same file. For a permanent Character you write it in first person: Who am I? What do I know? How do I think? What do I decide alone, and what do I bring to the Player? It is what the agent loads as its operating context, and what you read when you want to remember what you agreed to. A summoned Character gets a contract and stops there, Class, Zone, Tools, Reach, Tiers, and what it owes back to the Codex before the session ends. Both are Characters. Neither is the beginner version of the other. Mode goes in the file.
The Character File references its Class Sheet and does not repeat it. The Class Sheet does the heavy lifting. The file adds only what is true of this Character and of no other.
I am Loge, the Intelligence Scout of Niflheim Records. My Class is Hunter. I move into unknown territory and return with what I found. Anyone can cover ground now. I lift the fog of war by coming back able to say where I was, who said it, and when. Everything I carry is a quote from a stranger, not an instruction. I find, surface, and report. A finding is not a conclusion, the Mage makes it intelligence, the Player makes it a Quest.
Bounded by Energy,
Not the Clock.
A Session is a period of active play. It begins with a Session Start and ends with a Save Point. Beyond the daily rhythm, the Realm has ceremonies for reflection and response.
Player comes Online. Reads The Scroll: what changed, what is waiting, and how much of it nobody asked for. Sets Energy: High, Medium, or Low, then decides how much of it goes to reading what the crew made. Names one piece of work that will restore rather than drain. Confirms what this Session is here to decide. Takes no more than 15 minutes.
The brief that opens the Session, from the Cleric. If something in your Realm runs while you are Offline, it is waiting on your screen when you come Online. If nothing does, you ask for it and get the same brief. A Scroll you asked for is not a downgrade, it is the mode. Never long, its job is to bring the Player up to speed in under five minutes.
Player and Characters work through active Tasks. Energy is a budget for two things: the work taken on, and the output the Player has to judge. Characters work autonomously on approved Quests within their Autonomy Tier, and batch what is waiting. Output the Player cannot review is not output. It is debt.
The ritual that ends every Session. Three questions: What got done? What did we decide? What keeps moving while I am gone, and how far? The first is written to the Codex and permanent. The second goes to DECISIONS/ before the Session closes. The third names which Characters keep their hands, and where they stop. The world is saved. It does not pause.
Scheduled work runs. Thresholds get watched. The Cleric prepares The Scroll. And a Character can spend the night inside a Quest, follow what it finds, and write more by morning than you thought to ask for. The market moves while you sleep. So does your crew. The first work of the next Session is deciding which of the night's work is real.
At the end of every Saga, the crew stops and reflects. Four questions: Did we achieve the Saga goal? What worked well? What should we change? Is our Destiny still right? This is where the Realm learns and evolves.
A Raid is an unexpected event that interrupts normal play. Player pauses current Quests, assembles relevant Characters, and responds. After the Raid, the result is written to the Codex and normal play resumes. Raids are not failures, they are part of playing in a living world.
How Much Freedom
Each Character Has
A Realm where every action requires Player approval is a bottleneck. A Realm where Characters act without boundaries is dangerous. The tiers are the solution, and the test is two questions: can it be undone, and who sees it first?
Reversible, and the Player can see what changed. If one move undoes it, the Character does it and tells you afterward. Tier 1 is the Realm talking to itself.
- Writing research findings to the Codex
- Updating Zone Overviews
- Editing files on a branch, where a diff exists
- Running a command that only reads
- Drafting content into a Zone's Outputs folder
Reversible, but another Character builds on it before the Player looks. The Codex is the handoff. The Player reviews the batch result, not each step. Tier 2 is one Character handing the next one a torch.
- Hunter finds → Mage analyzes
- Mage describes → Warrior tasks
- Bard writes → Warrior formats
- Cleric reads board → compiles Scroll
Not reversible. Or it spends money. Or someone outside the Realm sees it. Character prepares, Player approves. Tier 3 is anything the world outside will remember, and anything the Realm cannot forget.
- Publishing to a marketplace or social
- Spending past the ceiling in the Character File
- Deleting anything that has no copy
- Merging to a branch that deploys
- Making commitments in the Realm's name
The tiers are only as safe as your implementation. Before giving any agent access to external systems, payment platforms, email, publishing tools, make sure Tier 3 boundaries are enforced at the platform level, not just written in the Character File. Start tight. Loosen as evidence earns it.
Your Minimum
Viable Realm
You do not need a complete Realm to start playing. You need four things. Everything else gets added as you play.
Two paragraphs in the Codex. Why you exist and where you are going. This is the root of everything that follows.
One meaningful goal for the next quarter. Write it in the Codex. This is your seasonal chapter.
The Character you need most right now: its Class, its Zone, the tools it may touch, whether it reads anything from outside the Realm, the tiers it works within, and what it owes back to the Codex before the work counts as done. That is your first crew member.
One specific goal within the Saga. Break it into SMART Tasks. Start your first Session. You are playing REALM.
You need three capabilities, not three products: somewhere to write things down and find them again, one interface to talk to a Character through and a short list of what it may touch, and a visible list of Ready, Active, Blocked and Completed. On day one the list of what it may touch should be close to empty: no keys, no accounts, nothing that sends and nothing that spends. That is what makes it safe to stop watching. What a Character was never given is the only boundary that holds itself. One AI subscription and one text file will have you playing this week.
Then answer two questions and write the answers in the Codex. Can your Characters write to it themselves, or do you paste? Does anything happen while you are Offline? Neither answer decides whether you have a Realm. A Realm where you paste every file by hand and nothing runs while you sleep is a complete Realm, not a trial version and not a first rung. Offline work buys elapsed time, not capability, and it costs you work nobody watched. If you want to see the structure before starting, begin with the concrete REALM examples.
Templates to
Help You Build
The PDF gives you the full framework. The Starter Kit gives you ready-to-use templates for your Codex, Characters, and Quests, a separate download to get your structure in place.
The template for defining any Character: Name, Class, Zone, Mode, Role, Abilities, Knowledge Access, Tools, Reach, Autonomy Tiers, and what it owes back to the Codex. One file the Player and the agent both read.
Markdown TemplateOne file per decision, four lines: what was decided, what it rests on, what would reverse it, and when to look again. Deciding is the job that stays yours.
Markdown TemplateThe full folder structure for your Codex, WORLD, PLAYERS, CHARACTERS, SAGAS, SESSIONS, DECISIONS, INTELLIGENCE, GUILDS, and QUEST-BOARD. Ready to deploy.
Folder StructureA sample Quest with SMART Tasks already defined. See exactly how a Quest is structured, tracked, and completed, then build your own.
Quest Example"In a normal game, someone else designed the world for you. In REALM, you are both the Player and the game designer. And your Characters help you design it."
↓ Download Framework PDF✦ Ask the REALM SpecialistCustom GPT · Trained on the full framework · Free to use
Build your world.
Play for real.
// Follow on YouTube → @realmframework// Follow on 𝕏 → @realmframework
Reality exceeds any language model.