Skip to main content
Atlas persists runtime activity to Postgres so you can replay discovery runs, audit sessions, and power evaluation reports. This reference summarizes the tables the SDK creates by default and how they relate to each other.

Overview

  • discovery_runs captures onboarding metadata produced by atlas env init.
  • sessions stores per-request telemetry, review status, reward stats, and learning notes.
  • trajectory_events holds fine-grained telemetry (plan approvals, guidance, validations, tool calls).
  • learning_registry caches the latest playbooks per learning_key.
A complete schema is defined in atlas-sdk/atlas/runtime/storage/schema.sql. The sections below call out the columns you are most likely to query.

discovery_runs

Link discovery runs back to runtime sessions through shared metadata (for example, metadata.learning_key or metadata.discovery.environment_factory entries).

sessions

Three performance indexes optimize training data queries:
  • sessions_reward_score_idx: Functional index on (reward_stats->>'score')::float for 10-100x faster reward filtering
  • sessions_created_at_idx: Index on created_at DESC for 50-100x faster date range queries
  • sessions_metadata_gin_idx: GIN index on metadata JSONB for learning key queries
Use review_status to filter exports and harness runs, and join the metadata hash to inspect adaptive_summary, execution_mode, learning_history, or drift alerts.

Metadata Schema Fields (v0.1.13+)

The metadata JSONB column contains structured telemetry. Key fields accessible via AtlasSessionTrace dataclass: Essential fields:
  • session_reward: Aggregate reward with score and uncertainty
  • trajectory_events: Ordered list of runtime events
  • student_learning: Student persona learning notes
  • teacher_learning: Teacher persona learning notes
  • learning_history: Historical learning data
  • adaptive_summary: Mode selection (auto/paired/coach) and probe evidence
Property accessors (loaded on demand):
  • learning_key: Task identifier for grouping sessions
  • teacher_notes: Guidance provided during execution
  • reward_summary: Simplified reward statistics
  • drift: Detected schema or behavior drift
  • drift_alert: Critical drift warnings requiring review
  • triage_dossier: Pre-execution risk assessment
  • reward_audit: Detailed judge breakdowns
  • plans – JSON plan snapshot keyed by session_id.
  • step_results / step_attempts – per-step traces and validation payloads.
  • guidance_notes – ordered teacher guidance emitted during execution.

step_results Schema Fields (v0.1.13+)

Step-level telemetry accessible via AtlasStepTrace dataclass: Essential fields:
  • runtime: Step execution time in milliseconds
  • depends_on: Array of step IDs this step depends on (dependency graph)
Property accessors:
  • attempt_history: Previous attempt records if step was retried
Query step execution times and dependencies for performance analysis:

trajectory_events

The learning evaluation harness samples these events to count validations, guidance injections, and reward updates. Filter by event->>'event_type' to narrow to specific telemetry (e.g., reward, learning_playbook, tool_call).

learning_registry

The runtime loads this table at session start and updates it after successful learning synthesis (subject to learning.update_enabled). Join back to sessions via metadata.learning_key to reconstruct the history that produced the current playbook.

Query Examples