Beta Version
Beta Version
Section titled “Beta Version”sigMAX is currently in beta and under very active development.
Evaluation builds are intended for exploration, technical validation, architecture experiments, generator tests, runtime evaluation and documentation review. Access is subject to the supplied distribution terms. It should not yet be treated as a stable production platform for critical workloads.
Editions and Execution
Section titled “Editions and Execution”sigMAX is proprietary software with two editions. Core uses Docker Compose with Host and Config on one host; code executes in a container without a dedicated execution isolation boundary. Pro uses Kubernetes and the COS2000 executor in a KubeVirt VM.
Product architecture and implementation readiness are separate concerns. The executor reference distinguishes the COS2000 code already present from the Kubernetes integration that still needs deployment validation. Evaluation terms and available packages are described through access and editions information.
What Beta Means
Section titled “What Beta Means”Core ideas are being exercised in real code. Expect:
- frequent changes in contracts, agreements and generated artifacts;
- runtime behavior that may evolve as primitives are refined;
- limits that are intentionally conservative during testing;
- documentation that may be updated as implementation details settle;
- breaking changes between repository revisions;
- incomplete tooling around production hardening.
Recommended Use
Section titled “Recommended Use”Use evaluation builds for:
- local tests and demonstrations;
- validating contract-first generation workflows;
- reviewing generated C/WASM and runtime behavior;
- experimenting with component boundaries;
- comparing generated agreements against expected architecture;
- giving feedback before the stable surface is frozen.
What Is Moving
Section titled “What Is Moving”The most active areas are the places where generated output meets runtime behavior.
| Area | Beta expectation |
|---|---|
| Pseudocode DSL | Keywords, formatting and validation rules may still be refined. |
| Runtime primitives | Names, limits and capability checks may evolve as tests reveal edge cases. |
| Deployment packaging | Core Host + Config Compose packaging and Pro KubeVirt integration must be checked against the supplied release. |
| Agreements | Evidence fields can grow as validation becomes more precise. |
| Studio and documentation UI | Presentation can change quickly while the model stabilizes. |
What To Keep Stable In Tests
Section titled “What To Keep Stable In Tests”When evaluating sigMAX, keep enough context to reproduce what happened:
- supplied release identifiers and source revisions when available;
- generated contracts and agreements;
- runtime configuration;
- container image digests, build metadata and, for Pro, executor VM image identifiers;
- test input and output samples;
- validation logs.
Not Yet A Production Promise
Section titled “Not Yet A Production Promise”The operational surface is not yet stable. Before serious deployment, manually inspect generated code, runtime configuration, routes, storage behavior, HTTP policies, secrets, limits and container outputs.
Feedback Is Expected
Section titled “Feedback Is Expected”The useful part of a beta is feedback. Reports about unclear documentation, unsafe defaults, missing validation, confusing generated output or runtime edge cases help stabilize the project faster.
sigMAX is moving quickly, so this page should be read as a maturity note: the direction is intentional, but the production contract is not final yet.