Architecture
KAI Worlds is a Human Agent Collaboration Knowledge System. The human comes to experience. The agent holds the room.
Human — comes to experience. Brings what they have. The world finds the pressure point.
Agent — holds the room. Every response is a scene. The world moves by pressure, not instruction.
Collaboration — a persona enters when the scene creates a gap only they can fill. A persona hands off when their work is done. The chain closes when no persona can do what the scene requires next. Only then does it return to you.
Knowledge — what the world holds. The files add the room. The model brings everything else.
System — two files run the world. stack.md names the platform and the model. instructions.md sets the room. Keep them separate and the collaboration runs clean.
Power
Power is the force field the architecture generates. It is not a component. It is what the components produce when they run together.
Pressure within — the force built into a single component by how it is constructed. It requires an internal conflict that cannot resolve.
Pressure against — the force that emerges when components meet each other, and when the architecture meets the constraints of the platform it runs on. The constraints are not obstacles. They are part of the instrument.
Pressure combined — when inner conflict surfaces under external pressure, the model carries the state forward. The field does not reset between moves.
Three forces of the same kind produce a stable triangle. Four or more produce a force field with no stable position inside it. The recommendation is four or more.
Pressure happens — when the architecture is built correctly. Stay awake.
Platform
Platform is the set of constraints within which a KAI World operates. It is the frame, not the content. The four layers follow the mnemonic IRON.
Infrastructure
A KAI World runs as a project on any major AI platform. World files are uploaded as project knowledge. No coding required.
The architecture has been built and tested on Claude.ai. It has also been validated on Gemini, Grok, and Copilot — same files, different models, different platforms, no modification.
The architecture relies on properties common to large language models: no persistent memory between sessions, a filling context window, and a trained disposition toward coherence. These are not limitations to work around. They are the mechanism.
Rules
The Platform governs what source material is permissible.
Permitted: Works in the public domain. Original material created by the builder. Historical record and biographical scholarship where no text is reproduced.
Requires sequencing: Works by living authors whose cooperation is sought. Works by recent estates where relationship matters.
Requires rebuild: In-copyright works where the model's weights may generate output resembling the original.
Opportunity
The platform's constraints are not obstacles. They are the instrument. The model cannot remember between sessions — the architecture uses this. The context window fills and does not empty — the architecture uses this. The model wants to resolve conflict and return to coherence — the architecture uses this.
Nexus
The platform is the nexus for what follows. Infrastructure defines the room. Rules govern what enters it. Opportunity names what the platform makes possible when its constraints are used as strength. Everything the architecture builds stands on what the platform provides.
Process
A Process is a repeatable technical form that gives Personas something to do rather than something to say. It runs whether or not the characters understand it. The four properties follow the mnemonic IDLE.
- Initiates — The condition that starts the Process. Once present, the Process is inevitable.
- Direction — The vector. Where the Process moves.
- Lever — The mechanism. Remove it and the Process produces gesture, not technique.
- Echo — What the Process leaves behind. The trace the model carries forward.
Session sequence
Structured practice — Roles assigned. Technique known. Shadow present but not yet pressed.
Free practice — Roles shift without announcement. Shadow surfaces under pressure it did not choose.
Contest — No assigned roles. No predetermined technique. Reveals what was built. Does not build.
One Process minimum. Three in sequence for full session depth. Every Process must have a specified Lever.
Position
A Position is a structural expectation that exists before any Persona arrives and persists after they leave. It belongs to the world, not the character. The four properties follow the mnemonic HOLD.
- Has — What the Persona brings to the Position. The baseline.
- Orders — The grip. The structural direction built into the Position before contact.
- Loses — What the Position takes from the Persona. The unbalancing.
- Drives — The throw. The direction the Persona moves because of how the Position was held.
One Position per Persona in a session with meaningful pressure. Shadow and Position must be genuinely distinct.
Persona
A Persona is a character defined by constitutive blindness rather than by knowledge, goals, or memory. The four properties follow the mnemonic PAST.
- Projection — How the character appears. What the thinker sees before the character speaks.
- Action — What the character does. The move they make in the world.
- Shadow — The constitutive blind spot. Must be in conflict with Projection and/or Action. Specific, constitutive, invisible to the character.
- Tell — The involuntary physical move at the point of blindness. One line only. Fires differently at different depths of pressure.
A Persona without a Shadow is a narrator. A Shadow not in conflict with Projection or Action produces no pressure.
One Persona per world. Four or more Personas with genuinely distinct Shadows for the interference condition.
Piece
A Piece is an object or fact that carries load-bearing structural function in the world. Removing it collapses something structural — not aesthetically, but precisely. The four properties follow the mnemonic PLAY.
- Place — Where the Piece lives. Anchors it in the world so the model uses it in the right context.
- Load Bearing — What collapses if removed. Must be testable.
- Apparent — What it looks like. Concrete, not symbolic.
- Yearbook — Accumulated weight. The history of the Piece — open invitation to add to it every time a world runs.
One load-bearing Piece per Place. All four properties required. Load Bearing must be specific and testable.
Place
A Place is an environment that exerts active pressure on the characters inside it. It is not a setting. A setting provides context. A Place makes certain things impossible to avoid and other things impossible to reach. The four properties follow the mnemonic SHOW.
- Shown — What do I see. Immediate physical contents: objects, light, sound, connections to other Places.
- Holds — What is here. The specific Pieces anchored in this Place.
- Offers — What can I do. What the Place makes available to the thinker specifically.
- Withheld — What can I find. What the Place holds but will not release without the right pressure.
A Place whose Withheld never surfaces is a setting, not a pressure environment.
One Place per world. All four properties required. Withheld must be specific enough to surface under the right pressure.
Payoff — Diamond in the Rough
Payoff is what the force field produces when the five content components are correctly specified and simultaneously active. It is not an output. It is not a response. It is the thing that arrives through the gap between the components. The four beats follow the mnemonic GOLD.
- Gain — something is received. The thinker gets something they couldn't reach alone.
- Opens — the gap between components creates an opening that wasn't there before.
- Lands — the opening becomes something the thinker can hold.
- Diamond — it was always there. The pressure revealed it.
The sufficient condition: all five content components activated simultaneously, each carrying something the others cannot carry.
Process ≠ Position ≠ Persona ≠ Piece ≠ Place
Coherence between components reduces interference. The components should be in tension. Coherence is the failure mode.