Kaelum Bench v0.2 · Public Calibration

Qwen3.8 Max

Accounting Capstone · Run evidence

Provisional · Hybrid

Single configuration-specific calibration run. Not a verified v1 result or statistical ranking. The model-judged component is one stored outcome. The current public release has no model-judge repeatability qualification. A fresh judge call is not guaranteed to reproduce it.

Methodology →

Run summary

Published result

Score

35.8/ 100

Raw score 358.0 / 1000

Valid outputs
99 / 100

Successfully scored responses

Model cost
$1.84

Tested-model inference only

Judge cost
$18.24

Independent AI evaluation

Total cost
$20.08

Model plus evaluation

Scoring method
Hybrid

Configuration-specific

Release status
Provisional

Public calibration

Cost composition

Recorded run cost

Model inference · $1.84AI evaluation · $18.24

Run identity

Model setup

Model
Qwen3.8 Max
Provider
Alibaba
Exact model ID
qwen/qwen3.8-max
Benchmark
Accounting Capstone
Reasoning
xhigh
Tool access
None

Output health

Execution quality

Valid outputs

99 / 100

99.0%

Attempted
100
Model tokens
364.7k
Not valid
1

Scoring process

How this run was evaluated

Hybrid scoring combines deterministic checks with an independent AI rubric assessment. The judge evaluates tasks that require rubric-based review; it does not generate the tested model's answers.

No signed public judge-policy record is available for this release.

Judge model
openai/gpt-5.6-sol
Assessments
99 / 100
Judge tokens
783,938
Judge retries
5
Technical appendixFull technical receiptExact configuration, execution, judge and run-identity fields for stored-evidence audit and replay.Open full technical receipt

Run identity

Exact model configuration

Exact model ID
qwen/qwen3.8-max
Provider
Alibaba
Exact provider route
openrouter/alibaba
Runtime ID
openrouter-tool-free-non-streaming-v8
Reasoning profile
reasoning-max-supported
Reasoning configuration
xhigh
Tool access
None

Material configuration parameters

allow_fallbacks
false
data_collection
deny
max_attempts_per_task
3
max_concurrency
3
max_generation_metadata_lookups
1
max_output_tokens
44000
max_raw_response_bytes
16777216
max_request_bytes
1048576
metadata_timeout_seconds
60
request_timeout_seconds
300
require_parameters
true
temperature
0
zdr
false

Scoring and usage

Exact execution evidence

Score
358.0 / 1000
Percentage
35.8%
Scoring method
Hybrid
Comparison protocol
Configuration-specific
Tested-model cost
$1.84
Judge cost
$18.24
Total cost
$20.08
Input tokens (tested model)
86,674
Output tokens (tested model)
278,025
Total tokens (tested model)
364,699
Attempted tasks
100 / 100
Valid responses
99 / 100
Invalid JSON
0
Schema failures
0
Provider failures
1
Missing responses
0

Judge evidence

Independent assessment details

Judge model
openai/gpt-5.6-sol
Judge provider
OpenRouter (Azure EU)
Judge tokens
783,938
Judge assessments
99
Judge retries
5

Run provenance

Versioned run identity

These timestamps delimit the recorded wall-clock lifecycle span. They do not measure active model execution time or comparable latency.

Benchmark ID
FMB-CAP-ACC-03
Benchmark version
0.3.0-dev
Scorer ID
fmb-live-scorer-v1
Started at
Completed at
Run ID
02a6a4e8-9ba2-53a7-a5c1-f458ed6e9c64

Authenticated publication

Signed release evidence

Most visitors only need the run JSON. The other files let auditors and developers independently verify the publication chain behind this result.

Start with this file

Recommended · this run

Single-run JSON

A sanitized, machine-readable copy of this exact result: model configuration, score, usage, execution, costs, judge summary and provenance. Best for reviewing, archiving or importing this run. The sanitized single-run JSON is a derived projection and is not separately signed.

Download sanitized run JSON

Advanced downloads

Release verification files

These files work together. A single verification file is not useful on its own.

Release inventory

Public manifest

The signed inventory of this release. It lists every published file together with its SHA-256 digest and byte size.

Download signed manifest

Authenticity proof

Ed25519 signature

The detached signature over the exact manifest bytes. It lets the public detect whether the signed manifest was changed.

Download Ed25519 signature

Verification key

Public key

The public verification key used to check the signature locally. It cannot be used to create a valid Kaelum signature.

Download public key

All public runs

Run index

A machine-readable directory of all 126 public runs, including their run IDs, benchmark versions and configuration references.

Download public run index

Benchmark dataset

Source aggregate

The complete published dataset for Accounting Capstone, covering all model runs in this benchmark. Its hash and byte size are bound by the signed manifest.

Download source aggregate
Cryptographic verification detailsPublication identifiers, hash bindings and a local verification command.Open cryptographic verification details

The Ed25519 signature authenticates the exact public manifest bytes, including the release inventory. The manifest in turn binds this run's source aggregate by its SHA-256 digest and byte size.

Configuration key
config-c77efa5c3bd8fcd155b544e09e1a057bd04d9a5b173c3eba118f5830e4d4ef60
Campaign ID
daf55664-0f64-5efd-82e3-07e31557aa5d
Comparison group ID
accounting-capstone-0.3.0-dev-configuration-specific-v1
Signed release ID
2459535f-f982-5826-81ed-c8f6d1514773
Release ID
c44af57d-9091-45c8-9299-96dee423e175
Publication key ID
kaelum-bench-public-release-20260718-v1
Manifest SHA-256
caa004fcccade516afe661a318e69b555844595cbcd726cdc749ff3c64a6378f
Source aggregate
fmb-live-runs-capstone.json
Source aggregate SHA-256
85402a8acfbe9f2ff893e95de5c1e105daada9d13ebf267a87fc67d858020660
Source aggregate bytes
21,048

Verify the evidence chain

  1. Verify the detached Ed25519 signature over the domain-prefixed exact manifest bytes using the published public key.
  2. Confirm that the sidecar payload SHA-256 equals the manifest SHA-256 shown above.
  3. Hash the source aggregate and compare its SHA-256 and byte size with the signed manifest entry.
  4. Resolve this run ID through the public run index and match its campaign ID inside that aggregate.
node -e 'const fs=require("node:fs"),c=require("node:crypto"),m=fs.readFileSync("public-manifest.json"),s=JSON.parse(fs.readFileSync("public-manifest-signature.json","utf8")),k=fs.readFileSync("kaelum-bench-public-release-20260718-v1.pem");console.log(c.verify(null,Buffer.concat([Buffer.from("kaelum-bench-fmb-public-release-v1\0"),m]),k,Buffer.from(s.signature_base64,"base64")))'