Beta Version

sigMAX is currently in beta and under very active development.

The project is usable for exploration, technical validation, architecture experiments, generator tests, runtime evaluation and documentation review. It should not yet be treated as a stable production platform for critical workloads.

What Beta Means

The beta stage means the core ideas are being exercised in real code, but the shape of the platform is still moving.

You should 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

sigMAX is best used today 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

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.
Generated Compose files	Local stack shape may change as component discovery and storage wiring mature.
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

When evaluating sigMAX, keep enough context to reproduce what happened:

repository commit hashes;
generated contracts and agreements;
runtime configuration;
Docker image tags or build metadata;
test input and output samples;
validation logs.

Not Yet A Production Promise

The beta does not yet promise a fully stable operational surface.

Before any serious deployment, generated code, runtime configuration, route bindings, storage behavior, HTTP policies, secrets, limits and container outputs should be inspected manually.

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.