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.
The SRIP Process defines how the Sigma Runtime Standard (SRS) evolves through transparent, peer-reviewed contributions under the governance of the Sigma Stratum Research Group (SSRG).
Each SRIP represents a proposed modification, extension, or clarification of the Sigma Runtime architecture.
All accepted SRIPs are versioned, archived, and integrated into the canonical SRS specification, while all revisions and historical proposals are tracked in the SRIP Registry.
| Stage | Description |
|---|---|
| 1. Draft | Initial specification authored by contributor(s). Must follow the SRIP template and include motivation, rationale, and technical description. |
| 2. Review | Technical and conceptual evaluation by the SSRG Steering Committee and designated reviewers. |
| 3. Revision | Updates made based on reviewer and editor feedback. |
| 4. Approval | Steering Committee votes to accept, defer, or reject the SRIP. |
| 5. Integration | Editors merge the approved SRIP into the canonical Sigma Runtime Standard (SRS) branch. |
| 6. Release | The change is included in the next official Sigma Runtime Standard version and archived under a DOI. |
SRIP-01, SRIP-02, etc.).SRIP-00 defines foundational and procedural rules.All SRIPs beginning with SRIP-08 and later are tracked through the
Sigma Stratum SRIP Registry, located under /registry/ in the
sigmastratum/documentation repository.
This ensures that:
Only Active SRIPs are listed in the /srs/active-srips.md index,
while the Registry contains the complete historical record.
To submit a new SRIP:
sigmastratum/documentation repository.srip-XX-your-title./templates/SRIP-TEMPLATE.md.SRIP Proposal.Upon approval, the SRIP will be merged and tagged for the next release cycle,
and an archival copy will be stored in the /registry/ directory.
All SRIPs are reviewed by:
Each accepted SRIP is:
/srs/);/registry/);This two-tier archival system (Active + Registry) ensures that the canonical runtime
remains lightweight, while the Registry preserves a full evolutionary record
of all proposals, drafts, and superseded versions.
The SRIP process ensures:
For general inquiries or submissions:
contact@sigmastratum.org
Summary:
The SRIP Process provides a structured path for the evolution of the Sigma Runtime Standard — ensuring every architectural change is transparent, reviewed, archived, and permanently recorded in the Sigma Stratum Registry as part of the open standard framework.