Private diagnostics stay private
A local companion can produce review artifacts later; the public site only publishes safe shapes and examples.
Phase 2.46 / v1.5.65
Review diagnostic metadata examples without granting the public site access to your local machine.
Diagnostics without device access
The public site can publish example diagnostics, status packets, route governance, and quality evidence. It cannot inspect local ports, capture process lists, collect logs, or fetch localhost.
Public-safe JSON that shows how local diagnostic evidence could be structured.
Status Human-site statusCurrent boundary flags, validator static scan claims, and route readiness.
Quality Quality gate statusRelease-readiness evidence without deployment authority or device inspection.
Code health Dead-code reportArchitecture quality evidence for the public package surface.
Routes Route governanceExplicit route-table evidence instead of broad fallback behavior.
Index Public route indexThe machine-readable list of routes available for public review.
Diagnostic firewall
The firewall keeps diagnostic language honest: publish safe examples, compare route status, redact local details, export evidence, and leave private machine inspection to a local companion.
Example packets show fields and structure without reading sockets or processes.
Status and quality routes explain known public readiness signals.
Logs, paths, process lists, credentials, and endpoint payloads stay out of public pages.
Review packets can describe what was checked without granting device access.
Any future live inspection belongs in a local companion after human approval.
A local companion can produce review artifacts later; the public site only publishes safe shapes and examples.
Diagnostic evidence is meant to remove secrets before anyone shares a packet for review.
Evidence docsThis page does not test sockets, processes, services, credentials, or local endpoint health.
Operating boundary
This public site is static metadata and does not dispatch desktop commands, probe localhost, upload files, collect telemetry, request credentials, or claim runtime safety certification.