Overview
discovery_runscaptures onboarding metadata produced byatlas env init.sessionsstores per-request telemetry, review status, reward stats, and learning notes.trajectory_eventsholds fine-grained telemetry (plan approvals, guidance, validations, tool calls).learning_registrycaches the latest playbooks perlearning_key.
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')::floatfor 10-100x faster reward filteringsessions_created_at_idx: Index oncreated_at DESCfor 50-100x faster date range queriessessions_metadata_gin_idx: GIN index onmetadataJSONB for learning key queries
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+)
Themetadata JSONB column contains structured telemetry. Key fields accessible via AtlasSessionTrace dataclass:
Essential fields:
session_reward: Aggregate reward with score and uncertaintytrajectory_events: Ordered list of runtime eventsstudent_learning: Student persona learning notesteacher_learning: Teacher persona learning noteslearning_history: Historical learning dataadaptive_summary: Mode selection (auto/paired/coach) and probe evidence
learning_key: Task identifier for grouping sessionsteacher_notes: Guidance provided during executionreward_summary: Simplified reward statisticsdrift: Detected schema or behavior driftdrift_alert: Critical drift warnings requiring reviewtriage_dossier: Pre-execution risk assessmentreward_audit: Detailed judge breakdowns
Related tables
plans– JSON plan snapshot keyed bysession_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 viaAtlasStepTrace dataclass:
Essential fields:
runtime: Step execution time in millisecondsdepends_on: Array of step IDs this step depends on (dependency graph)
attempt_history: Previous attempt records if step was retried
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
Related Pages
Training Data Pipeline– Direct database access for training data extractionExport Runtime Traces– CLI usage and JSON schema for session exportsRuntime Safety & Review– Review gating and drift detectionEvaluation Harnesses– Harnesses that query the schema for analytics