MEKYRA

MEKYRAThe AI-native play platform

Your game, running.

Create and run games, live experiences and simulations. Write the rules in plain words: MEKYRA turns them into a playable system, referees every move, remembers every state and replays every match exactly.

  • Card & board games
  • Party games
  • Detective nights
  • Live events
  • RPG campaigns
  • Classroom scenarios
  • Team challenges
  • Corporate drills
Play the live demo See what you can build

Try it: turn a blue dial in §4.1, then aim the Imp.

pocket-tactics · rulebook p.4v0.4.0
§4.1

When Spark Imp enters play, deal damage to an enemy unit in .

ClaudeReads as: one target, enemy side, lanes next to the Imp. Turn the dials.

when spark_imp.enterstarget 1 enemy.unit where lane in adjacent(self.lane)do damage(target, 2)Compiled§4.1 · 3 checks

Enemy lanes · tap a unit to aim Spark Imp

1Spark Imp11

The engine checks every aim against §4.1 before anything happens.

Who it’s forFour kinds of table

One engine.
Every kind of table.

A designer testing a combo. A host running a mystery night. A game master keeping a campaign straight. A team rehearsing a crisis. Different tables, same need: rules everyone can trust, run the same way every time.

  • For creators

    Game designers

    “I want to test my mechanic tonight, not after the next print run.”

    A playable version of your game you can share by link, and thousands of playtests before the first print.

    • Card games
    • Board games
    • Party games
    • Prototypes
    e.g. Pocket Tactics

  • Live experiences

    Hosts & organizers

    “I want a room full of people hooked for two hours, without a spreadsheet and a tired host.”

    A night that runs itself: a private role on every phone, a stage screen for the room, and reveals that land fairly and on time.

    • Detective nights
    • Escape rooms
    • Quiz shows
    • Multiplayer events
    e.g. The Ninth Lantern

  • Worlds & campaigns

    Game masters

    “I want my world, my characters and my house rules to stay straight for months.”

    A campaign that remembers: canon with sources, rules that stay consistent, a world that persists between sessions.

    • RPG campaigns
    • Persistent worlds
    • House rules
    • Play-by-post
    e.g. Hollowmere

  • Training & simulations

    L&D, safety and ops teams

    “I want realistic practice that runs the same way for every group, and a debrief people actually use.”

    A drill built from your playbook, with roles, injects and an after-action report written from the log.

    • Tabletop exercises
    • Team challenges
    • Classroom scenarios
    • Corporate simulations
    e.g. The Last Supply Route

Why MEKYRAMore than an AI game generator

AI can write
a game.
MEKYRA runs it.

Ask a chatbot to referee and it improvises: a different ruling each time, no memory of the board, no record of what happened. MEKYRA keeps the creativity and adds what a real game needs: a referee that never bends.

AspectAn AI chat on its ownMEKYRA
RulesRe-interpreted with every messageCompiled once, each rule linked to the sentence it came from
FairnessThe model decides who is rightThe engine checks every move before anything happens
MemoryLoses track of the boardEvery state saved; players drop out and rejoin mid-turn
ProofNo record of why something happenedEvery match replays to the same result, event by event
TestingYou find the broken combo at the tableThousands of simulated games find it first

PlatformOne engine, three surfaces

Create.
Play.
Understand.

Studio, Table and Replay are three views of one ruleset. A change you make in Studio is the rule the Table enforces and the rule Replay explains. Everything below is computed live by the same engine as the demo.

Create

Studio

Every rule keeps the sentence it came from. Unclear wording becomes a question in the Ambiguity Ledger, with both readings spelled out, until you rule on it.

Inside Studio

§5 Healing

  1. §5.1

    When Mender enters play, heal 2 damage from a friendly unit.

  2. §5.2

    Whenever another friendly unit is healed, Bloom Wisp heals 1 damage from another friendly unit.

    ClaudeThis trigger can fire itself again. Whether it stops depends on §5.3.

  3. §5.3

    A heal that removes no damage as healing.

    Question A-1Two readings are possible. Using the literal one until you rule.

Play

Table

The Table asks the engine before it answers anyone. Illegal moves are stopped with the rule they break; ghost seats fill empty chairs.

seed 1208 · step 12 of 29 · state b9cf2786

Inside Table
Seat 29/12
3Mender23
2Shieldbearer14
3Sniper Owl22
4Ironback35zz
2Shieldbearer13
Seat 111/12

Understand

Replay

A match is a seed and a list of actions. Replay re-executes it event by event, cites the rule behind each one and checks the final hash.

