How Sessions Work

Active, archived, cloned, resumed, and imported session behaviour in Riskonami.

A session is the persisted container for one assessment run.

What a session contains

  • current phase pointer
  • per-phase JSON artifacts
  • per-phase DOT artifacts where applicable
  • per-phase message history
  • runtime preview and protocol state
  • final report revisions
  • session-scoped uploads and enrichment context

Active session model

In normal user flow, a user has one active session:
  • Active — isArchived = false
  • Archived — isArchived = true
  • Frozen — isFrozen = true
When a new active session is created, other active sessions for that user are archived.
When the user returns, the product loads the most recent active session rather than starting over automatically.Creating a new assessment sets the owner, starts at phase 1, and reserves a credit when the access mode is credits.

Resume, clone, and import

Resume archived session

Resuming creates a new active session from an archived source. It copies saved phase artifacts, messages, and the latest report content into a fresh working session.
Use resume when you want to continue work from a completed or abandoned run without mutating the archived original.

Clone session

Cloning creates a working copy of an existing session so the user can branch from prior work.
Cloning is the supported path after a report is issued and the original session is archived.

Import session

Import creates a new active session from an uploaded export payload.

Session-scoped uploads

Uploaded files are scoped to the current user and current session:
  • files uploaded in one session do not appear in another session
  • GPT upload tools resolve files in the current session scope
Uploads belong to the assessment session, not only to the user account. Diagram import in Phase 2 follows the same session scope.

Session archive

When the final report is issued, the session is archived. The archive stores the session payload, phase artifacts, messages, report revisions, and issued report bytes when available.