This policy defines how third-party implementations may truthfully self-declare against public SRS/SRIP requirements without implying official Sigma certification, endorsement, partnership, approval, or badge authorization.
Any third party may make a truthful self-declaration if it follows the public specification license, attribution requirements, marks policy, and this self-declaration policy.
A self-declared implementation must use the phrase "self-declared" adjacent to the claimed conformance level wherever the claim appears.
A self-declaration should use clear wording such as:
Do not use "Sigma Certified", "Sigma Runtime Certified", official badges, ∿ as a certification mark, or language implying official endorsement unless the implementation is reviewed, approved, and listed by Sigma Stratum.
A self-declaration must identify the SRS/SRIP version, the claimed conformance level, the supported SRIPs, unsupported SRIPs, known deviations, and evidence artifacts.
Evidence should be reviewable, version-pinned, and specific to the implementation scope.
Every self-declaration must identify the SRS/SRIP version or publication date used.
If the implementation targets only a subset of SRIPs, the declaration must identify the included and excluded SRIPs.
Self-declared conformance is not official certification and must not be presented as endorsement, approval, partnership, or certification by Sigma Stratum.
Attribution, citation, implementation, or self-declaration does not create official conformance registry status.
Sigma Stratum may request correction where a self-declaration is misleading, incomplete, not version-pinned, missing evidence, implying official certification, using protected marks without permission, or omitting known deviations.
Correction requests should identify the specific claim, the policy issue, and the requested correction.
Allowed:
Not allowed without approval: