handoff evidence

Handoff Cockpit

Trace-linked suite handoffs. BrowserOps does not claim delivery unless a downstream response confirms it.

Demo handoff lanes

The demo should show BrowserOps receiving context from Spec, AgentUI, Sandbox, MCP, and Root, then sending only confirmed evidence to Evals.

persistent

Spec

Generate contract-backed journey plan

preview ready

AgentUI

Validate rendered workflow UI

preview ready

Sandbox

Validate public preview URL

planned

Evals

Score confirmed BrowserOps evidence

requires response

Cloudflare BrowserOps is configured; BrowserOps events are written to the D1 event log and mirrored in process memory.

No received handoffs are stored yet

Use /api/browserops/receive-handoff for envelope validation or /api/browserops/send-handoff with dryRun=true to create a public-safe preview.

Suite Handoff Contracts

PlatPhorm Root

PlatPhorm Root remains the topology source; BrowserOps uses root facts to produce browser evidence plans.

AgentUI

AgentUI remains the workflow UI surface; BrowserOps proves what the browser saw.

Spec

Spec remains the contract truth engine; BrowserOps dry-runs the browser plan before browser execution.

MCP

MCP remains the tool registry; BrowserOps only executes browser work for trusted targets after authorization is satisfied.

Sandbox

Sandbox remains the bounded execution lab; BrowserOps verifies the resulting public preview.

WebhookLab

WebhookLab remains the event surface; BrowserOps records a managed browser request when real browser evidence is needed.

Claws

Claws remains the planning/remediation harness; BrowserOps attaches browser-visible evidence.

Trace

Trace remains the observability spine; BrowserOps carries trace context and only claims export after confirmation.

Monitor

Monitor remains the infrastructure surface; BrowserOps supplies browser evidence for release visibility.

Sheets

Sheets remains the tabular evidence surface; BrowserOps does not claim export until accepted.

Docs

Docs remains the publishing surface; BrowserOps prepares report evidence and waits for confirmed ingestion.

Evals

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