Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Renamed to gaptrace

ragradar-core

Shared kernel for the ragradar observability system: the run-record schema, the single SQLite store, and the sNrN target parser. ragradar-capture, ragradar, and ragradar-evaluate all depend on it — it depends on nothing.

You normally do not import this directly. Instrument pipelines with ragradar_capture, evaluate with ragradar_evaluate — both re-export the schema dataclasses. ragradar_core exists so those packages share one store contract instead of three copies of it.

Zero-dependency guarantee

ragradar_core imports only the Python standard library (sqlite3, dataclasses, json, re, pathlib, datetime). This is enforced by a test (tests/test_zero_deps.py) that imports the package in a subprocess and asserts nothing outside the stdlib was loaded.

What lives here

Module Contents
ragradar_core.schema RunRecord and its child dataclasses (ChunkRecord, TokenBudget, TokenUsage, Turn, CacheEvent, ToolCallRecord), all tolerant of unknown kwargs
ragradar_core.store store location, schema + migrations, and every persistence primitive (runs, eval scores, benchmark, policies)
ragradar_core.targets parse_target_id("s4r3") -> (4, 3) — the one sNrN parser

Environment setup contract

ragradar_core.store.connect() guarantees the environment before returning a connection:

  1. ~/.ragradar/ exists (created if missing),
  2. ~/.ragradar/runs.db exists (created if missing),
  3. the schema is at the latest version — fresh databases are created directly at the latest version; databases written by older package versions are migrated in place.

Any entry point — a library call, a CLI command, an example script — works on a fresh machine with no prior CLI invocation.

Schema version + migration story

One constant, ragradar_core.store.SCHEMA_VERSION (currently "3"), recorded in the meta table. The migration chain walks old databases forward on first connect:

  • v1 → v2: adds eval_scores / risk_score / evaluated_at columns to runs; creates the benchmark and policies tables.
  • v2 → v3: creates the runs_fts FTS5 index over run queries (with insert/update/delete sync triggers, backfilled from existing rows) and drops the now-redundant idx_runs_query index.

A database reporting a version this package doesn't know raises RuntimeError rather than guessing.

DB location and layout

The store lives at ~/.ragradar/runs.db (SQLite, WAL mode).

Table Columns
meta key, value — holds schema_version
sessions session_id, title, pipeline, created_at
runs session_id, run_seq, query, pipeline, created_at, run_data (JSON RunRecord), eval_scores (JSON), risk_score, evaluated_at
benchmark pipeline, factor, threshold, correlation, sample_count, updated_at
policies pipeline, policy_data (JSON), updated_at
runs_fts FTS5 index over runs.query

Runs are addressed as s{session_id}r{run_seq} (e.g. s2r3) everywhere — "run" is the data noun; capturing is the verb, and belongs to ragradar-capture.

Metadata

Release files for ragradar-core 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ragradar-core 0.1.0
File Size Uploaded Provenance Actions
ragradar_core-0.1.0.tar.gz 24.0 kB Without provenance Details for ragradar_core-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ragradar-core 0.1.0
File Interpreter ABI Platform Actions
ragradar_core-0.1.0-py3-none-any.whl Python 3 none any Details for ragradar_core-0.1.0-py3-none-any.whl

Total release size: 40.2 kB

Release files / ragradar_core-0.1.0.tar.gz

Download URL ragradar_core-0.1.0.tar.gz
Size 24.0 kB
Tags Source
SHA-256 checksum
How to use checksums
4f769c380316d9224f2ce87d15ec1df561f1e5949cd209b8617d26e1533f1c36
BLAKE2b-256 checksum
How to use checksums
e951ade6fa57cf4459372b973c58feee3237f6008f46de15eedfb127fdcb60bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.10

Release files / ragradar_core-0.1.0-py3-none-any.whl

Download URL ragradar_core-0.1.0-py3-none-any.whl
Size 16.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
428ad0e16d2ae70512a0cac7ea9ef9912ab8be80fded36c0569a15910fcc0b8a
BLAKE2b-256 checksum
How to use checksums
f5436ec96509a1e4de3b182c6a9959a57cb9551cfcb40a4d3ae7f57332fa4ad4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.10

Security for ragradar-core 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page