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

PSEN

PSEN blueprints model safe local planning loops as reviewable documents instead of hidden execution.

Read technical boundary Review examples

PSEN planning model

Plan, simulate, evidence, review before local authority is granted.

PSEN turns a local endpoint request into a visible rehearsal: describe the intent, simulate against public-safe examples, produce redacted evidence, and leave the final decision on the user's device.

  1. 01 Plan

    Declare endpoint scope, allowed operations, denied operations, limits, and expected output before runtime handoff.

  2. 02 Simulate

    Use public-safe JSON examples to rehearse the workflow without granting browser authority or touching localhost.

  3. 03 Evidence

    Export redacted receipts, Markdown summaries, and hash manifests so another person can inspect the request.

  4. 04 Review

    Approve, reject, or revise locally in the desktop companion instead of trusting hidden execution.

PSEN contract Intent before action Simulation before runtime Evidence before trust Human review before approval
Plan

Describe before doing

Endpoint intent, allowed operations, denied operations, and evidence policy should be visible before any local runtime handoff.

Schema references
Simulate

Use examples as rehearsal

Safe JSON samples let people understand a workflow without granting the browser authority.

Open examples
Review

Receipts over mystery

The path favors artifacts people can inspect later instead of one-time hidden execution.

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.