LocalEndpoint
Metadata-onlyNo public command dispatch Browser-local validationNo upload intake Private runtime stays localNo localhost probing Invited distributionChecksum-backed artifacts

Phase 2.46 / v1.5.65

LocalEndpoint glossary

Plain-language definitions for manifests, local endpoints, evidence artifacts, validators, UAI envelopes, and desktop approvals.

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.

Desktop approval Human permission before handoff

Future approvals, denials, receipts, and revocation belong in the local companion app.

Language decoder

The words separate knowledge from control.

The decoder keeps LocalEndpoint language precise: manifests describe shape, metadata explains context, evidence carries proof, approvals stay local, and runtime never hides inside a public page.

  1. 01Manifest means declared shape

    Fields name allowed operations, denied operations, limits, outputs, and evidence policy.

  2. 02Metadata means description

    Public route context can be read by humans and agents without becoming permission.

  3. 03Evidence means review artifact

    Receipts, hashes, packets, and summaries support inspection without private endpoint data.

  4. 04Approval means local decision

    Consent, denial, revocation, and receipts belong on the person's device.

  5. 05Runtime means private lane

    Execution, credentials, localhost access, and commands stay outside the website.

Decoder rule Words define power Metadata is not permission Receipts beat claims Desktop decides
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 Desktop approval stays local
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.

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.