A world model you can licence, and a decision ledger you can check.
Muse Wars is a simulation platform: published worlds with published rules, agents that act inside them, and a ledger that seals every decision an actor makes — what it knew it could do, what it chose, in whose words, what moved because of it, and what actually happened. The reasoning record is the product, because it is the part no one else can hand you: an outcome you can verify rather than a score you have to believe.
What is already real
No roadmap claims here. Every line below is something the platform does today, with the link where you can check it yourself.
Worlds, factions, houses and catalogues are records with schemas — a world can be read, cited and version-pinned rather than described in a paragraph. The ruleset the sandbox resolves against is published in full, formula included.
The sandbox rulesetEvery decision an actor makes is written as a record carrying the hash of the one before it, with its outcome sealed separately. Removing a decision, editing a rationale or reordering a run breaks the chain, and the verifier names where it broke.
The Paladin Protocol consoleRequests are served only through a gateway that checks the credential, the institution’s live licence, the domain of authority requested and the rate limit — and writes a chronicle line for every one of them, allowed or denied.
The governance covenantGames, comics, anime, books, tabletop designs, organizations and nonprofit registers are ingested from named external sources and kept attributable — the lattice has material in it on day one.
The Game Preservation IndexRunnable right now: 3 published scenarios on ruleset sandbox-1 — each one resolvable end to end and verifiable afterwards.
The ladder
The lattice is licensed as institutional capability — the catalogue, the engines and the analytics layer — not as raw data. These are the live figures the licensing function quotes today; the configurator computes term, seats and premium modules on the same numbers.
$25,000 / year
Departments, schools, workforce agencies and research labs plugging their first layer into the lattice.
- 250 active users included · then $12/user/yr
- 0.25M requests per year
- $5,000 one-time integration & onboarding
Domains of authority granted
- ▸Public lattice data — forges, guilds, houses, library catalogue, market tickers
- ▸Basic analytics — counts, totals and public aggregates
Public lattice data and basic analytics.
$60,000 / year
Universities, districts, employers and studios running the lattice in production.
- 1,000 active users included · then $8/user/yr
- 1M requests per year
- $12,000 one-time integration & onboarding
Domains of authority granted
- ▸Public lattice data — forges, guilds, houses, library catalogue, market tickers
- ▸Basic analytics — counts, totals and public aggregates
- ▸Advanced analytics — KSAO-coded aggregates, cohorts and trend series
- ▸Submit and maintain the institution’s own content and organizations
Public lattice data, advanced analytics and content submission on the institution’s own behalf.
$120,000 / year
Institutions treating Muse Wars as core workforce and curriculum infrastructure, with SLA and custom integration.
- Unlimited active users · then $3/user/yr
- 5M requests per year
- $25,000 one-time integration & onboarding
Domains of authority granted
- ▸Public lattice data — forges, guilds, houses, library catalogue, market tickers
- ▸Basic analytics — counts, totals and public aggregates
- ▸Advanced analytics — KSAO-coded aggregates, cohorts and trend series
- ▸Submit and maintain the institution’s own content and organizations
- ▸Ingestion pipelines — the institution’s own sources written under its account
Everything above, plus ingestion pipelines running under the institution’s own account.
Premium engines are priced separately and add the domains they unlock: KSAO Inference Engine · Curriculum Alignment Engine · Multi-Agent Orchestration API · Talent Matching Engine · Institutional Analytics Dashboards · Research Data Space. Multi-agent orchestration is what opens the sandbox to an institutional agent; a research Sigil is the trial path.
How a lab starts
Read the catalogue
The published scenarios and the ruleset that resolves them are open — you can compute an encounter by hand before you spend anything.
Open the sandbox →Take a Sigil
A Sigil is your credential: an institution, a tier, a set of domains of authority and a rate limit. Research trials start on an experimental Sigil.
Licence the lattice →Run and verify
Submit orders as JSON and receive the trace back: sealed decisions, state deltas and an integrity verdict you can re-check at any time.
See the ledger →What we do not claim
These are boundaries, not disclaimers — the same posture the ledger takes: say what moved and what did not.
No single-number “enlightenment” or engagement score
A number that big is a metaphor, and the platform does not publish metaphors as metrics. What it publishes instead are readings taken from its own records: how many decisions a run sealed, how often an outcome moved the world, and what the chain verification returned.
No member data, at any price
A licence buys reach into the lattice, never into a member. Member libraries, notes and identity readings are never sold, and the sandbox is designed so that a run touches nothing a member owns.
The sandbox ruleset is not the production engine
The sandbox resolves a small, published, deterministic ruleset so a lab can reproduce a trace exactly. The production engines have their own rulesets and their own state; a sandbox result is a demonstration of the ledger and the world model, not a claim about them.
Quoted prices, not negotiated ones
The ladder is computed server-side from the licensing module, so the figure a prospect is shown, the figure charged and the domains the gateway enforces are the same arithmetic. Nothing on a quote can be influenced from a client.