Re-executedfinal 24ed9663
Inside Replay
  1. Seat 1 wins.§6.1
  2. Spark Imp dealt 1 to Seat 2’s Keep.§3.1
  3. Cinder Drake was destroyed.§3.3
  4. Ironback dealt 3 to Cinder Drake.§3.1
  5. Cinder Drake dealt 4 to Ironback.§3.1
  6. Seat 1 drew Ironback.§2.2
  7. Turn 15: Seat 1 has 5 energy.§2.1
  8. Seat 2 played Ironback to the left lane.§2.3
  9. Seat 2 drew Ironback.§2.2

PrincipleOne line we don’t bend

Claude reasons.
MEKYRA executes.

AI is brilliant at reading intent, finding gaps and explaining outcomes. A referee has to give the same answer twice. So MEKYRA splits the work, and you can see the line everywhere on this site: blue pencil for Claude, the ink stamp for the engine.

How the split works

Claude reasons

  • Reads the rulebook, FAQ and errata together
  • Drafts Rulespec and cites the sentence for each rule
  • Turns unclear wording into questions instead of guesses
  • Explains findings and proposes fixes

Neverdecides whether a move is legal during play.

MEKYRA executes

  • Checks every action against the compiled rules
  • Resolves triggers in a fixed, logged order
  • Draws randomness from a recorded seed
  • Replays any match to the same final hash

Always the same answer for the same state and action.

Break-It LabReal games, played in your browser

Break it before
your players do.

Two ghost seats play the current rules thousands of times from numbered seeds. The Lab reports loops, seat imbalance and stalls, cites the rule involved and offers a fix you can apply in one click.

Nothing here is pre-computed. Press the button and count.

ruleset v0.4.0 · seeds 1,000–1,999 · ghost seat vs ghost seat
0/ 1,000 games played

Open the full Lab with history and charts

Play across worldsSame engine, different paper

Four worlds.
One engine.

A card duel, a hidden-role mystery, a tabletop campaign and a team drill. Two are playable on this site right now. All four pass through the same three steps: a rule as written, an engine check, a logged event.

Playable now

Pocket Tactics

Three lanes, two Keeps, twelve cards each. Small enough to learn in a minute, interesting enough to break.

  • Playable on this site
  • 19 rule lines, 3 open questions
  • Seeded, replayable, breakable
Play it now
  1. Rule, as written

    §4.1 When Spark Imp enters play, deal 2 damage to an enemy unit in an adjacent lane.

  2. Engine check
    Rejected§4.1

    Shieldbearer is in the same lane as the Imp. Adjacent means the lane next door.

  3. Event, loggeddamage · spark_imp → lane_runner · 2 · destroyed · §4.1

Training & simulationsTeam development, not employee evaluation

Your playbook,
as a drill.

Five lines of an incident playbook become the rules of a team exercise: roles, resources, injects from a facilitator, and an after-action report with an improvement plan. Nobody gets a personal score.

Run the Last Supply Route Playable now

incident-playbook.pdf · compiled lines

  1. PB 2.1

    Every decision needs its owning role at the table. If the owner is away and no delegate is named, the decision waits.

  2. PB 3.2

    Any single spend above $30k needs Finance sign-off.

  3. PB 3.4

    Spending beyond the incident budget needs executive approval, which is outside this exercise.

  4. PB 4.1

    After a public claim about supply, Communications answers within the same round.

  5. PB 5.3

    Never commit more than half of remaining stock to a single customer.

ProofWhat MEKYRA has built

No drawn-only
features.

Everything you can click on this site runs: the engine, the ghost seats, the replays and every Lab number. Behind it is a multiplayer rules engine we have been building and testing since April 2026.

Playable now

Play it on this site

  • Pocket Tactics: rules with live dials, a match against a ghost seat, exact replay and the Break-It Lab
  • The Last Supply Route: a team drill with a facilitator console and an after-action report
  • Every simulated number, computed in your browser while you watch
Built

Engineered since April

  • Structured effects and ordered triggers
  • Authoritative legality and targeting
  • Persistent decisions that survive a reconnect
  • Deterministic execution with seeded randomness
  • Automated regression tests
  • Public runtime reference on GitHub
In development

Shipping next

  • Rulespec compiler: rulebook text in, typed rules out, with Claude
  • Ambiguity Ledger on your own rulebooks
  • One engine for every genre: duels, hidden roles, campaigns, drills
  • Table rooms by link, with phones as private hands
Engineering notes Roadmap: five directions ahead Runtime reference on GitHub