Skip to content

Judge tab: the button sits away from its badge, and a judgement does not say what its call took #195

Description

@aitianshi

Priority

high. The judge client times its calls (app/nullius/judge/client.py); the rest is the judge tab's template.

Components

  • app/nullius (backend)
  • app/web (routes)
  • templates and static files
  • docs and the site
  • catalogue (benchmarks, agents, capabilities)
  • the standard (ports, kits, relay, runs)
  • CI, workflows and skills

Today

On a trial's judge tabs the Judge button sits alone on the right, far from the experimental badge. After judging, what the call took (its time, the model, the tokens, the cost) is only in the badge's hover, and the time is not recorded at all.

Wanted

The button on the left, under the badge, and beside it what the last judgement took.

Acceptance

  • The Judge button sits on the left, under the experimental badge.
  • Once judged, a line beside it says how long the calls took, the model, the tokens and the cost, each only when the record has it.
  • The client records each call's seconds with its usage; a judgement of several calls adds them up.
  • A judgement stored before this, with no time, still shows.

Dependencies and related

#197 is stacked on #196 (the Decision rename), which merges first.

Activity

  1. added
    enhancementNew feature or request
    P3When convenient: wording, layout, tests
    on Nov 17, 2026
  2. added a commit that references this issue on Nov 18, 2026
    0d83e39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3When convenient: wording, layout, testsenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions