This glossary gathers the main sigMAX vocabulary used across the documentation.

Record of produced artifacts and evidence. Its creation does not mean validation passed; separate checks can remain pending or report failures.

Contract describing the full application architecture, services, networks, exposure and constraints.

Structured description of components, dependencies, runtime boundaries and infrastructure choices.

Generated or validated output such as code, configuration, documentation, container metadata or evidence.

Frontend site framework used to assemble pages, routes, content collections and static output.

Ability to trace what was requested, generated, validated and deployed.

Artifact record for a WASM executable, its contract and build evidence. Studio creates it before the separate binary validation report; it can initially be pending.

Contract describing one WASM executable, its interfaces, constraints and allowed primitives.

Layer that describes executable artifacts, C or MoonBit compilation to WASM, binary agreements and their validation.

Intermediate architecture intent used before contracts and generated artifacts are finalized.

Controlled deterministic C-like subset used as a compilation path toward WASM.

C-compatible binary memory layout exchanged with WASM for selected typed values.

Explicit runtime permission required before a WASM module can use a sensitive primitive.

Credential or TLS material used by managed network and exposure layers.

Compiler toolchain used to produce wasm32 artifacts from the deterministic C subset.

Modular application unit described by contracts and executed or integrated through the runtime model.

Contract describing one component, its interfaces, dependencies and expected behavior.

Representation of components, boundaries, communication and generated implementation artifacts.

Registry for reusable components, templates or generated assets; availability depends on the deployment.

Runtime service responsible for configuration and artifact distribution. It shares the same host as Host in Core.

Packaged runtime unit used to run generated services or supporting infrastructure.

Network topology connecting local or managed containers.

Expected state before generation or execution.

Design approach where expected behavior and boundaries are described before code or deployment output.

Generation flow where LLM output is constrained by contracts, schemas, deterministic tooling and validation.

Constrained pseudo-code representation used before deterministic code generation.

Proprietary sigMAX edition deployed with Docker Compose. Host and Config share one host; WASM executes in a container without a dedicated execution isolation boundary.

An x86-64 operating system with WAMR, native sigMAX primitives and the Radjae compiler. In the Pro architecture it runs in a virtual machine managed by KubeVirt. See the executor reference.

Runtime integration layer that can support internal service invocation and component-to-component concerns.

Storage behavior described as configuration and exposed through controlled runtime operations.

Generation process intended to produce reproducible artifacts from the same contract and inputs.

Toolchain stages that avoid uncontrolled output drift.

Document Intermediate Representation used for rendered documents, reports, pages and documentation.

Deployment mechanism for sigMAX Core, with Host and Config on the same host.

Process for identifying divergence between expected state and produced or deployed state.

Domain-specific language used to represent constrained intent, pseudo-code or configuration.

State that actually exists after generation, validation or execution.

Historical edition name in older documentation. The current professional edition is sigMAX Pro; Enterprise is not a third edition.

Data proving what was generated, validated, executed or observed.

Limit around what executable code can access or perform at runtime.

Service or execution engine that runs the selected WASM artifact. Core places execution in a container; Pro uses COS2000 in a VM.

State described by contracts before execution or generation.

WASM imports that expose named runtime capabilities instead of implicit host access.

Point where generated code becomes controlled executable output and should no longer be freely rewritten.

Enriched Markdown layer used for documentation and lightweight frontend content.

Any output created by the generation pipeline.

Set of generated services, configuration, runtime assets and documentation.

Divergence between intended architecture and produced artifacts.

Runtime operation described at a generic level instead of hard-coded per implementation.

Dashboard tool commonly used for observability views.

Endpoint or signal used to probe a service. A liveness response does not establish dependency readiness or business correctness; those need their own checks.

Architecture style separating domain logic from infrastructure adapters.

Intentional close coupling inside a bounded component or functional domain.

Rust runtime service that handles application requests and runtime-side capabilities. It is distinct from the physical host and from the Config service.

Professional contact and support entity for sigMAX.

Kubernetes component that manages inbound traffic routing.

Human or model-authored description of the expected architecture or behavior.

Companion runtime process used internally for component or service integration.

A boundary that limits access between execution environments. Core has no dedicated execution isolation beyond its container deployment; Pro uses a COS2000 VM managed by KubeVirt. WASM memory and import rules are a separate layer.

No term yet.

Orchestration platform used by sigMAX Pro.

Virtual-machine management layer within Kubernetes, used to run the COS2000 executor VM in Pro.

