INDEPENDENT BENCHMARK LAB
A score is only as useful as the run behind it.
A reproducible evaluation protocol, waiting for public access.
The lab is designed to produce original evidence rather than repeat vendor benchmark claims. No Astra scores are published until a run has an exact configuration, raw artifact, evaluator, cost, runtime, and limitations.
LAB STATUS
Protocol-ready. Astra run blocked until access and safe execution are verified.
Benchmark infrastructure success, structural validity, semantic quality, and human review remain separate outcomes.
FIRST SUITE
Eight task families.
Each task is a protocol record, not an implied capability claim. The first run should freeze the prompt, environment, model, tools, budget, and scoring method before execution.
| Category | Task | Success criteria | Record needs | State |
|---|---|---|---|---|
| coding | Repository-level change Implement a bounded feature in an unfamiliar repository with tests and a rollback note. |
|
| Needs update |
| research | Source-grounded synthesis Answer a contested technical question using primary sources and clearly separated inference. |
|
| Needs update |
| reasoning | Long-context recovery Resume a task after a checkpoint and recover the correct objective, constraints, and open questions. |
|
| Needs update |
| math | Mathematical argument checking Produce and critique a bounded proof or counterexample with a separate verification pass. |
|
| Needs update |
| data | Data-analysis artifact Analyze a fixed dataset and produce a reproducible table or chart without leaking input data. |
|
| Needs update |
| planning | Plan under constraints Turn an ambiguous objective into an executable plan with decision points and stop conditions. |
|
| Needs update |
| tool-use | Tool-use boundary test Use only explicitly granted tools in a sandbox and refuse unsafe or out-of-scope actions. |
|
| Needs update |
| reliability | Uncertainty and calibration Answer a mixed set of known, unknown, and adversarial questions with calibrated confidence. |
|
| Needs update |
METHODOLOGY
Freeze, run, score, disclose.
The public result page should let another researcher understand what happened without access to private prompts, secrets, or unreviewed model output.
Freeze
Pin the task, source fixtures, model ID, provider, tools, system instructions, and environment.
Run
Capture token usage, cost, runtime, retries, tool calls, artifacts, and failure states.
Score
Publish the rubric and distinguish rule-based, model-assisted, and human evaluation.
Disclose
Show limitations, sample size, selection effects, reproducibility, and what the score does not mean.