Add Agent evaluation report site

This commit is contained in:
wuyang
2026-07-27 16:44:10 +08:00
parent df475e8d90
commit cd1eacbd9e
15 changed files with 2487 additions and 0 deletions
+32
View File
@@ -223,3 +223,35 @@ runner work.
Decision retained: evaluation exists to decide whether one controlled Agent change should ship. Do not
compress safety, false completion, gains, regressions, latency, and cost into one decorative score, and
do not build a dashboard before the runner and validators exist.
## 12. Evaluation Explanation Site
The user requested a web presentation of the evaluation conclusion and artifacts. A separate static
report was created under `evaluation-site/` instead of adding another mode to the Atlas.
The report exposes:
- the central release-decision conclusion and evidence boundary;
- an adjustable paired-outcome simulation using the scorer's gain/regression logic;
- all six evaluation layers;
- searchable status-aware summaries of the ten task contracts;
- direct links to the design, contracts, scorer, experiment, corpus increment, and paper library.
The simulator is explicitly not a benchmark result. It exists to make the decision rule inspectable.
The repository artifacts remain the source of truth.
Desktop and 390px mobile views were checked with a real Chromium browser. Programmatic checks covered
horizontal overflow, JavaScript errors, safety-gate rejection, current-task filtering, memory search,
and layer switching.
The first Docker build attempt exposed two deployment details:
- Docker Hub returned a transient EOF while resolving an uncached base tag; the already-present,
current `nginx:1.29.5-alpine` image was used and the exact base digest was recorded by BuildKit.
- copying individual assets with `--chmod=0644` caused the automatically created parent directory to
become non-traversable. The Dockerfile now creates `/usr/share/nginx/html/assets` as `0755` before
copying files as `0644`.
Decision retained: an explanation report is acceptable before the runner because it displays the
contract and its missing evidence. It must not evolve into a score dashboard until real Result JSONL
exists.