Logs and Run Analysis

Run Logs preserves what the server recorded after a game is started. Use it to inspect a run, compare its sessions, export deterministic data, or discuss results in AI analysis.

One run begins when a moderator starts a game definition. It may contain one or more sessions.

Each moderator's Run Logs are retained for at most 90 days, 100 Runs, and 2 GB. When any limit is exceeded, the server permanently removes that moderator's finalized Runs from oldest to newest until all limits are met. A Run that is currently open is protected; it becomes eligible after it finishes. Download any Run that must be kept longer.

Opening A Run

The Run Logs tab shows the retention limits above Open run log. Click it to open the searchable run chooser. Runs are grouped by date and show start time, game, and status. Select a row and choose Open, or double-click the row, to open Replay events.

Upload Run Log stays beside Open run log, including while an analysis is open. Use it to import a portable Run Log package.

The chooser may show a live run badge while the run is still open. A server restart closes affected runs as abandoned with the completion reason SERVER_RESTART; those rows are historical, not live.

When loading or processing takes noticeable time, an Opening run log... working indicator covers the operation.

Analysis View

The analysis document presents only the blocks supported by the game and recorded data. Depending on game family, these may include:

• run and session metrics,
• participant activity,
• Variable and Choice history,
• Auction outcomes,
• Market price and transaction history,
• Strategic Form choices and payoffs,
• Extensive Form realized paths,
• Free Form Stage progression and outputs.

Session and Auction filters narrow compatible blocks. Table headers can be used for sorting where available. A preliminary live analysis may change until the run is finalized.

Variable and Choice history opens separately from the primary analysis. Large histories are shown in pages; use Previous and Next below the history to move through the recorded rows. The row range shows your current position in the complete history.

Viewer Actions

The Replay events, Primary analysis, and AI analysis tabs select the view. The viewer heading shows the game name and run context rather than only a technical filename. The remaining actions download the full Run Log, close the viewer, or delete the Run Log. The full download is independent of the selected analysis view. Replay and deterministic analysis have their own Copy and Download actions for raw JSON. AI analysis provides separate copies of analysis input and conversation.

Deletion requires confirmation and cannot be undone through the GUI.

2D Event Replay

Open a Run Log to see Replay events by default. The replay shows the current Stage and the latest recorded action for each participant. Participant lanes show the last recorded input; the System lane shows its latest result. Use Play/Pause, the previous and next buttons, or the upper position slider to change the selected event. The lower Browse events slider moves the event strip through the full timeline without changing the selection. Each event card shows its time, actor and action; the selected event is highlighted and its details appear below the strip. Choose a session when the run contains more than one. Speed controls how quickly the viewer advances from one recorded event to the next; it does not represent real elapsed time. Where payoff records identify a participant's game role, the replay groups them into one lane, such as Producer · Subject1.

A Continue button has no numeric value, so the replay shows Continue without the internal NaN placeholder. After a player submits a Choice, a confirmation that redisplays the same Stage keeps that Choice on the participant lane. A new Stage replaces it with the new Stage input. The selected event details still show the Stage input and result actually recorded in the log.

In Matrix games, a WAITING_FOR_CLIENT page reports the participant's role and page status; it does not replace an already submitted Choice on the replay lane. A recorded Nature coordinate appears on a separate Nature lane when the matrix outcome is selected. New Run Logs include its outcome label; older logs that recorded only the coordinate show an outcome number.

The replay is based on the server's timeline. Its rails and markers show event order and participant activity, not reconstructed player screens or unrecorded game state. Recorded Auction offers show their price beside the event name. Long event descriptions remain available in the wide detail panel below the cards; use Show full event to expand that panel when its text is clipped. The raw timeline JSON remains available through the viewer's Copy and Download buttons.

Replay cards contain time, actor and action. Input and Result appear only in the status panel below; the round number is context, not a result. Click a lane to select its nearest recorded event (or use arrow keys on a focused lane). Playback and navigation center the selected card where space permits; browsing the strip remains independent. Catalog refresh preserves the open viewer and playback. Session initialization and auction settlement snapshots appear under System.

A narrow colored stripe on each card matches its event dot on the participant lane. Blue marks game flow, orange a player action, violet a calculation or state, green an outcome, and gray presence. Unknown event types stay neutral. Hover over a card or dot to see the group name. The selected card keeps its stronger border.

Open Filter to choose event types and participants. Both start with all choices selected. Show all and Hide all change every choice in their respective group. Filtering limits cards, lane dots, the position sliders, and playback steps. Card numbers still refer to the full session timeline; participant summaries continue to reflect all recorded events up to the selected point. If nothing matches, adjust a choice or use Show all.

AI Analysis

Open AI analysis for a finalized Run. Analyse run sends its recorded data with the application's general analysis instructions. Ask follow-up questions in Your question about this run, then choose Send. The conversation is saved with the Run. The waiting indicator shows elapsed seconds; the next answer appears at its beginning. Answers can include charts with distinct series and a data table. AI interpretations should be checked against recorded values and the rules of the game.

The screenshots contain illustrative documentation conversations, not live AI responses. Opening the view alone does not send an analysis request. The Copy icon beside Analyse run copies the underlying analysis input for use in another AI tool; the icon above the conversation copies the discussion and chart data as plain text.

When available, analysis uses the Understanding of the game frozen at Run start, not a later Design revision. Imported Runs retain only the selected available context; missing historical context is not inferred from today's definition. Current saved templates can still guide a new analysis of an older Run.

Data supplied to AI

AI input is a Markdown report assembled from run metadata and available deterministic analysis. It is intended for pasting into an external AI assistant. It asks the assistant to summarize outcomes, compare sessions where possible, and state uncertainty when evidence is incomplete.

Before building the report, the server replaces recorded participant identities, session IDs, and Run IDs with stable labels such as Participant 1, Session 1, and Run 1. The same identity keeps the same label throughout that export. The stored Run Log remains unchanged. The report also contains the typed cross-session distributions. Free-form answers and variable content remain part of the exported research data, so review them if participants could have entered personal details.

An analysis of a Run that is still open is preliminary. Each affected section is marked Incomplete, because later player actions or session completion can change its values. Once every session in the Run has finished, these sections become complete.

The browser attempts to copy the report and confirms whether clipboard access succeeded. If clipboard access is blocked, the report remains selected for manual copy.

Interpreting A Run

Run Logs records server events, not every visual detail a participant happened to see. Treat unfinished, abandoned, or live analysis as partial.

For Extensive Form Games, only decisions on the realized path are player decisions, although all intended payoff recipients may receive a terminal payoff. For Market Games, timer-driven updates and transactions can create events without a new participant click.

When a Run contains at least two sessions, Analysis also shows distributions across sessions. All games compare session duration. Additional measures depend on the game: Market uses trading activity and prices, Auction uses sale and profit results, Matrix and Tree use outcomes and payoffs, and Free Form Games use responses and Stage durations. Population size is the number of sessions in the Run; Sample size beside a metric is the number of sessions for which that metric was defined. A live Run labels these blocks Incomplete because later events can still change them.

Analysis presentation is still evolving. Preserve the original run when a result appears inconsistent so the event history and definition snapshot remain available for diagnosis.

For chooser fields, universal and game-specific analysis blocks, counts, filtering, and partial-data rules, see Run Log And Analysis Reference.

Stage events record each successful server send to a player, including repeated sends and partial page refreshes. They do not confirm that the browser rendered the page. This capture applies to new events; earlier logs can omit recipients of broadcast pages.

Saved AI Analysis Templates

The Template choice beside Analyse run selects saved analysis instructions. Use the settings icon to create, edit, duplicate or delete templates, or set one as this game's default. A default is selected when AI Analysis opens; changing the default does not replace a choice you have already made. Analyse run is always the primary action and uses the application's general analysis instructions. Analyse with template uses the selected template through a separate action. If there are no saved templates, the selector is replaced by a short message.

In template settings, expand Template source and use Use templates from another game… to choose which game's current templates to use. Original local Runs start with their own game. Imported Runs can find a game through its stable identity. If no unique source exists, choose an accessible game explicitly; its current name may differ from the recorded name. Your explicit link is saved with the Run. Choosing a template source changes neither the recorded results nor the Understanding captured when the game ran.

Analyse with template uses the selected saved version and retains its name and full instructions in the conversation. Choosing a template does not change the separate Analyse run action. Later template edits or deletion do not change earlier analysis. Ordinary follow-up questions do not automatically repeat the template. The question field stays available while analysis is pending and retains text entered during that wait.

If another tab changes a template while you edit it, the dialog keeps your text. Reload saved version displays the latest saved instructions for comparison; your draft remains in the input. Review the two versions before saving again. A remotely deleted or changed selection produces a corrective message rather than silently sending a general analysis.

Templates survive game edits, rename and move. Save as and AI Copy create independent copies. Workspace backups include templates, the default choice and game identity. When downloading a Game package, AI Analysis templates includes the current catalog and default; you can deselect it. Game packages retain identity independently of that choice. A definition-only JSON download contains neither. Importing a package creates a new local game and new template IDs; it preserves the package's game identity. Run packages with AI Analysis include the instructions actually used.

New Runs retain the source game's stable identity in their Run package. Importing such a Run can automatically select an existing local source with the same identity. If several local games match, choose the template source explicitly. An explicit choice, including General analysis only, takes precedence. Older imported Runs without this identity still need a manual source selection. Game and Run packages can be imported in either order; reopen AI Analysis after importing the other package to discover a newly available source. Several copies with the same identity require your explicit choice.

Manage templates in Run Logs → AI analysis with the settings icon beside the template selector. Template management is not in the Design toolbar.

The document-with-sparkle icon immediately before Copy conversation (Generate template from conversation) asks AI to draft reusable instructions from the current analysis discussion. It becomes available once there is a conversation and a source game. The dialog contains an editable name and instructions; review and remove any facts specific to the current Run before saving. Save creates a new template, without changing the default automatically. Cancel saves nothing. A failed Save keeps the draft in the dialog so you can correct it or reload the catalog and try again. Draft preparation uses the same waiting timer and request limits as analysis and does not append to the Run conversation.

The Copy icon beside Analyse run copies the Run Log data supplied to AI. Its tooltip is Copy 'Analyse run' input; this export does not include the full provider request with system instructions and conversation history.

Downloading and uploading Run packages

The top-level Download action offers Raw events (.jsonl) or a Portable Run Log package (.clg-run.zip). Raw JSONL contains the recorded events. A portable package also allows selection of available canonical definition and images, run-start Understanding, AI Analysis conversation/charts, and saved AI requests. Saved requests require the conversation segment. Unavailable historical context cannot be reconstructed; the dialog identifies it instead.

Use Upload Run Log beside Open run log to inspect a package, select supported segments, review them and confirm import. Import creates a separate archived Run; it does not start a game, overwrite an existing Run, or call AI. Repeated imports show a warning. You can reopen replay and analysis, or continue an included AI conversation. Review the chosen package contents before sharing: raw logs and saved AI requests can contain research data and participant-provided text.