Canonical: https://hypler.com/glossary # Software and SI terms business owners ask about. Terms from Hypler's work: older system upgrades, source-backed data, SI review steps, private operations, code status, analytics systems, and approval-first automation. Public examples stay high-level so private infrastructure details remain private. All (60) Agent Infrastructure Authorization Code Ops Commerce Systems Data And Evidence Infrastructure Languages And Interoperability Operations SI & Intelligence Web Systems SI & Intelligence ## Super Intelligence (SI) Hypler's current language for its intelligence infrastructure direction, evolving from the earlier artificial intelligence (AI) term. ### How Hypler uses it Hypler engineers the model interfaces, data systems, workflows, permissions and evidence that increasingly capable intelligence systems need. ### Example A system connects a model to approved sources and typed tools, with evaluation and scoped authorization before consequential actions. Artificial Intelligence (AI) MCP Approval-First Automation SI & Intelligence ## Artificial Intelligence (AI) The earlier term retained in Hypler's historical sources, established technical references, vendor names and search aliases. ### How Hypler uses it Current company copy leads with SI while historical AI titles and stable URLs remain accurate and accessible. ### Example An older AI briefing links to current SI infrastructure work without changing the original announcement title. Super Intelligence (SI) Model Router SI Review Packet Agent Infrastructure ## MCP Model Context Protocol: a standard way for SI agents to call typed tools and read structured context. ### How Hypler uses it Hypler uses MCP-style contracts so agents can read, diagnose, propose, and stage work without broad shell, database, or runtime access. ### Example A scoped agent resource can expose safe tools for inventory, code status, review packets, and staged plans. Tool Registry Approval-First Automation Resource Audience Agent Infrastructure ## MCP Gateway A central host where agent tools are exposed through stable routes, scopes, schemas, and authorization boundaries. ### How Hypler uses it Hypler models path-scoped gateways with separate resources so authority does not leak between systems. ### Example Ops and telemetry resources can share gateway patterns while keeping separate audiences and scopes. Protected Resource Metadata Resource Audience Scope Authorization ## Protected Resource Metadata A machine-readable document that tells clients how a protected API or MCP resource should be authorized. ### How Hypler uses it Hypler models metadata for each future MCP resource before enabling runtime token parsing or live endpoints. ### Example Protected-resource metadata can describe which authorization server and scopes a resource expects. WWW-Authenticate Resource Audience Bearer Token Authorization ## Resource Audience The exact resource a token is meant for. A token for one resource should not be accepted by another resource. ### How Hypler uses it Hypler keeps MCP resources separate even if they share one gateway hostname. ### Example A token issued for one operations resource should not authorize a different telemetry or workflow resource. MCP Gateway Scope Bearer Token Authorization ## Scope A named permission such as read, propose, or stage that limits what a client can do. ### How Hypler uses it Hypler scopes distinguish safe reads from proposals, stage previews, and any future approved execution. ### Example `hypler.ops.read` can read inventory; `hypler.ops.stage` can prepare previews but still does not execute. Approval-First Automation Tool Registry Break-Glass Authorization ## WWW-Authenticate An HTTP response header that tells a client why authentication failed and what authorization information is needed. ### How Hypler uses it Hypler’s source-only contract models the failure shape before registering any live MCP endpoint. ### Example A `401` response can point to protected resource metadata and required scopes. Protected Resource Metadata Bearer Token MCP Gateway Agent Infrastructure ## Tool Registry A catalog of available agent tools, their input/output contracts, permissions, source files, and audit expectations. ### How Hypler uses it Hypler keeps the registry visible in Ops so humans can inspect what agents are allowed to do. ### Example A tool can be marked `read`, `diagnose`, `propose`, or `stage` with `mutates=false` until execution is approved. MCP Audit Event Approval-First Automation Operations ## Approval-First Automation Automation that moves through review and approval before any live state-changing action occurs. ### How Hypler uses it Hypler stages automation as observe, diagnose, propose, preview, approve, then execute only after contracts and rollback paths exist. ### Example A security fix can first appear as a patch preview and approval review instead of directly editing files or restarting services. Stage Preview Audit Event Break-Glass Operations ## Stage Preview A structured preview of a future change that does not write files, run commands, deploy, or mutate runtime state. ### How Hypler uses it Hypler uses stage previews for inventory gaps, system scaffolds, security patch requests, and future automation bundles. ### Example A stage preview can list planned file changes and rollback notes while keeping `writes_files=false`. Approval-First Automation Patch Preview Tool Registry Data And Evidence ## Source-Backed Evidence Information that can point back to a source row, citation, API response, event, or stored record. ### How Hypler uses it Hypler favors evidence visible in UI surfaces instead of burying proof in logs or ad hoc database queries. ### Example LNSAT source filters and field evidence packets let operators inspect where a signal came from. Evidence Packet Citation Ledger Source Health Data And Evidence ## Evidence Packet A packaged summary of facts, sources, traces, and context that an operator or SI system can review. ### How Hypler uses it LNSAT and modernization systems use packet-style thinking to turn raw data into inspectable operational context. ### Example A field event can include source metadata, extracted facts, confidence, map context, and API visibility. Source-Backed Evidence SI Review Packet Citation Ledger SI & Intelligence ## SI Review Packet A compact structured packet prepared for an SI model to review, summarize, classify, or prioritize. ### How Hypler uses it Hypler feeds models curated operational context instead of giving them raw unrestricted backend access. ### Example An Ops review packet can merge graph changes, code status, validation state, and blocked actions for analysis. Source-Backed Evidence Model Routing Operator Visibility SI & Intelligence ## Model Routing Choosing which SI model or provider should handle a task based on cost, latency, context, privacy, or capability. ### How Hypler uses it Hypler separates conversational routing, deep review, local model lanes, and hosted API model use. ### Example A small model can handle routing while a stronger model reviews complex infrastructure packets. SI Review Packet Private Cloud Agent Tool Gateway Infrastructure ## Private Cloud A privately controlled environment for services, dashboards, data, models, and operations. ### How Hypler uses it Hypler uses private cloud language publicly while keeping exact hardware, IP, tunnel, and credential details private. ### Example Ops dashboards can show system status and service health without publishing sensitive host details. Operational Map Service Registry Private Route Infrastructure ## Operational Map A visual or structured map of systems, services, routes, dependencies, data stores, and job flows. ### How Hypler uses it Hypler maps operating systems so operators can see how products, services, databases, jobs, and SI lanes connect. ### Example A map can connect a public product, its admin surface, data pipeline, analytics DB, and SI review lane. Service Registry Route Policy Operator Visibility Infrastructure ## Service Registry An inventory of services, routes, ports, owners, runbooks, dependencies, and health checks. ### How Hypler uses it Hypler stores non-secret service facts so the Ops UI can explain what exists and where to inspect it. ### Example A service row can identify its system, role, health endpoint, dependency edges, and runbook pointer. Operational Map Source Health Private Cloud Data And Evidence ## Source Health Status and freshness information for external APIs, feeds, records, imports, crawls, or source-run pipelines. ### How Hypler uses it LNSAT, modernization, and analytics surfaces use source health to show whether evidence is fresh, stale, blocked, or failed. ### Example A map signal is more useful when the operator can see source freshness and last successful fetch context. Source-Backed Evidence Evidence Packet Operational Map Data And Evidence ## Signal Map A UI that organizes operational, business, or source signals into a map-like surface for quick scanning. ### How Hypler uses it LNSAT, modernization, and private-ops surfaces use signal-map patterns to make important data visible without digging through tables. ### Example Source, route, relationship, evidence, and system-health signals can be grouped into one operator-facing surface. Operator Visibility Source Health SI Review Packet Web Systems ## API Layer The server-side contract that serves data and actions to one or more interfaces, integrations, or agents. ### How Hypler uses it Hypler builds API layers first so product UI, agent tools, partner systems, and internal dashboards do not each invent their own business logic. ### Example Commerce search, vector lookup, cart sync, stats, and design jobs are served through API routes rather than being trapped in a storefront page. Route Policy Structured Data Partner Feed Infrastructure ## Cache Layer A fast read path that stores expensive or repeated results so the product does not recompute or refetch them on every request. ### How Hypler uses it Hypler uses caches for search results, filter counts, media URLs, source snapshots, and operator summaries where freshness rules allow it. ### Example A catalog search page can use cached counts and indexed records while a background import updates supplier data. Fast Data Access API Layer Source Health Infrastructure ## Fast Data Access A design approach where schema, indexes, caches, and job boundaries make common reads quick and predictable. ### How Hypler uses it Hypler designs high-traffic paths around indexed Postgres queries, normalized records, cacheable responses, and dedicated workers for slow tasks. ### Example Search by carat, cut, color, clarity, price, shape, and semantic intent should return quickly without waiting for supplier APIs or SI jobs. Cache Layer Dedicated Compute Lane Postgres Infrastructure ## Dedicated Compute Lane A separated runtime path for expensive work such as models, embeddings, image analysis, imports, or batch review. ### How Hypler uses it Hypler keeps heavy jobs away from request paths so public products stay responsive while private workers process slower work. ### Example SI design generation or evidence embedding can run through a worker lane while the UI shows status and cached product data. Job Queue Private Cloud Model Routing Operations ## Job Queue A controlled backlog for work that should run asynchronously with status, retries, priority, and audit state. ### How Hypler uses it Hypler uses queue-shaped workflows for imports, SI design generation, source processing, embedding backfills, and review packet creation. ### Example A design request can become a job with pending, processing, completed, failed, and cancelled states. Dedicated Compute Lane Audit Event Approval-First Automation Commerce Systems ## Partner Feed An external supplier or partner data source that must be normalized before it can safely power product flows. ### How Hypler uses it Hypler treats partner feeds as contracts with import, delta, validation, availability, and checkout-handoff rules. ### Example A supplier feed can update inventory, media, attributes, pricing, and availability without blocking the user-facing path. API Layer Source Health Fast Data Access SI & Intelligence ## Semantic Search Search that understands meaning and intent, not only exact keywords. ### How Hypler uses it Hypler uses semantic ideas for evidence search, product search, source lookup, and agent-readable context. ### Example A user can search for a business concept and still find related records that use different wording. Embedding Source-Backed Evidence SI Search Optimization SI & Intelligence ## Embedding A numeric representation of text or data that lets systems compare meaning and similarity. ### How Hypler uses it Hypler plans embedding fabric carefully because vectors need model metadata, namespace control, and regeneration rules. ### Example A source fact can be embedded so related evidence can be found by meaning, not only by exact text. Semantic Search Vector Namespace Model Routing SI & Intelligence ## Vector Namespace A separated collection of vector records, usually grouped by model, system, source, or purpose. ### How Hypler uses it Hypler treats namespaces as operational contracts so model changes do not silently corrupt search behavior. ### Example Operational evidence vectors should not be mixed with another system's vectors unless the namespace policy says so. Embedding Semantic Search Source-Backed Evidence SI & Intelligence ## SI Search Optimization Structuring content so SI assistants and semantic crawlers can understand and cite it. ### How Hypler uses it Hypler applies this to public product pages, APIs, structured docs, and source-backed content. ### Example A product or service page should explain what exists, how it works, and what evidence supports it. Semantic Search Source-Backed Evidence Structured Data Web Systems ## Structured Data Machine-readable metadata that describes pages, products, services, articles, or entities. ### How Hypler uses it Hypler uses structured data for public discoverability and internal source clarity. ### Example A commerce product can expose product attributes, availability, and entity relationships in a parseable shape. SI Search Optimization Semantic Search Source-Backed Evidence Infrastructure ## Route Policy Rules for how systems should connect: public edge, private route, local service, brokered path, or blocked path. ### How Hypler uses it Hypler models route policy so UI and agents know which paths are allowed and which require approval. ### Example A public website route and a private ops route can be documented as different operational surfaces. Private Route Operational Map Approval-First Automation Infrastructure ## Private Route A route meant for authenticated operators or trusted systems, not public visitors. ### How Hypler uses it Hypler separates public marketing/product surfaces from private operations and agent-control surfaces. ### Example A private Ops dashboard can show internal service state while the public site only describes capabilities. Private Cloud Route Policy MCP Gateway Operations ## Audit Event A record of who or what acted, what was requested, what resources were touched, and what happened. ### How Hypler uses it Hypler designs tool calls, approvals, review packets, and future execution paths to leave audit evidence. ### Example A staged patch request should record actor, input digest, output digest, approval state, and touched resources. Approval-First Automation Tool Registry Idempotency Operations ## Idempotency A design rule that lets the same request run more than once without accidentally duplicating a write or action. ### How Hypler uses it Hypler models idempotency before any approval or persistence write is allowed. ### Example An approval decision can include an idempotency key so retries do not create duplicate audit rows. Audit Event Approval-First Automation Transaction Preview Operations ## Transaction Preview A no-write outline of the database rows and ordered steps a future transaction would perform. ### How Hypler uses it Hypler uses transaction previews for approval persistence and operational summary persistence before live writes exist. ### Example A preview can show approval row update, audit insert, touched-resource rows, idempotency record, and rollback notes. Stage Preview Idempotency Audit Event Code Ops ## Patch Preview A proposed code or configuration change shown as structured review data before any file is edited. ### How Hypler uses it Hypler stage tools can preview missing inventory fields, security changes, and system scaffolds without applying patches. ### Example A patch preview can identify target files, proposed edits, approval state, and rollback requirements. Stage Preview Approval-First Automation Code Ops Code Ops ## Code Ops Operational visibility into repositories, changes, validation commands, impacted services, and protected paths. ### How Hypler uses it Hypler treats code status as an operations surface, not just something hidden in a developer terminal. ### Example An Ops page can show dirty files, branch status, validation commands, and which services a change could affect. Patch Preview Tool Registry Operator Visibility Operations ## Operator Visibility Making progress, evidence, blocked work, risks, counts, and next actions visible to the person running the system. ### How Hypler uses it Hypler prefers surfacing state in `/agents`, maps, workloads, and admin views instead of leaving it buried in logs. ### Example Embedding progress, source health, approval state, and contract status should be visible in the UI. Operational Map Signal Map SI Review Packet Authorization ## Break-Glass A high-risk emergency permission level for broad or destructive recovery actions. ### How Hypler uses it Hypler keeps break-glass tools absent from current public/agent scaffolds until explicitly designed and approved. ### Example A restart, destructive migration, or emergency bypass should not share the same gate as a read-only inventory tool. Scope Approval-First Automation Tool Registry Web Systems ## 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 Vite API [Read related engineering guide](https://hypler.com/wiki/software-architecture) Web Systems ## 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. React API Transactions [Read related engineering guide](https://hypler.com/wiki/typescript-contracts-interfaces) Web Systems ## 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 API Vite [Read related engineering guide](https://hypler.com/wiki/api-event-contracts) Web Systems ## 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. Node.js API Transactions [Read related engineering guide](https://hypler.com/wiki/api-event-contracts) Data And Evidence ## 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 Transactions Ingestion [Read related engineering guide](https://hypler.com/wiki/sql-durability-audit) Data And 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. Embeddings PostgreSQL Ingestion [Read related engineering guide](https://hypler.com/wiki/retrieval-source-quality) Web Systems ## 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. React TypeScript Node.js [Read related engineering guide](https://hypler.com/wiki/software-architecture) Data And Evidence ## 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. PostgreSQL Embeddings API [Read related engineering guide](https://hypler.com/wiki/retrieval-source-quality) Web Systems ## 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. Express Node.js Transactions [Read related engineering guide](https://hypler.com/wiki/api-event-contracts) Data And Evidence ## 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. pgvector Ingestion Semantic Search [Read related engineering guide](https://hypler.com/wiki/retrieval-source-quality) Data And Evidence ## 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. PostgreSQL API Idempotency [Read related engineering guide](https://hypler.com/wiki/sql-durability-audit) Infrastructure ## 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. Testing and Observability API Source-Backed Evidence [Read related engineering guide](https://hypler.com/wiki/testing-observability) SI & Intelligence ## 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. API Model Routing Capability [Read related engineering guide](https://hypler.com/wiki/software-architecture) Languages And Interoperability ## 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 Translation loss Document digest [Read related engineering guide](https://hypler.com/vusl) Languages And Interoperability ## 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 Fail-closed inspection Canonicalization [Read related engineering guide](https://hypler.com/wiki/rust-systems-security) Languages And Interoperability ## 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. Rust Canonicalization Document digest [Read related engineering guide](https://hypler.com/wiki/testing-observability) Languages And Interoperability ## 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. Document digest Rust Python [Read related engineering guide](https://hypler.com/vusl) Languages And Interoperability ## 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. VUSL Fail-closed inspection Source-Backed Evidence [Read related engineering guide](https://hypler.com/vusl) Languages And Interoperability ## 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. Rust Translation loss Canonicalization [Read related engineering guide](https://hypler.com/vusl) Languages And Interoperability ## 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. Canonicalization VUSL Source-Backed Evidence [Read related engineering guide](https://hypler.com/vusl)