APEX VESPA

PrivateSovereign Cockpit Operate the estate; interface with ETHRAEON. Cross-platform, vendor-agnostic.

What VESPA is

APEX VESPA is the sovereign cockpit app and extensible sandbox surface: sovereign use of VPS extensible cloud services, vendor-agnostic LLM use, always cross-platform. It is distinct from VESPER: VESPER is the internal infrastructure and governance truth-ledger that VESPA reads as a backend. VESPA never claims to be VESPER.

Capabilities (v1, from canon spec)

Model selection (model-agnostic, no forced tokenization)

Metering included; no forced tokenization. Model preference is operator-selected per the spec.

Estate operations (reads VESPER backend)

Architecture status/api/architecture-statusservice-bound; GET /ops/estate
Apps catalog/api/app-catalogservice-bound; GET /ops/estate
Apps status/api/apps-statusservice-bound; GET /ops/estate
Action bus/api/action-busservice-bound; GET /ops/estate
Activation status/api/activation-statusservice-bound; GET /ops/estate
Alignment status/api/alignment-statusservice-bound; GET /ops/estate

Panels map to VESPER /api/* endpoints, proxied live via the VESPER service binding at GET /ops/estate (Access-gated). The status cells self-populate from /ops/estate on load. No metric is rendered inline; values come from VESPER, never fabricated.

Operator introspection

Liveness/__healthsurface + vesper_bound (JSON)
Estate data/ops/estatelive VESPER panel data (JSON)
Manifest/ops/selfcockpit manifest + governance anchors (JSON)

Three internal JSON endpoints for operator introspection, all Access-gated. VESPA is the cockpit app; it reads VESPER, it is not VESPER.

Governance anchors

Chain 687e0c0f. Ruling 1: 16 filed / 73 specifications / 9 families. SOC 2 self-certified (no third-party audit claimed). Category positioning is architectural, not an achievement claim. Human sovereignty is supreme; AC-1 is the sole HITL authority.