Phase 3.397 / v1.5.187

Standards

Standards pages document the current metadata contracts and coding boundaries used by the LocalEndpoint site package.

Standards console

Standards are contracts, not slogans.

LocalEndpoint standards focus on fields, boundaries, schemas, route metadata, evidence artifacts, and UAI-style envelopes that can be reviewed, validated, and tested.

01 / Fields Endpoint shape is explicit

Endpoint manifests name allowed operations, denied operations, limits, output shape, and evidence policy.

02 / Conformance Contracts should be automatable

Conformance packs, validators, and status routes make claims easier to test than narrative docs alone.

03 / Transport Metadata does not open a channel

Transport bindings describe shape and context without creating local runtime authority.

04 / Boundary Local-first by default

Public standards describe metadata and evidence while local approval owns runtime authority.

Protocol foundry

A local endpoint standard should compile into evidence.

The foundry turns endpoint intent into fields, denied powers, portable proof, and a local approval handoff so people can understand the connection before any private runtime is involved.

01Declare shape

Manifests name operations, limits, output contracts, and evidence expectations.

02Deny powers

Unsafe paths are written down as contract fields instead of hidden behavior.

03Attach proof

Schemas, conformance packs, receipts, and route hashes travel with the claim.

04Move authority

Public metadata hands the decision to the local desktop approval surface.

05Review cleanly

Future certification work starts from evidence without pretending certification is done.

Foundry rule Fields declare intent Limits deny power Evidence travels Approval stays local

SchemaEndpoint manifest schema

Required fields, operation declarations, limits, output contract, and evidence policy.

ConformanceUAI conformance pack

Metadata-only pack with route hash and runtime certification explicitly false.

FieldsUAI field registry

Named fields agents can inspect without receiving local capability.

TransportTransport bindings

Transport metadata that describes shape without opening a runtime channel.

EnvelopeUAI envelope example

Machine-readable wrapper for public route context and boundary flags.

BoundaryTechnical boundary

The public website can explain, publish, validate, and export public-safe artifacts only.

ValidationUAIX validation docs

Manifest validation turns metadata into inspectable fields without granting control.

WorkbenchBrowser validator

Validate examples and export receipts without upload intake or localhost probing.

Standards contract Fields before trust Validation before runtime Runtime authority remains local No legacy burden yet

Design

Local-first by default

Public standards describe metadata and evidence while local approval owns runtime authority.

Boundary docs

Testing

Contracts should be automatable

Schemas, validators, and status routes make claims easier to test than narrative docs alone.

Validate

Evolution

No legacy burden yet

Before release, standards can stay clean and direct without preserving accidental public behavior.

Conformance pack

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.