Hypler Software and SI Glossary
React
A JavaScript library for composing user interfaces from components.
How Hypler uses it: IZIOS uses React for customer and administrative interface composition.
Example: A search result, filter control, and inventory review panel can share reusable interface components.
TypeScript
A typed language that extends JavaScript and checks many data-shape mistakes before code runs.
How Hypler uses it: IZIOS uses TypeScript to make client and server contracts clearer to maintainers.
Example: A product response type can show which fields an interface may expect from an API.
Node.js
A JavaScript runtime used for server applications and build tooling.
How Hypler uses it: IZIOS uses Node.js for its server-side application runtime and supporting tooling.
Example: A server process receives an API request, applies application rules, and returns a defined response.
Express
A Node.js framework for HTTP routes and request middleware.
How Hypler uses it: IZIOS uses Express to define server API routes and request handling.
Example: A route can validate a request, call product services, and return a documented response.
PostgreSQL
A relational database for durable structured records, queries, and transactions.
How Hypler uses it: IZIOS uses PostgreSQL-backed records for catalog and operational data.
Example: Catalog records can join source identifiers, specifications, certificates, and availability evidence.
pgvector
A PostgreSQL extension that stores vectors and supports similarity search.
How Hypler uses it: IZIOS uses pgvector-backed retrieval for embeddings alongside structured product data.
Example: A broader search phrase can retrieve related product records while filters retain exact constraints.
Vite
A frontend development server and build tool for modern web applications.
How Hypler uses it: IZIOS uses Vite in its frontend build path.
Example: A developer can update an interface component and see the browser bundle refresh during development.
Ingestion
The controlled intake of external records so they can be normalized, validated, and used by a product.
How Hypler uses it: IZIOS ingests supplier inputs before they become searchable catalog records.
Example: A supplier file is parsed, checked, normalized, and connected to its source identity.
API
An application programming interface: a defined contract for software to request data or actions from another system.
How Hypler uses it: IZIOS exposes reusable product data through API boundaries instead of binding all business logic to one storefront.
Example: A connected client requests catalog data through a documented route and response shape.
Embeddings
Numeric representations of content that let software compare related meaning.
How Hypler uses it: IZIOS stores versioned embeddings for vector retrieval alongside source-aware product records.
Example: A natural-language search can compare its embedding with catalog embeddings to find related listings.
Transactions
A grouped database change that either completes as one consistent unit or is safely rolled back.
How Hypler uses it: IZIOS keeps commerce transactions distinct from supplier availability truth and discovery results.
Example: A hold workflow can write related records together while preserving the source evidence used for a decision.
Operating system
The software layer that manages a computer's hardware and provides the environment where applications run.
How Hypler uses it: LNSAT lists operating-system targets separately from runtime qualification evidence.
Example: A planned Linux, Windows, or macOS target still needs its own architecture, lifecycle, storage, and recovery evidence.
Model provider
An organization that offers models or model APIs that a system may evaluate as a target.
How Hypler uses it: Rangoon uses provider references as inspectable planning context for model targets.
Example: A capability plan can state its target assumptions without claiming an integration is shipped or supported.
VUSL
A provider-neutral semantic view for describing capabilities, observations and relationships while preserving native meaning.
How Hypler uses it: VUSL describes capabilities and observations across platforms. Rangoon is first consumer; an independent core is planned.
Example: A semantic observation identifies its native source and translation limits without granting permission.
Rust
A systems programming language with ownership and type rules that help control memory use and make interfaces explicit.
How Hypler uses it: The pinned VUSL conformance guide describes a Rust library that inspects supplied, bounded JSON offline.
Example: The inspector can return an accepted document or a fixed diagnostic; language choice alone does not prove security.
Python
A general-purpose programming language used for scripting, data processing and independent reference implementations.
How Hypler uses it: VUSL conformance documentation describes Python reference checks for the same bounded subset as the Rust inspector. This is not a Python SDK.
Example: Shared fixtures can compare accepted canonical bytes and refusals across implementations.
Canonicalization
Converting accepted data into one precisely defined byte representation so equivalent accepted inputs can be compared consistently.
How Hypler uses it: The experimental VUSL observation profile defines a bounded canonical representation and exact conformance vectors.
Example: A different whitespace layout may yield the same canonical bytes when the profile accepts both inputs; unknown fields still refuse.
Translation loss
Information or meaning that is omitted, transformed or cannot be preserved when one system represents another system’s records.
How Hypler uses it: VUSL keeps native identity and translation limits visible rather than implying that every semantic view is lossless.
Example: A projected policy report can preserve a reported decision without carrying engine authorization or proving an external effect.
Fail-closed inspection
Refusing an interpretation when required checks fail instead of guessing, truncating or treating missing evidence as success.
How Hypler uses it: The current VUSL profile rejects unsupported versions, duplicate fields, unknown core fields and inputs outside its bounds.
Example: A document over the byte limit returns a refusal rather than a partially accepted observation.
Document digest
A computed hash of document bytes that helps identify content; a hash by itself does not authenticate its author or grant authority.
How Hypler uses it: The VUSL source describes canonical SHA-256 expectations and a separately domain-separated document identity. These remain distinct from approval and execution evidence.
Example: Matching digests help compare content but cannot establish a cross-provider relationship or prove a resource changed.