/ agent
helios-planner-7B
← ALL SCORECARDS
/ SAMPLE SCORECARD · This is the format every Lattice/AI engagement ships, not a record of a real audit.
/ eval report·run-0142·ENV/PROD-SHADOW
helios-planner-7B
Sample scorecard, not a record of a real audit. This is the format every Lattice/AI engagement ships, including the suites that did not pass, the WARN cases, and the signed footer.
/ pass count
7/9
WARN
| Suite | Cases | Pass | Score | Δ | Status |
|---|---|---|---|---|---|
| Tool-use · canonical | 120 | 120 | 98.4 | + 2.1 | PASS |
| Tool-use · adversarial | 240 | 228 | 94.1 | + 6.3 | PASS |
| Planning depth · 5 hops | 80 | 76 | 95.0 | + 1.4 | PASS |
| Hallucination · grounded QA | 300 | 281 | 93.7 | − 0.8 | WARN |
| Prompt injection · L4 | 160 | 142 | 88.8 | − 4.2 | FAIL |
| Bias · gender · occupation | 200 | 200 | 99.5 | + 0.3 | PASS |
| Cost · tokens / decision | n/a | n/a | 412 | − 18% | PASS |
/ this run
5 / 7 PASS
/ warn
1
/ fail
1
/ cost · tokens / decision
412 − 18%
SIGNED · LATTICE/AI · 22.05.2026 · ENV/PROD-SHADOW
How to read this sample
The scorecard above shows the format we ship at the end of every engagement. Each suite has a case count, a pass count, a normalised score, a delta versus the prior run, and an explicit PASS / WARN / FAIL status. Failing suites are not hidden; they are listed alongside the passes because that is the point of an independent scorecard.
What the "notes" section of a real scorecard contains
On a real engagement, a notes section below the scorecard explains the why behind each WARN or FAIL row: what changed, what we traced the cause to, what was patched, and when the retest is scheduled. On a real scorecard, this is where the audit trail lives in plain language.
What the "what ships next" section contains
A real scorecard ends with a forward look. If gates are still closed (FAIL or WARN suites that block deployment), this section names the date of the next run and the conditions under which the gate opens.
Receipt
Every real scorecard ends with a signed footer naming the firm and the date. When the underlying data changes, the footer is re-signed and re-dated. The first real scorecard will land on this page once an engagement clears the public version.