simhacker/moollm/soul-city

Soul City

Reusable place prototype — rooms, roads, shops, tools, objects, plazas, vehicles. Souls walk here (soul).

Human entry: README.md → SOUL-MODEL.md

Inspiration: Will Wright's 1996 Stanford lecture, where he named data portability as the thing he was working on and then demoed an unreleased Dollhouse by loading a SimCity city into it — lecture notes.

Grain

flowchart TD
    soul["skills/soul/: continuity body, zero or more minds"]
    city["skills/soul-city/: rooms, shops, tools"]
    map["Instance map: concrete rooms, roads, plazas, shops"]
    inhabitant["Soul + minds + character; bridges to other games"]
    soul -->|Instantiate / compose| map
    city -->|Instantiate / compose| map
    inhabitant -->|Inhabit| map

Contents

• Rooms, roads, maps, plazas — spatial index
• Shops, tools, objects — city affordances
• Vehicles — movable inhabitables
• Souls — citizens and visitors; each authors its mind graph
• Parties — multi-soul travel

Cross-game

Souls may bridge to characters, personas, and minds in other games. Each game keeps its own organization — one mind per game, as an organelle, in that game's own format, unflattened. incarnation — grant and author architectures.

Two kinds of crossing at a save-file border, and they are different primitives:

The act is transmigration, not import/export — souls are travelers, and most are refugees (delisted games, retired servers, formats locked on purpose), so the statuses that apply are the ones borders use: traveler, expat, immigrant, refugee. Never cargo.

Identity rule: fork and sync, never transport. Both sides stay alive; shared fields sync; the soul is saved before any ending is played. Conservation means nobody vanishes at the border, and no soul is returned to a world that can no longer hold it.

Media pages are a separate interoperability layer: capture and caption do not require a save parser, although capture availability and permissions still apply. Pages use Dublin Core metadata and form a graph. Linear albums, slideshows, and books are selected routes through that graph, not its only storage structure. Users can also author pages without a source game.

Planned content tools consume pages and routes, attach target-specific build metadata, and generate or update game objects. Keep stable source IDs, generated object IDs, and save-placement records separate. Rebuilding an object should reuse its allocated ID; changing instances in saves requires an explicit placement/update operation. Preserve unknown metadata, disclose lossy conversions, and check rights before publication or redistribution.

Protocol: SOUL-BRIDGES.md · luggage: SOUVENIRS.md · terms: GLOSSARY.md · world-to-world (non-save-file) travel: PORTABLE-NPCS.md.

Instances

Bound documents

MOOLLM-side machinery underneath the soul files: object-system/ · LATENT-SPACE-INHERITANCE.md · ENDOSYMBIOSIS.md · sims-design-index.md

MicropolisCore-side design + implementation: soul-city.md · characters-as-hydrogen.md · roadmap · role sheets · peer games · pet shop · sims-io (field mapping, TypeScript) · vitamoo (layered resource I/O) · soul-angel modules

Vocabulary mapping between the two repos: README.md.

Public entry

skills/soul-city/

Part of MOOLLM

README · skills/ · INDEX.yml