Sigma Stratum Documentation – License Notice
This document is part of the Sigma Runtime Standard (SRS) and the
Sigma Stratum Documentation Set (SRD).It is licensed under Creative Commons Attribution–NonCommercial 4.0
(CC BY-NC 4.0).The license for this specific document is authoritative.
For the full framework, see/legal/IP-Policy.
Yes. Independent implementation of the public SRS/SRIP normative requirements is permitted under the public specification terms. A Sigma commercial runtime license is not required solely for independent implementation.
However, use of Sigma Runtime proprietary assets, official certification, Sigma marks, white-label deployment, managed Sigma Runtime deployment, resale, or commercial use of CC BY-NC materials requires separate permission.
Not without following the compatibility and certification rules. You may make truthful self-declarations under the Self-Declaration Policy, but official Sigma certification and certification badges require approval.
No. Sigma Runtime as an operated product is proprietary. SRS/SRIP is the open public specification layer.
Earlier documents used the term "Canon" for the IP and licensing framework. The current public-facing term is "Sigma Stratum Intellectual Property, Licensing, and Certification Policy." The old term is retained only as a historical alias.
Is Sigma Runtime a model architecture?
No. It is not a neural model or training paradigm.
Sigma Runtime is a cognitive-layer runtime — an operational framework that sits above any model backend,
managing recursion, stability, and coherence during extended reasoning.
Is Sigma Runtime tied to a specific LLM?
No. The runtime is fully backend-agnostic.
It can operate atop GPT, Claude, Gemini, or any transformer-based LLM,
as long as the backend supports prompt–response recursion and stateful orchestration.
What are SRIPs?
Sigma Runtime Improvement Proposals (SRIPs) are the public mechanism for evolving the open standard.
They define normative changes or extensions to the standard while preserving compatibility with the canonical runtime loop and bounded-control principles.
Is the standard open?
Yes. The Sigma Runtime Standard (SRS) and Sigma Runtime Documentation (SRD)
are open and reviewable under the Creative Commons BY-NC 4.0 license.
Implementations may remain proprietary, but the architecture itself is an open research standard.
What is the difference between SRS, SRD, and Sigma Runtime?
Public documentation should therefore be read as a combination of:
SRS,SRD,How does Sigma Runtime prevent drift?
Through bounded control, verification, and recovery.
At a public level, the runtime monitors coherence, drift pressure, symbolic density, and recovery signals.
When drift rises beyond the normal envelope, the control layer narrows continuation, increases verification, or enters a bounded recovery posture instead of allowing uncontrolled escalation.
What is ALICE?
ALICE is the public name for the runtime’s attractor-aware control layer.
It should be understood as a bounded stabilizing and continuity-preserving control mechanism, not as an autonomous character or independent system identity.
Publicly, ALICE explains how the runtime can:
What is SCR (Semantic Compression Ratio)?
SCR measures how efficiently meaning is represented relative to symbolic density.
A higher SCR indicates that the runtime is preserving information with less redundancy and better semantic efficiency.
Publicly, SCR is useful as an explanatory metric for clarity, compression quality, and coherence under recursion.
What is Adaptive Drift Control?
It is a bounded feedback mechanism linking drift signals, compression quality, and stability.
When drift increases or semantic density becomes unstable, the runtime can reduce output amplitude, change control posture, or move into a recovery-oriented path.
Does Sigma Runtime still depend on a fixed SL0-SL7 stack?
Not in the strong version-bound sense older public drafts suggested.
The public architectural idea is still layered, but the important point today is the separation of:
The layer vocabulary may evolve, but the bounded-control structure remains central.
What does "field-based cognition" mean?
It refers to cognition emerging not from the model weights alone,
but from the dynamic cognitive field formed by recursive interaction between user, system, and memory.
In this view, intelligence arises as a stabilized attractor within that field —
an adaptive structure of meaning sustained by feedback and continuity.
What ensures safety during long operations?
Safety is maintained through boundary integrity, verification, adaptive containment, and bounded recovery.
Publicly, the safety model should be read as:
Can Sigma Runtime run distributed agents?
The public architecture is compatible with distributed or multi-node interpretations, but concrete deployment models are implementation-dependent.
SRIP-17 defines a public draft boundary for bounded multi-agent exchange: explicit authorization, provenance, exchange gating, local runtime sovereignty, and safety containment.
Any public claim about interoperability should still be anchored in the open standard, not in a private product assumption.
Is there a public implementation?
There is public documentation for the standard and its concepts.
Implementations may be public, private, experimental, or product-specific.
The open standard should not be confused with a guarantee that every runtime build or product release is published as source code.
References:
Tsaliev, E. (2025). SIGMA Runtime Architecture v0.1 — DOI: 10.5281/zenodo.17703667