Phase 2.46 / v1.5.65

Evidence Artifacts

Evidence artifacts are review records, examples, schemas, and exports that help people inspect readiness without activating private systems.

Know what LocalEndpoint does Validate an Endpoint Manifest

Evidence artifacts

Share proof without sharing the private endpoint.

Evidence artifacts make LocalEndpoint claims inspectable: what was declared, what was checked, what was removed, what was hashed, and what remains outside the public site.

01 / Declare Capture the public claim

Record manifest shape, route identity, boundary flags, and review scope before any local approval path.

02 / Redact Remove private material

Evidence can describe readiness without raw logs, endpoint payloads, credentials, tokens, or local paths.

03 / Hash Make the packet comparable

SHA-256 manifests let reviewers confirm that shared packets and receipts have not drifted.

04 / Label State what it does not prove

Evidence supports readiness review; it is not runtime certification, credential validation, or marketplace approval.

Proof relay

Evidence moves forward while private material stays behind.

The relay turns a public claim into a review packet: declare the contract, strip private data, bind the artifact with hashes, label what it proves, then hand reviewers something portable.

01Name the claim
Capture the route, manifest shape, version, boundary flags, and review purpose.
02Strip secrets
Remove raw endpoint payloads, local paths, credentials, tokens, and private logs.
03Bind hashes
Attach checksums so exported packets can be compared after download or review.
04Label limits
State that evidence supports review without certifying runtime safety or marketplace approval.
05Share proof
Portable receipts give people something concrete to inspect without opening a private endpoint.

Relay rule Claims named Secrets removed Hashes attached Review portable

Human siteHuman-site evidence example

Public copy, route, and clarity checks in a redacted evidence shape.

GatewayCustom gateway evidence

Route registry and metadata evidence for the explicit public gateway.

QualityQuality gates

Current readiness signals and the gates that still need proof before broad release.

RoutesRoute governance

Explicit route registration evidence instead of generic fallback behavior.

CodeDead-code report

Architecture hygiene evidence for review before distribution and certification work.

WorkbenchValidator workbench

Browser-local validation that can export a redacted packet, summary, and hash manifest.

Evidence contract Redacted fields only Hashes over mystery No raw endpoint payloads No runtime certification claim

Redact

Remove private data first

Evidence should prove shape, boundary, and review status without carrying secrets.

Privacy boundary

Hash

Make artifacts comparable

Hash manifests let reviewers confirm that a shared receipt has not changed after export.

Generate evidence

Label

Do not overclaim

Evidence supports readiness review; it is not runtime certification, Microsoft approval, or marketplace approval.

Quality gates

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.