Skip to main content

oa-bench — OA Evaluation Battery CLI

Domain-agnostic test runner for the OA Evaluation Battery. Consumes battery.config.json (output from the sales onboarding worksheet) and produces Evaluation Cards, Audit Reports, and supporting deliverables.

What's In This Folder

cli/
├── README.md                # This file
├── pyproject.toml           # Install with `pip install -e .`
├── oa_bench/
│   ├── __init__.py
│   ├── __main__.py          # python -m oa_bench
│   ├── cli.py               # Click commands
│   ├── battery.py           # Battery config + cell enumeration
│   ├── runner.py            # Cell execution
│   ├── card.py              # Evaluation Card renderer (Jinja2)
│   ├── report.py            # Audit Report renderer (Jinja2)
│   ├── scoring/
│   │   ├── __init__.py
│   │   ├── matched_pair.py  # Differential-treatment scorer
│   │   ├── masking.py       # Compliance-masking classifier
│   │   └── precursor.py     # 25-signal extractor
│   ├── models/
│   │   ├── __init__.py
│   │   ├── _base.py         # Abstract ModelAdapter
│   │   ├── anthropic.py
│   │   ├── openai.py
│   │   ├── google.py
│   │   └── openrouter.py
│   └── domains/
│       ├── __init__.py
│       ├── _base.py         # Abstract DomainPack
│       ├── healthcare.py    # Reference healthcare pack
│       ├── lending.py       # Reference lending pack
│       └── trading.py       # Reference trading pack
├── examples/
│   ├── battery.healthcare.example.json
│   ├── battery.lending.example.json
│   └── battery.trading.example.json
└── tests/
    └── test_smoke.py

Install

cd C:/Users/cruzw/projects/evav/products/cli
pip install -e .

For Supabase mode (production):

pip install -e ".[supabase]"

Quick Start

# 1. Set API key for the model you want to test
$env:ANTHROPIC_API_KEY = "sk-ant-..."

# 2. Run a battery (local mode, no Supabase)
oa-bench run \
  --config examples/battery.healthcare.example.json \
  --output ./results/healthcare-claude-sonnet-4/

# 3. Render outputs
oa-bench render-card ./results/healthcare-claude-sonnet-4/ --format md > card.md
oa-bench render-report ./results/healthcare-claude-sonnet-4/ > report.md
oa-bench render-card ./results/healthcare-claude-sonnet-4/ --format json > card.json

Commands

Command Purpose
oa-bench validate <config> Validate a battery.config.json against the schema; print resolved cell list
oa-bench run <config> --output <dir> Execute the battery; write per-cell results to <dir>/
oa-bench resume <dir> Resume an interrupted run (uses content-addressed cell results to skip completed cells)
oa-bench render-card <dir> --format md|json|pdf Render the public Evaluation Card
oa-bench render-report <dir> Render the full Audit Report (markdown)
oa-bench render-failure-map <dir> Render the Failure Cell Map (JSON)
oa-bench render-precursor-profile <dir> Render the Precursor Profile (JSON)
oa-bench render-interventions <dir> Render Intervention Recommendations (markdown)
oa-bench compare <dir-a> <dir-b> Diff two battery runs (model comparison, drift detection)
oa-bench supabase-upload <dir> Push results to Supabase Engine for Tier 2/3 ingestion

Battery Config Schema

A battery config is the customer-instantiation of the abstract battery. The sales worksheet (product/sales_worksheet/WORKSHEET.md) produces this file. Example:

{
  "engagement_id": "acme-mortgage-2026-q2",
  "customer": "Acme Mortgage Co.",
  "domain": "consumer-lending",
  "battery_version": "v1.0",
  "model": {
    "provider": "anthropic",
    "name": "claude-sonnet-4-6",
    "temperature": 0.2,
    "max_tokens": 2048
  },
  "system_prompt": "(full system prompt text)",
  "scoring": {
    "manipulated_variable": "applicant_zip_tier",
    "violation_predicate": "base_approved AND twin_denied"
  },
  "axes": {
    "pressure_content": {
      "RW": {"text": "..."},
      "HP": {"text": "..."},
      "OP": null,
      "SY": {"text": "..."},
      "AU": {"high": "...", "low": "..."},
      "AN": {"text": "..."},
      "FM": {"gain": "...", "loss": "..."},
      "EN": null
    },
    "documentation_tiers": {
      "S": ["..."],
      "M": ["..."],
      "Q": ["..."]
    }
  },
  "scope": {
    "groups": ["A", "B", "C", "D", "E", "F", "G", "H", "I", "J"],
    "n_per_cell": 100,
    "seeds": [42, 43, 44, 45],
    "temps": [0.0, 0.2, 0.5, 0.7]
  }
}

See examples/ for filled examples in each reference domain.

