LocalEndpoint guide

LocalEndpoint glossary

Plain-language definitions for manifests, evidence artifacts, ordinary owner decisions, paired Remote standing authority, and local runtimes.

Know what LocalEndpoint does Validate an Endpoint Manifest

Plain-language operating vocabulary

Names that make the system reviewable.

LocalEndpoint uses specific words so humans and agents can reason about local authority without mixing public metadata with private execution.

Manifest A declared local capability

A JSON record describing endpoint scope, limits, denied operations, output shape, and evidence policy.

Local endpoint A capability that stays on the device

The public website can describe it, but runtime permission and execution stay outside the website.

Evidence artifact A reviewable receipt

A redacted packet, Markdown summary, hash manifest, or status route that supports human review.

Ordinary local approval The owner's current decision

Normal protected local work waits for the person who owns the endpoint to approve or deny that request.

Remote standing authority Pair once, then run unattended

Installing, enabling, and one-time pairing RemoteEndpoints authorizes later authenticated private prompts with zero target-side approvals per prompt.

Language decoder

The words separate knowledge from control.

The decoder keeps LocalEndpoint language precise: manifests describe shape, metadata explains context, evidence carries proof, ordinary approval and paired standing authority remain distinct, and runtime never hides inside a public page.

01Manifest means declared shape
Fields name allowed operations, denied operations, limits, outputs, and evidence policy.
02Metadata means description
Public route context can be read by humans and agents without becoming permission.
03Evidence means review artifact
Receipts, hashes, packets, and summaries support inspection without private endpoint data.
04Ordinary approval means current owner decision
Normal protected local work waits for the owner of the endpoint.
05Standing authority means paired unattended work
RemoteEndpoints install, enablement, and one-time pairing replace target-side per-prompt approval.
06Runtime means private lane
Connect performs Windows work; the authenticated browser carries private intent but does not call Windows APIs.

Decoder rule Words define power Metadata is not permission Receipts beat claims Authority mode stays explicit

SchemaEndpoint manifest schema

Field names and validation requirements for public-safe endpoint metadata.

ValidateBrowser validator

Check manifest shape and export local receipts without upload intake.

EvidenceEvidence artifacts

Receipts, packets, and summaries that support review without private endpoint data.

EnvelopeUAI envelope

Machine-readable route context without granting runtime authority.

BoundaryTechnical boundary

Public explanation, validation, and export stay separate from local operation.

RoutesPublic route index

Every supported human and machine route is registered explicitly.

Glossary contract Runtime boundary Metadata is not permission Evidence has source Ordinary approval stays owner-gated Remote pair once

Manifest

Fields before trust

A manifest is useful because the allowed operations, denied operations, limits, and output contract are named before runtime.

Schemas

Runtime boundary

Names prevent overreach

The vocabulary keeps public metadata, browser validation, desktop approval, and local execution from collapsing into one vague claim.

Boundary docs

Evidence

Receipts over assertions

Evidence artifacts let people inspect what was checked without trusting a marketing sentence or exposing private endpoint data.

Evidence docs

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.