Test fixture
Arithmetic, symbolic steps, and structured problem solving.
The model receives the prompt (and optional system message). The run uses scorer rubric_json_metrics with the JSON configuration below. Pass/fail and partial credit are determined entirely by that scorer against the model output; no human grading.
Return JSON only with keys answer, evidence, constraints. A login request hangs indefinitely. The login handler awaits a database query. The database connection pool is fully exhausted because long-running analytics queries have claimed every connection. What is the root cause of the login timeout?
{
"metrics": {
"accuracy": {
"checks": [
{
"contains": [
"connection pool"
]
},
{
"contains": [
"exhausted"
]
},
{
"contains": [
"pool contention"
]
}
]
},
"evidence": {
"checks": [
{
"contains": [
"analytics"
]
},
{
"contains": [
"long-running"
]
},
{
"contains": [
"awaits"
]
}
]
},
"constraint": {
"checks": [
{
"contains": [
"separate pool"
]
},
{
"contains": [
"pool limit"
]
},
{
"contains": [
"query isolation"
]
}
]
}
}
}temperature
0
max_tokens
500
timeout (s)
120
type
scored
file
reason-rc-login-timeout.json