Endpoint name, transport, allowed operations, denied operations, limits, output shape, and evidence policy are reviewable fields.
Phase 2.46 / v1.5.65
Validate a local endpoint manifest
Check endpoint manifests before anyone treats them as connection-ready. The validator path keeps the review local, explicit, and metadata-only.
Browser-local validation lab
Prove the manifest shape before anyone talks to a machine.
Validation turns endpoint claims into visible checks: required fields, denied operations, redaction policy, evidence output, and the boundary between public review and local approval.
Receipts should expose structure and readiness, not credentials, raw logs, private payloads, or local runtime secrets.
Redacted evidence packets, Markdown summaries, and hash manifests help people compare what was reviewed.
A valid manifest can inform a local review; it does not grant browser authority, runtime certification, or command execution.
Trust scanner
A green receipt is a review signal, not a permission slip.
The validation page helps people interpret proof correctly: it can make a manifest inspectable, expose missing boundaries, and prepare evidence for local review without becoming runtime authority.
Required fields, operation scope, input limits, output contract, and evidence policy can be compared before trust.
Credentials, raw logs, device state, or localhost claims should stop the workflow until a human reviews the payload.
Receipts, summaries, and hashes let another person or agent inspect what was checked without receiving secrets.
Validation does not connect to the endpoint, approve commands, certify safety, or bypass the Desktop decision surface.
Safe sample opens instantly
The browser validator starts with a valid manifest and produces a local receipt without upload intake.
Open workbenchEndpoint scope is explicit
Allowed operations, denied operations, input limits, output shape, and evidence policy are visible fields.
View schemaValidation is not execution
A valid receipt does not grant runtime authority, certification, marketplace approval, or permission to run commands.
Operating boundary
Public clarity, local authority.
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.