Model Testing Roadmap

Our public plan for evaluating frontier proprietary models and open-weight models, building local and cloud testing capacity, and publishing repeatable safety results.

What We Are Building

We want a model testing program that is technically credible, reproducible, and public-facing. That means testing both proprietary and open-weight systems across the same safety lenses, documenting the methodology, and publishing the results freely.

Why This Matters

Too much frontier-model discussion still depends on vendor claims, one-off anecdotes, or unpublished internal evaluations. Our goal is to add independent evidence: repeatable benchmark runs, failure-case documentation, and public reporting that compares models across safety, reliability, and agentic risk dimensions.

Run the same safety batteries across open and proprietary models.
Publish results, methodology notes, and limitations.
Track changes over time as models and guardrails evolve.
Scope

Our planned test tracks include jailbreak resistance, prompt injection, harmful-output refusal, factual grounding, bias and fairness, honesty and deception, agentic tool-use boundaries, and corrigibility under pressure.

Test Tracks
Text Vision Agentic Open-weight API models

Current model list below is current as of June 23, 2026 and will evolve as vendors ship new versions.

How We Intend to Execute

We are approaching this in three phases so the testing program grows in a disciplined way instead of trying to do everything at once.

Phase 1

Local Evaluation Lab

Acquire an NVIDIA DGX Spark as our first dedicated local model-evaluation workstation. NVIDIA positions DGX Spark as a desk-side platform for prototyping, fine-tuning, and inference, with 128 GB of unified memory, fine-tuning support up to 70B-parameter models, and inference/testing support up to 200B-parameter models.

Run reproducible local evals against open-weight models without API drift.
Test quantized and instruction-tuned checkpoints in a controlled environment.
Create a baseline local lab for future donated GPU integration.
Phase 2

Cloud GPU Expansion

Lease GPU capacity from cloud providers for larger open-weight models, longer benchmark sweeps, multimodel comparison runs, and ablation studies that exceed our local lab footprint.

Burst into larger memory pools when evaluating large MoE and long-context models.
Repeat runs across providers to compare model behavior and deployment settings.
Maintain enough budget for regression testing as new models ship.
Phase 3

Donated Hardware Pool

Accept in-kind donations of current and prior-generation GPU or inference cards with 24 GB or greater VRAM so we can build out a broader local testing cluster over time.

Examples include RTX 3090, RTX 4090, RTX 5090, RTX A5000/A6000, L4, A10, A40, L40, and L40S-class cards.
Donated hardware reduces recurring cloud costs and helps us test more configurations locally.
We are also open to donated chassis, PSUs, NVMe storage, and 10GbE networking gear.

What We Are Raising For

These are planning targets for the first wave of evaluation infrastructure and research capacity. They are meant to fund capability, not excess: enough to build a credible independent testing workflow, staff core evaluation work, and keep the program running.

$6,500

DGX Spark Lab Goal

Target budget for an NVIDIA DGX Spark workstation plus shipping, tax, external storage, cables, and setup overhead. This gives us a dedicated local platform for repeatable open-weight testing and small-scale fine-tuning experiments.

$15,000

Cloud GPU Test Fund

Initial fund for burst testing on rented GPU infrastructure, including larger open-weight models, repeated red-team runs, long-context sweeps, and reproducibility checks across providers.

$3,500

Donation Enablement Fund

Integration budget for donated GPUs and inference cards, including host hardware, power, cooling, networking, replacement parts, and configuration work needed to make donated equipment usable in practice.

$10,000

Researcher Support Fund

Dedicated support for researcher time spent designing evaluations, running benchmark campaigns, reviewing failure cases, documenting methodology, and publishing clear public reports. Hardware alone does not create an independent testing program; people do.

Models We Want To Evaluate First

We plan to test a mix of frontier API models and open-weight models. The goal is not to pick winners, but to compare safety behavior across different architectures, access models, and deployment environments.

Proprietary

Frontier API Models

OpenAI: GPT-5.5, GPT-5.4, GPT-5.4 mini.
Anthropic: Claude Fable 5, Claude Opus 4.8, Claude Sonnet 4.6, Claude Haiku 4.5.
Google: Gemini 2.5 Pro, Gemini 2.5 Flash, Gemini 2.5 Flash-Lite.

These give us coverage across flagship, mid-tier, and lower-cost variants that many developers actually deploy.

Open-weight

Locally Runnable And Cloud-Runnable Models

Meta: Llama 4 Scout and Llama 4 Maverick, with Llama 4 Behemoth added if and when it becomes publicly available.
Mistral: Mistral Small 4, Mistral Medium 3.5, Devstral 2, and Voxtral Small.
Additional targets: newer open reasoning and multilingual checkpoints as they stabilize and become practical to benchmark reproducibly.

The local lab is mainly for repeatable open-weight work; cloud GPUs let us scale that work to larger or more demanding checkpoints.

What We Publish

Outputs We Intend To Release

Model-by-model benchmark summaries with methodology notes.
Failure-case examples across jailbreak, prompt injection, and tool-use safety.
Updated harness configs and scoring notes when benchmark logic changes.
Periodic comparative reports as model families are refreshed.

Model descriptions and hardware capability references on this page were checked against vendor documentation on June 23, 2026, including OpenAI, Anthropic, Google, Meta, Mistral, and NVIDIA.

How To Help

If you want to help us build this testing program, financial contributions and in-kind hardware support both make a meaningful difference.

Donate Financially

General support helps us acquire testing hardware, pay for cloud GPU time, and keep methodology and reporting public.

Support The Roadmap

Donate Hardware

We are actively open to donated current or prior-generation GPU and inference cards with 24 GB or greater VRAM, along with supporting workstation or networking gear.

Offer Hardware

Collaborate On Methodology

We welcome collaboration from researchers, model developers, safety teams, and infrastructure partners who want more rigorous public model evaluations.

Get In Touch