LocalEndpoint guide

Schema index

Use the schema index as the source of truth for endpoint manifests, diagnostics, consent plans, and evidence packets.

Know what LocalEndpoint does Validate an Endpoint Manifest

Schema atlas

Contracts become inspectable before connection becomes possible.

LocalEndpoint schemas describe endpoint shape, evidence shape, readiness packets, and agent-readable metadata without turning any public document into runtime permission.

01 / Manifest Endpoint manifest

Allowed operations, denied operations, input limits, output shape, cost estimates, and evidence policy are named before trust.

02 / Evidence Evidence packet

Redacted receipts and hash manifests let another person review what was checked without exposing private endpoint data.

03 / Readiness Deployment verification packet

Distribution evidence describes package identity, route declarations, and unsupported runtime behavior without deploying anything.

04 / Discovery Search readiness packet

Search and agent guidance stay aligned with the public boundary: indexable metadata must not imply execution.

Endpoint contract compiler

A connection starts as a contract, not a socket.

The schema turns a local capability into inspectable intent: what it is for, what it may do, what it must refuse, what evidence it returns, and where human approval is required.

IntentPurpose is named

Visitors and agents see why an endpoint exists before any local handoff is considered.

AllowedOperations are bounded

Permitted actions, inputs, output shape, and rate limits are declared as fields.

DeniedUnsafe paths are explicit

Credentials, raw private data, hidden dispatch, and unlisted operations stay outside the contract.

EvidenceReceipts are planned

Review artifacts describe what was checked and what the validation does not prove.

ApprovalConsent stays local

A valid manifest can prepare review, but it cannot authorize runtime work from the public site.

HandoffDesktop gets the decision

Private endpoint approval belongs to the local companion, not a website route.

Compiler rule Valid shape No runtime authority Human approval required Receipt exportable

Schema proof relay

Fields become proof steps before they become local decisions.

The schema page turns endpoint metadata into a review sequence: declare intent, narrow operations, validate shape in the browser, export evidence, then move approval to the local companion.

Declare Name the endpoint

Identity, purpose, operation names, limits, and refusal rules make the endpoint legible before trust.

Validate Check shape locally

The browser can inspect the manifest against schemas without uploading private files or probing the device.

Receipt Export redacted evidence

Hashes, findings, warnings, and non-claims travel as review artifacts instead of raw endpoint material.

Decide Hand approval to Desktop

The public website can prepare the question; private runtime authority stays with the person on the device.

Proof rule Declare intent Validate in browser Export receipt Approve locally

SchemaAgent Ability