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

Architecture

A compact view of the current custom WSGI architecture, explicit route table, and active code quality gates.

Architecture console

Custom WSGI route registry with inspectable quality signals.

The site runs through an explicit custom gateway: human routes, machine-readable JSON, discovery files, static assets, problem responses, and quality reports are deliberately registered instead of guessed.

01 / Entry Single WSGI gateway

The public website enters through the custom gateway and route registry.

02 / Registry Explicit route table

Human pages, JSON APIs, discovery files, and static assets are listed intentionally.

03 / Evidence Quality is inspectable

Architecture status, route governance, and dead-code reports are public machine-readable evidence.

04 / Boundary Problem responses are intentional

Unsupported paths return typed no-op problem responses instead of hidden framework fallback.

Public-to-local circuit

The architecture makes authority change lanes visibly.

A visitor should be able to see where each signal belongs: public discovery explains, browser validation checks shape, evidence records the review, Desktop handles approval, and private runtime never becomes a website route.

  1. 01Public discovery

    Routes, docs, schemas, and examples describe the local endpoint contract.

  2. 02Browser validation

    Manifest checks run in the tab without upload intake or localhost probing.

  3. 03Evidence export

    Receipts and packets make the review portable without exposing private data.

  4. 04Desktop approval

    Runtime decisions move to the local companion where the user can inspect them.

  5. 05Private runtime

    Local work, credentials, secrets, and device state stay outside the public gateway.

Authority rule Public site informs Browser checks Desktop approves Runtime stays private
StatusArchitecture status

Runtime kind, route count, active source areas, and quality priorities.

RoutesRoute governance

Explicit registration policy, route hash, method policy, and machine-readable route list.

CodeDead-code report

Removed runtime areas, prohibited dependency checks, and fallback-source hygiene.

GatewayCustom gateway status

Current package and boundary state for the custom WSGI route registry.

TableGateway route table

Registered human and machine routes with group, title, and metadata.

IndexPublic route index

Public surface for humans, crawlers, agents, and reviewers.

Architecture contract Single active gateway Explicit route table Zero runtime framework fallback Metadata-only evidence
Pattern

Explicit registry over framework magic

The current site avoids broad generic fallback and exposes the public surface for review.

Gateway cockpit
Quality

Dead code is part of the signal

Architecture checks publish route governance and dead-code evidence for pre-release hardening.

Quality gates
Boundary

Problem responses are intentional

Unsupported paths return a route-not-registered response instead of pretending every URL works.

Technical boundary

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.