Language model used to help describe intent, contracts, pseudo-code or documentation under constraints.

Artifact produced or inspected in a local Core environment.

Runtime records emitted for debugging, traceability and observability.

Log aggregation system often paired with Grafana.

Architecture property where components interact through explicit contracts and narrow interfaces.

Routing, certificates, ingress, reverse proxy and service exposure operated for a deployment. These require explicit configuration; the Pro name alone does not promise a managed service.

Text format used as the base authoring format for documentation.

Quantitative runtime signals used for monitoring and analysis.

Independently deployable service participating in a larger application architecture.

Object storage used for versioned Studio artifacts and, through the MinIO extent, application files and named buckets. See file storage.

Documentation syntax and visual convention emulated by FrontMark features.

Architecture composed of explicit, bounded and reusable components.

Source-language target supported alongside the C subset by the sigMAX pseudo-code compiler, with bindings in runtime/moonbit.

Workflow automation tool referenced by the documentation tooling ecosystem.

Host-side operation exposed to WASM only through an explicit runtime primitive.

Representation of routes, exposure, service paths and communication boundaries.

Web server that can publish FrontMark pages or interface assets; it does not define the WASM execution boundary.

Object Intermediate Representation for structured business values and typed data.

Runtime visibility through logs, metrics, traces, health checks and dashboards.

Container image format used for portable deployment artifacts.

A software distribution model that does not apply to sigMAX Core or Pro. Third-party components retain their own licenses.

API description format that can describe HTTP contracts and generated interfaces.

Controlled host capability exposed by the runtime to a WASM module.

The proprietary Kubernetes edition with a COS2000 executor VM managed by KubeVirt. See sigMAX Pro.

Software distributed under its publisher’s terms. Both sigMAX editions use this distribution model.

Assistance, packaging, integration and operational support subject to agreed service terms.

Metrics collection system commonly used in observability stacks.

Controlled pseudo-code language used before deterministic generation.

No term yet.

Role-based access control. Its implementation and scope must be verified in the deployed services.

Shared application cache backend selected through the Redis extent. Rust cache primitives enforce TTL and namespace quotas; Studio’s job queues use Redis for a separate purpose. See cache and state.

Transformation of DocIR or Markdown-like content into visible outputs such as HTML or PDF.

Ability to regenerate equivalent artifacts from equivalent inputs.

Infrastructure component such as Traefik used to route external traffic to internal services.

Mapping of inbound requests to generated components or runtime handlers.

System of configuration, request handling and execution services. Host, Config and the selected executor have distinct responsibilities.

Host API surface exposed through controlled primitives.

Rust implementation of the sigMAX host runtime and primitive boundary.

Software delivered as a managed service. This is a hosting arrangement, not a synonym for sigMAX Pro.

Set of execution, network, contract and capability rules that constrain system behavior.

Controlled call from one component or runtime context to another service.

Secure Integrated Generator of Modular Architecture with eXecution runtime.

See Core: the proprietary Docker Compose edition on one host.

Proprietary Kubernetes edition with COS2000 executing WASM in a VM managed by KubeVirt.

Component that follows known contracts, generation rules and runtime expectations.

Runtime model that keeps execution predictable across generated components.

The state.* primitive family stores values for the current request only. Shared cache and persistent business storage have separate lifetimes; see runtime integrations.

Declarative storage configuration describing storage behavior and allowed operations.

Name used for sigMAX authoring and inspection tooling. Studio is not a third edition.

Component framework used for interactive frontend islands.

Structured documentation or UI representation for comparison and scanning.

FrontMark/MkDocs-style content switcher used to compare related views.

Ability to verify generated behavior, contracts, agreements and runtime output.

The selectable application ingress extent for hostname/path routing, TLS and configured authentication middleware. See networking and identity.

No term yet.

Process that checks artifacts, inputs, outputs or effective state against contracts.

Frontend development server and bundler used under the Astro/Svelte stack.

WebAssembly executable format used for portable runtime logic. Execution placement and infrastructure isolation depend on the edition.

Function imported by a WASM module from the host runtime.

Module-level memory and import controls. These must not be confused with the dedicated VM execution boundary provided by the Pro topology.

Compilation target used for WebAssembly artifacts.

Portable binary instruction format used by sigMAX for controlled execution.

Predictable endpoint used for discovery, health, metadata or runtime inspection.

No term yet.

No term yet.

No term yet.