Romeo and Juliet ↓
Verona. The feud is already running. The city holds it and is held by it. Two households. Five processes. One arc that cannot stop itself.
For the person who acts at the speed of feeling and calls it love.
A world built on the operating logic of Romeo and Juliet. Five processes follow the play's arc - Defy, Woo, Marry, Err, Grieve - but run independently. A session may enter at any point without completing the sequence.
Six positions shape the souls before any persona arrives: heir, enemy, lover, friar, messenger, bereaved. Romeo and Juliet share position_lover. Romeo and Tybalt share position_heir. The Nurse and the Prince share position_bereaved. Shared positions create structural pressure the world holds without resolving.
Five pieces carry the load: the family name, the vow, the letter, the poison, the dagger. The dagger passes from Romeo to Juliet in the tomb - the only piece that changes hands, and the only moment the world's final agent acts entirely on her own.
The world runs in Shakespearean English throughout.
Defy - stand where the name forbids it Woo - speak before the cost is counted Marry - make the thing irrevocable Err - act on what is believed, not what is true Grieve - move past the measure the city allows
Romeo - loves at the speed of replacement and cannot see it Juliet - applies clarity within a decision she has not inspected Friar Lawrence - builds architecture without load-bearing walls Nurse - loves the child and has no instruments for the woman Tybalt - serves the feud believing he serves honour Prince - governs retrospectively and calls it law
Shakespeare, Romeo and Juliet. c. 1594-1596. Public domain. The world is not a retelling. It is an engine. The five processes are structural, not story-specific - additional plays may be added as new persona, place, and piece files without altering them.
Kai Schlueter - KAI HACKS AI - 2026 CC BY-NC 4.0 KAI Worlds - github.com/ChBrain/KAIWorlds
README.md v0.1.0 - KAI Worlds / Romeo and Juliet