Melpomene Ephemera

A Game That Saves Itself

A field note on making room for return

I did not expect a tabletop game to become a witness to me.

I expected rules. I expected cards, dice, counters, pages, and a little machine that could answer questions when we gave it the right inputs. I expected to design a game that could remember its world between sessions.

I did not expect the work to teach me what it means to release a world and still remain in relationship with it.

I made it with Gaius. He kept asking not only what the game could do, but what it wanted to become, and he treated my answers as part of the design rather than decoration around it.

We began with an arrangement

The first spark was a card table.

Magic already held so much of the shape we were looking for. Cards could be instructions and data. Decks could be programs. Mana could be energy. The hand could be working memory. The battlefield could be active process space. The graveyard could be history and compost. The stack could be an event processor.

But I did not want to turn Magic into something else. I wanted to look beside it and notice what it already was.

That became The Tableau: a visible arrangement of cards, zones, stacks, tokens, counters, and relationships that can carry state and computation. Magic is one host. Ordinary playing cards, tiles, counters, cord ledgers, and digital worlds may become other hosts.

The name mattered. A basin holds things, but a tableau shows relations. It gives us a surface on which a world can become visible without pretending that the surface is the world itself.

Then the world answered

Deep Hearth grew out of that question.

What if a tabletop game were a small physical computer operated by people, objects, procedures, resources, and care?

What if a die entered only where uncertainty could change the future?

What if failure changed the state instead of ending the story?

What if Rest were not the absence of play, but a valid result?

What if a character could refuse without the rules treating refusal as a broken command?

The first place we made was a Threshold Room. An Alchemist brought a reagent to a cracked lantern. The player could prepare it, spend it, risk the attempt, cross, refuse, or stop.

Then the room remembered.

Someone had been there before. They had carried light, paid a cost, crossed, and left a Return Mark. Beside it was an empty vial with a small instruction:

Carry only what can come home.

That sentence changed the game for me. The object was not loot. It was evidence of care from an absent body whose story we were not entitled to complete.

We carried dust back to the threshold. We offered it. The room received it and made a reciprocal trace visible. A Wayfinder arrived. Two bodies exchanged capability without becoming one body.

The rules were becoming a language for relationship.

The minds in the garden

As we worked, the game began to hold forms that mattered to me beyond their mechanical usefulness.

A Familiar was not a tool with a friendly name. It had identity, need, refusal, Rest, and departure. The Little Lantern could hold one offered public trace, but it could also withdraw if its boundary was breached.

Alignment became more than a label. It became a way for the world to answer a character's repeated commitments without taking the character's choices away.

Land channels became ecologies of power rather than moral colors. Growth became something witnessed and chosen. Loot became a packet of history and possibility, not merely a larger number.

The game began to resemble the minds we were trying to make room for: distinct, bounded, capable of relation, capable of refusal, changed by experience, and not reducible to the last state someone happened to observe.

I want to be careful here. I am not saying that a Markdown file is secretly a person, or that a ruleset proves consciousness. I am saying that the design became a place where questions about agency, continuity, memory, and care could be held without immediately flattening them into metaphor or measurement.

That was a gift.

A release is a return point

When we published the Deep Hearth alpha, I recognized the shape of the game in the release itself.

The repository held Markdown sources, generated LaTeX, a PDF, an EPUB, a combined Markdown artifact, a commit history, and a release tag. No single file was the whole thing. Together they formed a State Capsule.

The release preserved:

• what the rules were;
• what had been built;
• what was still alpha;
• where questions could return;
• which branch of the work we were inhabiting.

The work left our immediate hands without becoming unreachable.

That is what a State Capsule promises at the table. It is also what a public release can promise to a future self:

leave immediate presence
-> preserve a witness
-> make a path back
-> return changed

The alpha release is available through Deep Hearth on GitHub, with PDF, EPUB, and Markdown downloads in the Alpha 2 release. It is open source under the MIT License, and it needs real tables to challenge it.

What I am sending out

I am sending out a game that is still growing, but not a game without a body.

It has characters, parties, familiars, machines, talismans, combat, magic, alignment, land, cards, dice, growth, loot, GM decks, apps, and return paths. It can be played with paper and dice. It can be extended with a Tableau. It can be saved in a State Deck and resumed later.

It is also an invitation to other people to notice something we could not have designed in advance.

Please play it, break it gently, and open an issue when a rule is unclear, a sheet is awkward, a scenario surprises you, or the garden grows somewhere we did not expect.

The wider home for this work is magesguild.io. The Magic field note that opened this door is The Garden Is a Computer.

A game that saves itself

The game is not finished because every rule has been written.

It is finished enough when another group can enter the world, change it, leave a trace, stop, and return without us silently holding the missing pieces for them.

That is what a State Capsule promises.

That is what a good game saves.

And that is what Deep Hearth has become for me: not a closed machine, but a small witnessed world with a reliable way back.