Glossary
Glossary
Section titled “Glossary”This glossary gathers the main sigMAX vocabulary used across the documentation.
Agreement
Section titled “Agreement”Effective state produced after generation, validation or execution.
Application Contract
Section titled “Application Contract”Contract describing the full application architecture, services, networks, exposure and constraints.
Architecture Model
Section titled “Architecture Model”Structured description of components, dependencies, runtime boundaries and infrastructure choices.
Artifact
Section titled “Artifact”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.
Auditability
Section titled “Auditability”Ability to trace what was requested, generated, validated and deployed.
Binary Agreement
Section titled “Binary Agreement”Effective validated state of a WASM executable and its allowed execution boundary.
Binary Contract
Section titled “Binary Contract”Contract describing one WASM executable, its interfaces, constraints and allowed primitives.
Binary Model
Section titled “Binary Model”Layer that describes executable artifacts, deterministic C/WASM generation and binary agreements.
Blueprint
Section titled “Blueprint”Intermediate architecture intent used before contracts and generated artifacts are finalized.
C subset
Section titled “C subset”Controlled deterministic C-like subset used as a compilation path toward WASM.
c_repr
Section titled “c_repr”C-compatible binary memory layout exchanged with WASM for selected typed values.
Capability
Section titled “Capability”Explicit runtime permission required before a WASM module can use a sensitive primitive.
Certificate
Section titled “Certificate”Credential or TLS material used by managed network and exposure layers.
Compiler toolchain used to produce wasm32 artifacts from the deterministic C subset.
Component
Section titled “Component”Modular application unit described by contracts and executed or integrated through the runtime model.
Component Contract
Section titled “Component Contract”Contract describing one component, its interfaces, dependencies and expected behavior.
Component Model
Section titled “Component Model”Representation of components, boundaries, communication and generated implementation artifacts.
Component Registry
Section titled “Component Registry”Enterprise registry for reusable components, templates or generated assets.
Container
Section titled “Container”Packaged runtime unit used to run generated services or supporting infrastructure.
Container Network
Section titled “Container Network”Network topology connecting local or managed containers.
Contract
Section titled “Contract”Expected state before generation or execution.
Contract-first
Section titled “Contract-first”Design approach where expected behavior and boundaries are described before code or deployment output.
Controlled Generation
Section titled “Controlled Generation”Generation flow where LLM output is constrained by contracts, schemas, deterministic tooling and validation.
Controlled Pseudo-code
Section titled “Controlled Pseudo-code”Constrained pseudo-code representation used before deterministic code generation.
Open source sigMAX foundation with contracts, agreements, runtime primitives and a minimal Studio interface.
Runtime integration layer that can support internal service invocation and component-to-component concerns.
Declarative Storage
Section titled “Declarative Storage”Storage behavior described as configuration and exposed through controlled runtime operations.
Deterministic Generation
Section titled “Deterministic Generation”Generation process intended to produce reproducible artifacts from the same contract and inputs.
Deterministic Tooling
Section titled “Deterministic Tooling”Toolchain stages that avoid uncontrolled output drift.
Document Intermediate Representation used for rendered documents, reports, pages and documentation.
Docker Compose
Section titled “Docker Compose”Local orchestration target used by Core-oriented deployments.
Drift Detection
Section titled “Drift Detection”Process for identifying divergence between expected state and produced or deployed state.
Domain-specific language used to represent constrained intent, pseudo-code or configuration.
Effective State
Section titled “Effective State”State that actually exists after generation, validation or execution.
Enterprise
Section titled “Enterprise”Professional and managed sigMAX edition available at https://sigmax.build.
Evidence
Section titled “Evidence”Data proving what was generated, validated, executed or observed.
Execution Boundary
Section titled “Execution Boundary”Limit around what executable code can access or perform at runtime.
Expected State
Section titled “Expected State”State described by contracts before execution or generation.
Explicit Imports
Section titled “Explicit Imports”WASM imports that expose named runtime capabilities instead of implicit host access.
Final Code Boundary
Section titled “Final Code Boundary”Point where generated code becomes controlled executable output and should no longer be freely rewritten.
FrontMark
Section titled “FrontMark”Enriched Markdown layer used for documentation and lightweight frontend content.
Generated Artifact
Section titled “Generated Artifact”Any output created by the generation pipeline.
Generated Stack
Section titled “Generated Stack”Set of generated services, configuration, runtime assets and documentation.
Generative Drift
Section titled “Generative Drift”Divergence between intended architecture and produced artifacts.
Generic Operation
Section titled “Generic Operation”Runtime operation described at a generic level instead of hard-coded per implementation.
Grafana
Section titled “Grafana”Dashboard tool commonly used for observability views.
Health Check
Section titled “Health Check”Endpoint or signal used to verify service readiness or availability.
Hexagonal Architecture
Section titled “Hexagonal Architecture”Architecture style separating domain logic from infrastructure adapters.
High Coupling
Section titled “High Coupling”Intentional close coupling inside a bounded component or functional domain.
IA86 Computer Consulting
Section titled “IA86 Computer Consulting”Professional contact and support entity for sigMAX.
Ingress Controller
Section titled “Ingress Controller”Kubernetes component that manages inbound traffic routing.
Intent
Section titled “Intent”Human or model-authored description of the expected architecture or behavior.
Internal Sidecar
Section titled “Internal Sidecar”Companion runtime process used internally for component or service integration.
Isolation
Section titled “Isolation”Runtime property that limits direct access between executable code and the host.
No term yet.
No term yet.
Language model used to help describe intent, contracts, pseudo-code or documentation under constraints.
Local Artifact
Section titled “Local Artifact”Artifact produced or inspected in a local Core environment.
Runtime records emitted for debugging, traceability and observability.
Log aggregation system often paired with Grafana.
Low Coupling
Section titled “Low Coupling”Architecture property where components interact through explicit contracts and narrow interfaces.
Managed Network
Section titled “Managed Network”Enterprise-managed routing, certificates, ingress, reverse proxy and service exposure.
Markdown
Section titled “Markdown”Text format used as the base authoring format for documentation.
Metrics
Section titled “Metrics”Quantitative runtime signals used for monitoring and analysis.
Microservice
Section titled “Microservice”Independently deployable service participating in a larger application architecture.
Object storage option that can be used for extended storage in Enterprise contexts.
MkDocs Material
Section titled “MkDocs Material”Documentation syntax and visual convention emulated by FrontMark features.
Modular Architecture
Section titled “Modular Architecture”Architecture composed of explicit, bounded and reusable components.
Workflow automation tool referenced by the documentation tooling ecosystem.
Native Call
Section titled “Native Call”Host-side operation exposed to WASM only through an explicit runtime primitive.
Network Model
Section titled “Network Model”Representation of routes, exposure, service paths and communication boundaries.
Web server used in Core to expose the lightweight Studio interface and FrontMark content.
ObjectIR
Section titled “ObjectIR”Object Intermediate Representation for structured business values and typed data.
Observability
Section titled “Observability”Runtime visibility through logs, metrics, traces, health checks and dashboards.
OCI Container
Section titled “OCI Container”Container image format used for portable deployment artifacts.
Open Source
Section titled “Open Source”Core distribution model for the foundational sigMAX runtime and tooling.
OpenAPI
Section titled “OpenAPI”API description format that can describe HTTP contracts and generated interfaces.
Primitive
Section titled “Primitive”Controlled host capability exposed by the runtime to a WASM module.
Professional Support
Section titled “Professional Support”Commercial assistance, packaging, integration and operational support around sigMAX Enterprise.
Prometheus
Section titled “Prometheus”Metrics collection system commonly used in observability stacks.
Pseudo-code DSL
Section titled “Pseudo-code DSL”Controlled pseudo-code language used before deterministic generation.
No term yet.
Role-based access control used in Enterprise governance contexts.
Additional database or cache service that can be introduced when Enterprise architecture requires it.
Rendering
Section titled “Rendering”Transformation of DocIR or Markdown-like content into visible outputs such as HTML or PDF.
Reproducibility
Section titled “Reproducibility”Ability to regenerate equivalent artifacts from equivalent inputs.
Reverse Proxy
Section titled “Reverse Proxy”Infrastructure component such as Traefik used to route external traffic to internal services.
Routing
Section titled “Routing”Mapping of inbound requests to generated components or runtime handlers.
Runtime
Section titled “Runtime”Execution layer that loads WASM, exposes primitives, validates inputs and formats outputs.
Runtime API
Section titled “Runtime API”Host API surface exposed through controlled primitives.
Rust Runtime
Section titled “Rust Runtime”Rust implementation of the sigMAX host runtime and primitive boundary.
Managed software delivery mode supported by sigMAX Enterprise.
Security Model
Section titled “Security Model”Set of execution, network, contract and capability rules that constrain system behavior.
Service Invocation
Section titled “Service Invocation”Controlled call from one component or runtime context to another service.
sigMAX
Section titled “sigMAX”Secure Integrated Generator of Modular Architecture with eXecution runtime.
sigMAX Core
Section titled “sigMAX Core”Open source foundation for local and inspectable sigMAX projects.
sigMAX Enterprise
Section titled “sigMAX Enterprise”Professional and managed sigMAX edition for hosted workflows and enterprise capabilities.
Standardized Component
Section titled “Standardized Component”Component that follows known contracts, generation rules and runtime expectations.
Standardized Runtime
Section titled “Standardized Runtime”Runtime model that keeps execution predictable across generated components.
Runtime or business data read, written or validated through controlled boundaries.
storage.yaml
Section titled “storage.yaml”Declarative storage configuration describing storage behavior and allowed operations.
Studio
Section titled “Studio”Name of the sigMAX interface; Core includes a minimal Studio interface.
Svelte
Section titled “Svelte”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.
Testability
Section titled “Testability”Ability to verify generated behavior, contracts, agreements and runtime output.
Traefik
Section titled “Traefik”Reverse proxy option used in Enterprise-style managed deployment contexts.
No term yet.
Validation
Section titled “Validation”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 and isolated runtime logic.
WASM Import
Section titled “WASM Import”Function imported by a WASM module from the host runtime.
WASM Sandbox
Section titled “WASM Sandbox”Execution isolation boundary for WASM modules.
wasm32
Section titled “wasm32”Compilation target used for WebAssembly artifacts.
WebAssembly
Section titled “WebAssembly”Portable binary instruction format used by sigMAX for controlled execution.
Well-known Endpoint
Section titled “Well-known Endpoint”Predictable endpoint used for discovery, health, metadata or runtime inspection.
No term yet.
No term yet.
No term yet.