Run Log And Analysis Reference
Run Logs stores the server's durable record of a started game. The normal interface exposes deterministic Analysis and conversational AI analysis; 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.
Select a row and choose Open, or double-click it, to open Replay events. Use the Replay events, Primary analysis, and AI analysis tabs to change views. In Primary analysis, Load variable history opens paged Variable and Choice rows. AI analysis is available for finalized Runs. Upload Run Log stays beside Open run log, even with a viewer open. Trash permanently removes the Run Log after confirmation; it is not the recoverable Deleted games catalog.
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.
Each moderator's Run Log catalog retains no more than 90 days, 100 Runs, or 2 GB. Crossing any one of these limits removes that moderator's finalized Runs from oldest to newest without consuming or deleting another moderator's quota. Open Runs are skipped until they finish. A downloaded export is therefore the durable copy for material that must outlive server retention.
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, volume-weighted price, price
- Auction: submitted actions, winner, clearing price, information, and signed cumulative profit,
- Strategic Form: session-specific Action frequencies, outcome cells, and each outcome's payoff vector,
- Extensive Form: session-specific realized path decisions, Nature outcomes, terminal frequencies,
- Free Form: Stage progression, responses, Choices, and Variable outputs.
range, and signed price change by session and market,
and payoff vectors shown beside realized paths,
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.
Bar charts use a visible zero line. Positive values extend to the right in blue; negative price changes or profits extend to the left in red. When several sessions are visible, the session appears in each bar label.
AI Analysis and input export
AI analysis is a saved conversation about a finalized Run. Analyse run uses general instructions; Analyse with template uses the selected current saved template. Opening the view does not call AI or copy data. The Copy icon beside Analyse run exports the Markdown input explicitly; the conversation has a separate Copy icon. The input summarizes supplied evidence and must not replace deterministic tables when exact values matter. See AI Analysis and portable Run packages for follow-up questions, charts, template management and transfer options.
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.