sigMAX Studio
sigMAX Studio
Section titled “sigMAX Studio”sigMAX Studio is the interface for working with sigMAX projects.
It gives a graphical view over contracts, components, generated binaries, documentation, runtime status and generation progress. Studio does not replace the contract-first model; it makes the model easier to inspect, navigate and operate.
Core Studio
Section titled “Core Studio”The Core edition includes a lightweight Studio interface exposed through Nginx.
This minimal interface focuses on local inspection:
- browsing generated documentation;
- exposing FrontMark-based content;
- visualizing the generated project structure;
- inspecting contracts and agreements;
- following generation status;
- checking runtime status and health information.
It is intentionally limited. It is not a full managed control plane and should not be described as an automatically generated application frontend.
Typical Workflow
Section titled “Typical Workflow”Studio should make the generated project easier to inspect in the order engineers naturally debug it.
| Step | What Studio should help inspect |
|---|---|
| Intent and contracts | Application, component and binary expectations. |
| Generation | Produced files, warnings, logs and deterministic outputs. |
| Validation | Agreement results, drift reports and failed checks. |
| Runtime | Health, routes, OpenAPI, WASM module status and primitive usage. |
| Documentation | Generated docs, FrontMark pages and source links. |
In Core, this workflow stays lightweight. It is mainly a readable local surface over generated artifacts and runtime status.
Full Studio Experience
Section titled “Full Studio Experience”The complete Studio experience can provide richer authoring, inspection and operational workflows:
- editing intent and contract files;
- visualizing applications and component relationships;
- inspecting generated components and binaries;
- browsing generated APIs and documentation;
- following the generation flow step by step;
- showing runtime and generation status;
- relaunching generation steps;
- navigating validation results and drift reports;
- connecting to professional Enterprise workflows.
Core vs Full Studio
Section titled “Core vs Full Studio”| Area | Core Studio | Full Studio |
|---|---|---|
| Local documentation | Included | Included |
| Generated artifact inspection | Lightweight | Richer navigation and comparison |
| Contract editing | Limited or file-based | Guided editing workflows |
| Generation control | Local/manual | Managed workflows and history |
| Drift and validation views | Basic inspection | Review-oriented dashboards |
| Team features | Not the focus | Governance, roles and audit trail |
Boundary
Section titled “Boundary”Studio remains an interface layer.
It does not own the generation model, the runtime model, storage behavior or deployment topology. Those responsibilities stay with Core or Enterprise depending on the edition and deployment context.