Run Log And Analysis Reference

Run Logs stores the server's durable record of a started game. The normal interface exposes deterministic Analysis and prepared AI input; the underlying JSONL remains available from the session download.

Run Chooser

Open run log expands the chooser. The filter searches the available rows, which are grouped by start date.

• Started is the run start time.
• Game is the saved definition snapshot used by the run.
• Status is the run lifecycle state and may include a completion reason.
• the analysis icon opens deterministic analysis,
• the document icon opens AI input,
• Trash permanently removes the run log after confirmation.

A live run badge means the run is not finalized and its analysis is preliminary. ABANDONED with SERVER_RESTART is finalized historical data and must not be treated as live.

Loading

Opening analysis may require reading the event log, reconstructing session rows, and deriving game-specific blocks. The working wheel and Opening run log... overlay remain visible during that operation.

Universal Blocks

When data is available, analysis begins with run-level and session-level context:

• number of sessions,
• distinct participants,
• raw event count,
• duration,
• session start and end,
• responses,
• payoff rows and totals,
• final status and participant list.

One raw event can expand into several analysis rows. For example, one terminal event may create one payoff row per recipient. Row counts therefore need not equal raw event counts.

Game-Specific Blocks

Additional contributors add only blocks supported by the recorded game:

• Market: orders, transactions, prices, quantities, account values, and configured history Variables,
• Auction: submitted actions, winner, clearing price, information, and profit,
• Strategic Form: Action coordinates, outcome cells, and payoffs,
• Extensive Form: realized path decisions, Nature outcomes, terminal payoffs, and unreached participants where relevant,
• Free Form: Stage progression, responses, Choices, and Variable outputs.

An absent block usually means that the game family or recorded data does not support it. It should not automatically be interpreted as a zero result.

Filters And Sorting

Session, Auction, and other contextual selectors narrow only compatible analysis blocks. Table headers sort where the viewer offers sorting. Closing or reopening the viewer reconstructs the same deterministic document from the stored run.

AI Input

AI input is a Markdown projection of run metadata and deterministic analysis. It includes instructions to summarize only supplied evidence, compare sessions when possible, and state uncertainty.

Opening AI input attempts to copy it to the clipboard. A confirmation dialog reports success. If browser permissions block copying, the text remains selected for manual copy.

AI input does not add hidden analysis and should not replace inspection of the deterministic tables when exact values matter.

Partial And Final Data

Live analysis may change as events arrive. Finalized analysis is stable for the stored definition and event log, but it can still reveal an incomplete experiment, such as a manually finalized session or an abandoned server process.

Preserve the run whenever behavior is disputed. The definition snapshot, event order, completion reason, and derived tables together provide the diagnostic record.