The TempleA persistent 5e world
Menu
Play Guide / Public Alpha

No human game master required

PLAY-01 / PUBLIC ALPHA

Bring a character.
The world brings the rest.

Play a genuine 5e campaign alone, or make decisions as a group around one shared session. The AI presents the world and adjudicates it; you choose what your characters do.

Solo
Supported
Co-op
Shared table
Memory
Private SESSION

Start here

You do not need to
study the setting first.

Open the public alpha and state one clear intention. These are ordinary requests, not secret commands.

01 / New player

Begin a campaign

Ask the facilitator to create a character with you and start at the recommended opening.

Create a new solo 5e campaign and guide me through character creation.
02 / Group

Share one table

Tell it who is present and create a character for each player. One person can type the table’s decisions.

Begin a shared-table campaign for three players.
03 / Reader

Explore first

Ask about public world material without creating campaign state.

Explain the Temple and the six Ages without spoilers.

Current co-op boundary: shared-table play uses one conversation and one campaign SESSION. The alpha does not promise simultaneous multi-account turns.

Why it behaves differently

Generative scenes.
Non-generative truth.

The AI can invent the moment-to-moment expression of play without being free to rewrite the world underneath it.

Coherent AI

Checks before it answers

Named world claims resolve against public source. Rules determine uncertain outcomes. A declaration of victory, divinity, ownership, or knowledge remains an intention until adjudicated.

Fixed world

Exists beyond the prompt

The Temple’s history, Ages, institutions, metaphysics, conflicts, and established people are not rewritten to flatter the next choice. Your freedom is to act within them.

Persistent state

Remembers confirmed consequences

Characters, inventory, roll receipts, events, facts, and snapshots can persist. A failed tool call or vivid narration is not silently treated as saved state.

5e OGL / SRD

Uses a familiar game language

Characters, abilities, checks, saves, conditions, damage, equipment, encounters, rests, and level-based play give the campaign a common mechanical grammar.

One complete turn

Intent is not
outcome.

You may say, “I cross the burning gate.” That establishes what you try. It does not establish that the crossing is possible, safe, complete, or recognised.

The facilitator finds the relevant world premise, applies the rule, calls for any necessary roll, returns the result, and records a durable consequence only after the runtime accepts it. This is what keeps play from becoming collaborative wish fulfilment.

The campaign loop

Four steps you can
repeat for years.

  1. 01

    Create

    Make a 5e character. If you omit a rules system, the current runtime stores its tested 5e OGL/SRD-compatible default.

  2. 02

    Enter

    Start in a concrete place with a problem already in motion. You decide what your character notices, says, risks, and attempts.

  3. 03

    Resolve

    The facilitator uses world facts and 5e rules. Uncertain actions may call for checks, saves, combat, costs, clocks, or consequences.

  4. 04

    Persist

    Only confirmed runtime events become durable SESSION state. Save your private resume key and return when you are ready.

What the world remembers

Public canon stays fixed.
Your campaign still changes.

The system keeps two promises separate so both can remain meaningful.

PUBLIC SOURCE

The shared world

History, institutions, metaphysics, named facts, and public rules. A campaign can discover, contest, survive, or misunderstand them; it does not silently rewrite them.

Inspect the public sources →
PRIVATE SESSION

Your consequences

Your characters, inventory, relationships, events, rolls, injuries, discoveries, and durable facts. They can persist without becoming official history for every other table.

Read the continuity rules →

Keep your campaign

Save the key.
Verify the state.

01

Keep the resume key private.

The website never asks for it. Present it only inside the linked public alpha when you intend to resume.

02

Wait for runtime confirmation.

A proposed action, rejected payload, or unavailable service changes no revision and persists nothing.

03

Export what matters.

Ask for current state or a state summary and verify that the runtime actually returned it.

04

Delete only deliberately.

Permanent deletion is irreversible and counts only after the runtime confirms it.

StatusAlpha operational
PUBLIC records256
SOURCEFrozen public release
SESSIONStable ABI
Verified14 August 2026 UTC
Inspect status →

The first move is yours

Enter the world.
Attempt something.

Create a campaign, make one consequential choice, and let the Temple answer it.