Docs
Attributed documentation, ingestion, ranking, scoring, search, clipping, publishing, MCP/API docs, and evidence reports.
Validate Docs in BrowserOps
BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over Docs's product role.
- Target
- https://docs.platphormnews.com
- Journey
- PlatPhorm Docs homepage smoke
Held in memory only and sent in the authorization header.
Boundary
Public preview validates intent. Cloudflare 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 use the operator key for a protected Cloudflare browser check.
Live Public Connectivity
Docs is reachable for public discovery. Use Cloudflare-backed runs for browser evidence.
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
200passed
trace echoed
Cloudflare Browser Runtime
BrowserOps runs for Docs use cloudflare-browser-run. Cloudflare is configured; D1 stores run metadata and R2 stores artifacts. Session metadata records BrowserOps run ID, journey ID, and target service without storing credentials.
Capability Mapping
BrowserOps may call
- publish_evidence_report
- read_report_status
BrowserOps may receive
- docs_report_requested
Transport and Boundary
- Preferred transports
- openapi, rss, atom, mcp
- API docs
- https://docs.platphormnews.com/api/docs
- MCP status
- not advertised
- Auth boundary
- Public docs are readable; publishing and report mutation use BrowserOps-managed service credentials or service-to-service authorization.
Handoff Examples
Docs remains the publishing surface; BrowserOps prepares report evidence and waits for confirmed ingestion.