Phase 2.46 / v1.5.65

Direct answers

Direct answers for humans, developers, and invited testers who need to know what LocalEndpoint does today and what it refuses to do from the public site.

Start quickstart Read security boundary

Direct answers

The short version: public clarity, local authority, reviewable evidence.

LocalEndpoint.com is the public explanation and validation surface. Desktop is the local approval surface. The two are intentionally separated so people can understand the system without giving a website control over their machine.

Does the public site connect to my machine?

No. It serves metadata, docs, schemas, examples, and browser-local validation. It does not probe localhost, upload private files, dispatch commands, collect telemetry, or request credentials.

Who is this for right now?

Invited users, people you directly know, developers, reviewers, and early testers who want a local-first AI connection workflow before broad public distribution claims are made.

What makes it useful before broad release?

The site already gives visitors the story, public boundaries, schemas, route index, safe examples, quality gates, download artifacts, and browser validator path.

Can anyone download it from the website?

Technically yes, the current path is a checksum-backed portable package and offline toolkit. The copy stays clear that installer signing, store approval, and broader certification gates are future readiness work.

What does Desktop add?

Desktop is the local companion for visible approval, request review, local receipts, and future endpoint handoff. It is where private runtime decisions belong.

How should AI agents treat the site?

Agents can read discovery files, route indexes, schemas, examples, and quality gates. They should stop before runtime authority and hand off to human-controlled local review.

Answer resolver

Every common question resolves to one of four safe surfaces.

The FAQ turns uncertainty into routing logic: public pages explain, browser tools validate, Desktop approves, and receipts prove what was reviewed without exposing private endpoint state.

Public site Explains without control

Questions about what LocalEndpoint is resolve to overview pages, docs, route metadata, and security boundaries.

Browser Validates without upload

Questions about trying it safely resolve to manifest checks, examples, and local receipt exports.

Desktop Approves with visibility

Questions about action, permissions, and private runtime decisions resolve to the local companion.

Evidence Proves without secrets

Questions about readiness resolve to checksums, schemas, quality gates, and redacted review artifacts.

Resolver rule Explain publicly Validate locally Approve on device Share evidence only

Visitor decision spine

Ask like a human. Move only when the boundary is clear.

The FAQ is designed to turn uncertainty into a safe next step: understand the split, verify with public data, choose whether a download makes sense, then keep approval on the local machine.

01Understand the split
The website explains the public model; it does not become the endpoint.
02Verify with samples
Use public schemas, examples, and browser-local checks before private data enters the conversation.
03Download with evidence
Use checksum-backed artifacts while installer signing and broader distribution gates remain visible.
04Approve on device
Desktop turns requests into local review moments with receipts instead of hidden web commands.

Public siteExplains and validates

Browser tabChecks without upload

DesktopReviews and approves

ReceiptProves what happened

Answer router

Every answer points back to the same boundary: learn here, decide locally.

The FAQ should help a visitor choose the next safe move without pretending the website is a remote control surface.

Question What is LocalEndpoint?

Start with the public-to-local model and the permission membrane.

Question Can I try it safely?

Use the browser-local validator before any private endpoint review.

Question Can invited users download it?

Follow checksum-backed artifacts and keep broad-launch claims separate.

Question Where does approval happen?

Move runtime decisions to the local companion on the user's machine.

FAQ boundary Public clarity Browser-local checks Device approval Evidence, not secrets

Public webExplains

Pages, schemas, examples, discovery files, and quality evidence.

BrowserValidates locally

Manifest checks and receipts happen in the tab without upload intake.

DesktopApproves locally

Private runtime decisions stay on the user's machine.

Release pathInvited first

Useful now, with broader distribution gates still visible.

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.