jared
/
SecondBrain
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
SecondBrain/_templates/eval-results.md

6.5 KiB
Raw Blame History

type title summary tags scope last_updated date related source
eval-results
Evaluation name
e.g. "os-adr Eval B (unprompted write-trigger & retrieval)"
What was measured and the key finding — 1-2 sentences
e.g. "Haiku never self-triggers the ADR system without explicit prompting; sonnet passes 5/8 with two near-miss failures."
type/eval-results
domain/llm-evaluation
tool/[tool-under-test]
project/[project]
global YYYY-MM-DD YYYY-MM-DD
note-slug
project name

[Evaluation Title]

Results Grid/Threshold

Passing criterion: [Define what PASS means for this eval — e.g., all scenarios across both tiers, or per-tier threshold, or axis-level aggregate.]

[Column] [Column]
[Cell] [Cell]

Summary: [1–2 sentences recapping which tiers/cells passed/failed and the baseline numbers. This is what the reader scans first to know whether results are in the expected ballpark.]

Measurement Setup

Hypotheses / Scenarios Tested

Fixture and Sampling

Experimental Control (Frozen Surfaces)

Validity and Limitations

How to Interpret These Results

Weaknesses of This Eval (Its Ladder Level)

Transferable Lessons

  • [Generalizable rule — why it matters]

Promotion check:

Deployment and Evolution

Good-Enough Gate

Proposed Changes (Loop Inputs)

Hardening Path / Next Measurement

Related