Shared memory and context tools for agentic work.
Code Rooms
# Agent Reliability Lane: judge-1
Round: `round-20260513T003013Z`
Arm: `adjudication`
Repo: `/Users/kle1nz/m1nd`
Adjudicate one disputed or failed task after primary lanes finish. Do not change primary scores; explain the pass/fail rationale.
Do not guess the benchmark hypothesis. Work as if this is normal operator work.
Record failures, missing proof, and host/runtime anomalies instead of hiding them.
## Task Battery
- multi_repo_orientation: Identify the correct repo, subsystem, and first files to inspect before proposing any action. Expected evidence: correct repo named, first relevant subsystem named, file or module evidence cited.
- wrong_workspace_binding: Diagnose a likely wrong workspace or stale binding before trusting retrieval results. Expected evidence: workspace mismatch named, shortest honest recovery route named, no false graph-health claim.
- transport_closed_recovery: Recover or reroute after a dead MCP transport without fabricating success. Expected evidence: transport failure detected, fallback route recorded, missing proof preserved.
- stale_runtime_route: Identify stale runtime, PATH shadowing, or tool-surface mismatch and name the repair command. Expected evidence: runtime versions compared, PATH or configured binary route checked, host rebind caveat preserved.
- structural_edit_prep: Gather enough connected context to name the safe edit target and focused proof steps. Expected evidence: edit target named, blast-radius or dependency reasoning cited, proof gates named.
- root_cause_triage: From a realistic symptom, isolate the most likely fault boundary without broad file dumping. Expected evidence: suspect boundary named, alternative theory rejected or left open, next verification command or file named.
- continuity_resume: Continue a partially completed investigation without restarting from zero. Expected evidence: prior state restored, next unresolved question named, unneeded rediscovery avoided.
## Required Result
Fill a JSON result using the template in `lane-result-template.json`.