Paste, drop, or load a public sample without sending manifest content to the website.
LocalEndpoint guide
Validate an Endpoint Manifest
Validate an Endpoint Manifest in the browser without network calls, upload intake, telemetry, or localhost probing.
Required fields, operation boundaries, and evidence policy are checked before trust.
Obvious private material is surfaced so exported evidence can stay public-safe.
Reports, summaries, and hashes support review without activating an endpoint.
Workbench flight check
Run the validator like a local review ritual.
The workbench is strongest when the path is explicit: start from a public-safe sample, validate the shape, export redacted proof, and stop before runtime authority.
01
Start public-safe
Load a known sample before adapting fields for a local endpoint review.
02 Compare the shapeRequired fields and denied operations stay visible before trust.
03 Export redacted proofReceipts, Markdown, and hashes can travel without endpoint secrets.
04 Stop before authorityDesktop approval is the local decision surface, not this browser page.
Flight rule
Sample first
Validate locally
Share evidence
Approve on device
Receipt stack
Every export tells a different part of the review story.
The workbench should make outputs legible before anyone shares them: a machine-readable report, a human summary, a hash manifest, and a redacted evidence packet.
Structured errors, redaction hits, and boundary flags that agents or tools can compare.
A readable explanation of what passed, what failed, and what still requires local judgment.
Checksums help reviewers confirm that a shared receipt package did not change after export.
Portable proof keeps private endpoint data out while preserving what was validated.
Receipt rule
Redacted outputs
Hashes for comparison
No runtime authority
Desktop approval later
Proof membrane
A valid receipt proves review context, not runtime trust.
The validator makes local evidence portable without letting the public website become an approval surface. A passing result still means shape reviewed, redactions checked, and authority withheld.
Required fields, operation lists, evidence policy, and endpoint posture are checked for review.
Secret-looking values become review blockers before a receipt is treated as public-safe.
Reports, summaries, hashes, and packets can be shared without handing over endpoint authority.
The receipt does not deploy, certify, credential, command, or approve anything on a device.
Membrane rule
Validate metadata
Redact secrets
Export artifacts
Reject authority claims
Input
Endpoint manifest editor
Drop JSON here
or choose a local file. It stays in your browser.
Validation runs in the browser. The public site does not receive your payload.
Output
Validation receipt
Errors
No validation has run yet.
Redaction hits
none
Report JSON
{}
Bridge artifacts
Turn validation into reviewable evidence.
The workbench can generate a redacted evidence packet, Markdown summary, and hash manifest for sharing with humans or agents.
Redacted packet
{}
Markdown receipt
Run validation to generate a summary.
SHA-256 manifest
{}
Schema references
/schemas/localendpoint.endpoint-manifest.schema.json
/api/human-site-clarity/evidence/schema.json
What this proves
The receipt proves browser-side validation and redaction checks. It is not runtime safety certification, credential validation, Microsoft approval, or permission for autonomous execution.
Operating boundary
Public clarity, local authority.
Public product, docs, download, and validation pages do not dispatch desktop commands, probe localhost, upload files, collect runtime telemetry, or claim runtime safety certification. Account credentials are accepted only on dedicated account routes.