The public site does not scan, fetch, socket-check, or discover private services.
Phase 2.46 / v1.5.65
Security
Security starts with a hard public-site boundary: no local probing, no credentials, no telemetry, no command dispatch, and no hidden runtime activation.
Trust architecture
The safest public control plane is not a control plane.
LocalEndpoint.com is intentionally limited to metadata, docs, examples, schemas, and browser-local validation. Private authority stays local.
Manifest validation runs in the browser tab without sending private endpoint payloads to the website.
LocalEndpoint.com does not collect runtime traces, private logs, endpoint state, or device inventory.
Tokens, passwords, private keys, and raw local endpoint files are outside the public-site workflow.
No page click launches desktop work, installer actions, runtime execution, or autonomous control.
Security boundaries are documented and tested, but runtime safety certification is not claimed.
Firewall relay
Every risky request is routed to the smallest safe surface.
The public website does not become more powerful when a visitor has questions. It routes public learning to docs, safe checks to the browser, approval to Desktop, and runtime requests to denial.
Docs, schemas, route indexes, examples, and quality gates are safe to read without device access.
Manifest checks stay in the tab and can produce redacted receipts for review.
Private endpoint decisions move to a human-visible local companion when the person chooses.
Probing, credentials, uploads, telemetry, command dispatch, and certification claims stay blocked.
Firewall rule
Explain publicly
Validate locally
Approve on device
Deny runtime control
Security boundary matrix
What can happen here is smaller than what the product can become.
The public site can explain, publish contracts, validate local files in the browser, and link to evidence. It cannot operate a visitor's machine.
Docs, examples, schemas, route indexes, discovery files, and quality gates are safe public artifacts.
Manifest checks run in the tab and can export redacted receipts without sending payloads to the site.
Future Desktop approval belongs on the user's device, with visible consent and reviewable receipts.
No scan, fetch, socket check, service discovery, or private-network access is performed by the public site.
No credentials, tokens, private logs, or raw endpoint files are requested as part of the public experience.
No browser click on LocalEndpoint.com launches desktop work, runtime execution, installer actions, or autonomous control.
Read explicit routes
Every supported route is registered instead of generated by broad fallback behavior.
Use local-only tools
The browser validator redacts and hashes without network APIs or upload channels.
Export receipts
Share redacted evidence packets and hashes instead of private runtime data.
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.