Debugging playbook

Evals Failed Scorecard

Use when an Evals suite, rubric, assertion, or release gate emits a failed scorecard span.

Linked toolsok
4
Source: playbook registry
Updated: 5/25/2026, 5:11:10 PM
Evidence/query
Commandsok
2
Source: playbook registry
Updated: 5/25/2026, 5:11:10 PM
Evidence/query
EvalsSpecBrowserOpsTrace
Symptoms
  • evals span failed.
  • Scorecard evidence is failed or missing.
  • Release evidence report is blocked.
Likely Causes
  • A required assertion failed.
  • Scorecard artifact was not linked.
  • The target service did not expose enough public-safe evidence.
Checks
  • Open Evals scorecard ref.
  • Inspect /api/v1/traces/{traceId}/evidence.
  • Check failed span error code.
Evidence To Collect
  • eval run ID
  • suite
  • rubric
  • assertion
  • scorecard ref
platphormctl Commands
platphormctl trace report <traceId>
platphormctl harness run spec-evals-browserops-loop --target https://trace.platphormnews.com --dry-run