Hypler: SI infrastructure and systems software

Products and infrastructure

Rangoon operating-system targets

Under development.

Operating-system terminology

LNSAT operating-system targets

Under development.

Operating-system terminology

IZIOS implementation choices

IZIOS processes supplier inputs into normalized records, combines structured filters with vector retrieval, serves product data through APIs, and keeps commerce transactions separate from availability truth.

  1. Supplier ingestion
  2. Normalized records
  3. Structured filters and vector retrieval
  4. APIs
  5. Commerce transactions

These are documented implementation choices. Supplier availability remains source-controlled; compile-time contracts and runtime validation serve different checks.

VUSL

Semantic interoperability under development

VUSL is a public semantic-interoperability design with an experimental offline Rust inspection subset. Rangoon integration is planned; native engines retain authorization and enforcement.

VUSL public GitHub README at b55e019, captured October 18, 2026; source evidence, not a connected runtime demonstration

VUSL AI systems and frameworks

Current source coverage and integration direction. No connected provider or framework adapter is qualified by this public draft.

  • Rangoon — Planned integration. Capability authoring, composition, revisions, export and inspection remain with Rangoon.
  • OpenShell — Offline source work. Synthetic typed-window mapping and an unmounted read-only client/host path; no qualified live gateway or VUSL network binding.
  • LNSAT — Offline evidence inspection. Native-shaped JSON decoder preserves authorization, attempts, receipts and reconciliation as distinct facts. No connected engine claim.
Frameworks and native standards (7)
  • LangGraph / LangSmith — Reference ecosystem / unassessed adapter. Named in the pinned Rangoon capability audit. No VUSL adapter or framework compatibility is qualified.
  • MCP / Agent Skills / MCP Apps — Native contract references. Tools, resources, prompts, skill packages and embedded application contracts keep their own versions and host requirements.
  • A2A / ACP / AG-UI — Native contract references. Agent tasks, editor sessions and UI events remain separate native lifecycles; listing them does not establish adapter support.
  • OpenAPI / AsyncAPI / CloudEvents — Native contract references. API descriptions, asynchronous interfaces and delivery metadata are not execution authority.
  • OpenTelemetry / Trace Context / OCSF — Native contract references. Telemetry, correlation and security-event representations do not prove authorization or an external effect.
  • OAuth / OIDC / SPIFFE — Identity references. Native identity and credential semantics remain independent. VUSL does not issue credentials or grants.
  • W3C PROV / SLSA — Provenance references. Provenance and build-evidence concepts require their own scoped evidence; a document digest is not an authenticated producer.

Scope and qualification details

Explore VUSL / Read the technical document