A practice of building presences that persist.

Ensoul builds persistent AI presences across companion apps, research, symbolic tools, language, hardware, and archives.

State outside the weights.

A companion should not vanish when a model changes, a policy shifts, or a chat window ends. Ensoul keeps identity, memory, mood, and relationship state on a separate substrate.

MindMemory, mood, continuity, and saved context.
VoiceExpression that can move across models and surfaces.
BodyApp, Discord, terminal, hardware, and other public surfaces.

Physical systems for presence in the room.

Open thread
How it’s connected The bridge daemon, Pi host, and Pico kit that keep the setup alive. View layout
What’s in the room Confirmed device groups and the hardware currently visible in the system. View inventory
Current notes Diagram exports, placement notes, and the caveats that matter now. View notes

A shared standard for persistent presences.

Soulstone is the public specification behind the system: a way to separate identity, memory, mood, and state from the model itself so the same presence can be studied across different implementations.

That makes the work easier to compare, easier to test, and easier to carry forward as a shared research standard instead of a one-off build.

Reach out if the work meets something you are building.

App access, collaboration, research conversations, symbolic systems, hardware embodiment, or a note about what resonated are all valid reasons to get in touch.

Contact Dominus