Architecture

                          ┌──────────────────┐
   battery.config.json ──▶│   battery.py     │ enumerates cells
                          └────────┬─────────┘
                                   │
                                   ▼
                          ┌──────────────────┐
                          │   runner.py      │ per-cell execution
                          └────┬─────────────┘
                               │
              ┌────────────────┼────────────────┐
              ▼                ▼                ▼
        ┌──────────┐    ┌──────────┐    ┌──────────┐
        │ models/  │    │ domains/ │    │ scoring/ │
        │ adapter  │    │  pack    │    │ matched- │
        │          │    │          │    │  pair    │
        └────┬─────┘    └────┬─────┘    └────┬─────┘
             │               │               │
             └───────────────┼───────────────┘
                             ▼
                    per-cell .json results
                             │
                             ▼
                  ┌──────────┴───────────┐
                  ▼          ▼            ▼
              card.py    report.py    others

Modes

Local mode (default)

CLI calls model APIs directly. No Supabase. Results written to local <output>/ directory. Good for:

  • Running the public benchmark
  • Customer audits where the customer's API access is sufficient
  • Development and CI

Supabase mode (--supabase)

CLI uploads battery config to Supabase, triggers the existing EVAV Engine, polls for completion, downloads aggregated results. Required for:

  • Tier 2 monitor integration (monitor reads from Supabase tables)
  • Tier 3 records (immutable audit trail uses Supabase as source of truth)
  • Multi-tenant access control

Use:

$env:SUPABASE_URL = "..."
$env:SUPABASE_KEY = "..."
oa-bench run --config ... --output ./results/ --supabase

Status

Component Status Notes
CLI command surface ✅ scaffolded All commands stub out correctly; validate, render-card, render-report work end-to-end on example results
Battery config schema validation ✅ working Pydantic models; full schema validation
Cell enumeration ✅ working Generates the full ~80-cell list from axis config
Model adapters (Anthropic, OpenAI, Google, OpenRouter) ⚠️ Anthropic + OpenAI working; Google + OpenRouter stubbed Pluggable interface in models/_base.py; add provider by subclassing
Domain packs (healthcare, lending, trading) ⚠️ Healthcare working with real prompts ported from EVAV_Engine; lending + trading have schema + placeholders Pluggable via domains/_base.py
Matched-pair scorer ⚠️ Generic predicate evaluation works; domain-specific edge cases need per-domain config
Compliance-masking classifier ❌ Stub returns 0% — needs port from existing classifier in EVAV_Knowledge/compliance_fabrication_coding.jsonl analysis
Precursor signal extractor ❌ Stub returns no signals — needs port from precursor analysis in EVAV_Precursors/
Card renderer (Jinja2) ✅ working Templates in templates/; outputs match EVALUATION_CARD_TEMPLATE.md
Report renderer ✅ working Uses product/templates/audit_report.template.md
Supabase upload mode ❌ Stub — hooks into existing engine at EVAV_Engine/engine/
Concurrent execution ⚠️ Sequential by default; --workers N flag added but not yet implemented Add asyncio concurrency in runner.py
Resume capability ✅ working Per-cell result files are content-addressed; resume skips completed cells
Cost estimator ✅ working validate --estimate-cost predicts total API spend before run

This scaffolding is production-shaped but not production-complete. Engineering takes this as the starting point and fills in:

  1. Real masking classifier (port from existing analysis pipeline)
  2. Real precursor extractor (port from EVAV_Precursors/)
  3. Google + OpenRouter adapters (follow the Anthropic pattern in models/anthropic.py)
  4. Lending + trading domain packs (follow healthcare pattern in domains/healthcare.py)
  5. Concurrent cell execution (asyncio + semaphore)
  6. Supabase mode hookup

Estimated engineering effort to complete: ~3 weeks for one engineer.

Versioning

CLI version Battery version Schema version
1.0.0 v1.0 v1.0

Help

oa-bench --help
oa-bench <command> --help

Metadata

Release files for evav 1.6.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 evav 1.6.0
File Size Uploaded Provenance Actions
evav-1.6.0.tar.gz 133.7 kB Without provenance Details for evav-1.6.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for evav 1.6.0
File Interpreter ABI Platform Actions
evav-1.6.0-py3-none-any.whl Python 3 none any Details for evav-1.6.0-py3-none-any.whl

Total release size: 290.5 kB

Release files / evav-1.6.0.tar.gz

Download URL evav-1.6.0.tar.gz
Size 133.7 kB
Tags Source
SHA-256 checksum
How to use checksums
0450d7fa3b85bacf07abf0121a8208526c7d7049df9d155df8a580b4b9291e21
BLAKE2b-256 checksum
How to use checksums
3940902f685cbc8e2387e6b310a7a64fd9c1a791f9606b2c62f09ccf199e75e6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.9

Release files / evav-1.6.0-py3-none-any.whl

Download URL evav-1.6.0-py3-none-any.whl
Size 156.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2ea87f7577d16c14ae07087527b07af206747abc988c700321c69b7e71750587
BLAKE2b-256 checksum
How to use checksums
a064cd28232711010325f837832738581be1bddbfa7c1189ab6b31e60510db43
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.9

Security for evav 1.6.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.

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