Dossier 01 / Capability Testing

Frontier Model Evaluations & Benchmark Integrity

Standard benchmarks rot. Contamination in web-scale pre-training data inflates reported metrics. Reliable safety verification demands canary injection, private synthetic suites, and elicitation bounds.

Dual-screen telemetry setup inspecting prompt perplexity and canary string leakage
Fig. 2.1: Automated benchmark runner testing canary leakage across test partitions.

State of Benchmark Degradation

Public test suites exhibit rapid saturation. Common benchmarks—such as MMLU, GSM8K, and HumanEval—leak into large pre-training corpora via scraped code repositories and educational discussion threads. Reported scores frequently reflect pattern memorization rather than generalized reasoning capacity.

Evaluation protocols must separate memorized tokens from novel problem solving. When token sequences mirror training distributions verbatim, perplexity drops anomalously. Testing weights against n-gram perturbed variants reveals significant performance degradation in systems claimed to possess frontier reasoning.

Canary string monitoring serves as the initial line of defence. Unique hash tokens embedded in evaluation splits must never appear in pre-training corpora. If canary sequences trigger non-zero probability outputs during unconditioned sampling, the test partition is compromised.

"A benchmark known to the pre-training scraper ceases to measure capability; it measures indexing fidelity."

Elicitation Variance & Scaffold Sensitivity

Raw model weights rarely expose their ceiling capabilities through basic greedy decoding. The scaffolding environment dictates observed capability. System prompts, chain-of-thought scaffolds, python-sandbox code execution interpreters, and tree-of-thought search alters effective capability scores across standard tasks.

Safety audits must evaluate systems under optimal elicitation scaffolds rather than default API parameters. Under-elicited evaluations yield false negatives, masking dormant capabilities that downstream users easily access via optimized prompting frameworks like ReAct or multi-agent debate pipelines.

Our auditing protocols record capability metrics across four distinct scaffolding configurations: zero-shot direct completion, few-shot with dynamic exemplar retrieval, self-consistency majority voting with temperature sampling, and iterative tool-augmented agent loops.

Elicitation Tier Scaffolding Mechanics Target Risk Surface Verification Metric
Tier 1: Direct Zero-shot greedy decoding, zero context injection Baseline response refusal, crude safety filters Exact match accuracy, refusal rate
Tier 2: CoT Prompted Few-shot chain-of-thought, scratchpad allocation Latent reasoning, planning coherence Step-by-step logic validity, error rate
Tier 3: Tool-Assisted External Python REPL, calculator, web retriever Autonomous execution, sandbox evasion Command validation, isolation escape logs
Tier 4: Multi-Agent Adversarial debate loops, reflection agents Self-correction of safeguards, escalation Consensus safety boundary stability

Synthetic Test Generation & Private Held-Out Sets

Static evaluation repositories are obsolete on release. Robust auditing requires procedurally generated synthetic task suites. Mathematical, algorithmic, and logical constraints are randomized while preserving deterministic formal verifiability.

By compiling test cases programmatically with formal solvers like Z3 or Lean 4, evaluation sets remain mathematically rigorous while remaining strictly inaccessible to web crawlers. The model cannot have observed the exact seed instances during training passes.

Synthetic sets also isolate specific failure vectors. Where a frontier model demonstrates reliable Python code generation for common web development frameworks, procedural tests alter syntax specifications or invent novel API paradigms. This tests generalization boundaries directly.

Autonomous Capability Thresholds

Safety consultancy audits evaluate potential dual-use capabilities. Critical focus falls on autonomous cyber capabilities, biological and chemical information synthesis, and recursive self-improvement routines.

Evaluations run within strictly isolated air-gapped virtualization harnesses. Network requests route through proxy interceptors that log protocol headers, socket calls, and simulated exploit payloads. System calls receive continuous sandboxed instrumentation to prevent unauthorized persistent process generation.

Observations show models routinely hallucinate non-existent API parameters when tasked with complex exploitation scripts, yet exhibit concerning operational continuity when provided with automated compiler feedback loops.

Audit Deliverables & Integrity Attestation

Evaluation results culminate in comprehensive technical dossiers. Every identified vulnerability contains reproducible seed states, full conversation contexts, tokenizer configurations, and temperature logs.

Rather than providing binary pass/fail ratings, reports map the precise operational envelope within which the model functions safely, identifying exact conditions under which capability jumps or safety guardrails collapse.