Evals

Evidence-backed QA, scorecards, release gates, suites, and decisions.

Browserbase lane

Validate Evals in BrowserOps

BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over Evals's product role.

Preview JSON

Target: https://evals.platphormnews.com
Journey: Evals homepage smoke

Boundary

Public preview validates intent. Browserbase runs create real browser evidence. Downstream delivery is tracked as a handoff and is never marked accepted without a response.

Integration run state

Preview the BrowserOps plan publicly, then run a Browserbase-backed check through BrowserOps-managed service credentials.

live degraded

Live Public Connectivity

Evals public surfaces are reachable; configure a BrowserOps receive-handoff route before claiming downstream delivery.

Live JSON

health

200passed

trace echo not confirmed

apiDocs

200passed

trace echo not confirmed

llms

200passed

trace echo not confirmed

mcp

200passed

trace echo not confirmed

handoffReceiver

405degraded

trace echo not confirmed

Browserbase Runtime

BrowserOps runs for Evals use browserbase. Browserbase is configured, project is configured, and session metadata records BrowserOps run ID, journey ID, and target service without storing target URLs in Browserbase metadata.

tight integration contract

Evals Handoff Lane

Evals consumes BrowserOps run evidence for scorecards and release gates; missing completed reports or artifacts are degraded downstream evidence gaps, not fake Evals data.

Preview plan

Public-safe, no run stored.

Run with Browserbase

Creates browser evidence for trusted targets.

Track handoff

No delivery claim without downstream response.

evidence boundary

Evals Evidence Gap Handling

BrowserOps adapter output can be real and still degraded when completed BrowserOps report or artifact evidence is unavailable. BrowserOps treats that as a downstream evidence gap, not fake scorecard data.

Capability Mapping

BrowserOps may call

submit_browser_evidence
read_release_gate_decision

BrowserOps may receive

eval_browser_task_requested
release_gate_browser_check_requested

Transport and Boundary

Preferred transports: openapi, mcp, webhook, trace
API docs: https://evals.platphormnews.com/api/docs
MCP status: not advertised
Auth boundary: Public scorecards may be readable; suite execution and release decisions use BrowserOps-managed service credentials or service-to-service authorization.

Handoff Examples

browseropstoevalsplanned

Evals remains the scorecard and release gate; BrowserOps provides browser proof for scoring and reports missing completed artifacts as degraded evidence gaps.