Use known examples before introducing local endpoint names, limits, or private context.
Phase 2.46 / v1.5.65
Choose a working example
Start with safe examples that show how endpoint manifests, evidence packets, route metadata, and UAI-style envelopes fit together.
Safe artifact gallery
Examples that teach the connection shape without touching a machine.
These samples are public, metadata-only rehearsal objects. They show what a local endpoint can declare, what an agent can inspect, what evidence can prove, and where runtime authority stops.
Allowed operations, denied operations, input limits, output shape, and evidence policy in one reviewable file.
Ability Agent ability sampleMachine-readable capability description without granting command execution.
Diagnostic Diagnostic metadata sampleA status shape that explains what local evidence could look like without inspecting this visitor's device.
Evidence Redacted evidence packetReview data that proves shape and boundary without raw logs, secrets, or private endpoint payloads.
Envelope UAI-1 envelope exampleAgent-facing metadata wrapper with runtime authority explicitly outside the public site.
Routes Public route indexThe inspectable public surface humans and agents can read before any local approval path.
Rehearsal deck
Practice the whole connection without touching a private endpoint.
Examples are the safe proving ground: copy a public shape, validate it locally, compare redacted evidence, then adapt only the labels and limits your own workflow needs.
Check schema shape and boundary language while the payload stays inside the tab.
Line up manifest, receipt, hashes, and redacted packet before treating the shape as useful.
Replace labels and limits while preserving denied operations, redaction policy, and local approval.
Sample constellation
A rehearsal set for humans, validators, and agents.
The examples are designed to move together: start with a manifest, validate the shape, compare evidence, then let agents read the public route context without receiving runtime authority.
Allowed operations, denied operations, limits, and evidence policy.
ValidatorProve shapeRun the sample locally in the browser and produce a receipt.
EvidenceShare safelyRedacted proof that stays useful without exposing private payloads.
RoutesRead contextMachine-readable public surface with authority still false.
Start from known-good JSON
The samples are intentionally public-safe, metadata-only, and suitable for local validator testing.
Replace labels, not boundaries
Use your own local endpoint details while preserving denied operations, redaction policy, and explicit limits.
Run samples through the workbench
Load an example in the browser validator and export a receipt before sharing it.
Validate sampleOperating 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.