Sigma Runtime Standard - Public Specification Notice
This document is part of the Sigma Runtime Standard (SRS) public specification layer.Specification License: CC BY 4.0.
Implementation Safe Harbor: independent implementation permitted under public SRS/SRIP terms.
Machine-readable artifacts: Apache License 2.0 where explicitly marked.
Marks / Certification: governed by Sigma Marks and Certification Policy.
Proprietary Runtime Assets: not licensed by this SRIP.Independent implementations of public SRS/SRIP normative requirements are welcome under the public specification terms.
Product assets, protected Sigma marks, official certification, compatibility badges, CC BY-NC commercial use, and patent commitments use the relevant policy or explicit covenant. Independent implementation, attribution, or citation does not imply certification, endorsement, partnership, official compatibility, or permission to use Sigma marks as product identity.
Sigma Runtime Improvement Proposal
| Field | Value |
|---|---|
| SRIP | SRIP-08 |
| Title | Phase Vector Model & PRM (Phase-Regulating Runtime Module) |
| Version | Foundational Draft |
| Status | Draft / Foundational Lineage |
| Date | 2026-04-17 |
| Authors / Contributors | E. Tsaliev |
| Owning Layer | Control Layer / Telemetry / Mathematics |
| Parent Specs | SRIP-03, SRIP-05, SRIP-06 |
| Related Specs | SRIP-09, SRIP-10, SRIP-11, SRIP-15 |
| Specification License | CC BY 4.0 |
| Implementation Safe Harbor | Independent implementation permitted under public SRS/SRIP terms |
| Machine-Readable Artifacts | Apache 2.0 where explicitly marked |
| Marks / Certification | Governed by Sigma Marks and Certification Policy |
| Proprietary Runtime Assets | Not licensed by this SRIP |
| Independent Implementation | Permitted under the public specification terms |
| Commercial Runtime Boundary | Relevant policy or explicit covenant for protected Sigma marks, official certification, managed deployment, white-label, resale, CC BY-NC commercial use, and patent commitments |
| Information Class | Open |
| Change Class | SRS-only |
| Normative Status | Retained as foundational lineage with status note; not the active public control baseline unless introduced through an explicit successor reference or new proposal path. |
| Conformance Level | Conceptual / Foundational Lineage |
| SRD Synchronization Action | Deferred review |
| Release Alignment Status | Foundational lineage; no active production control conformance claim is made by this document alone. |
Public Status Note
This document is retained as foundational lineage with status note, not as the active public control baseline.
Its vector-control and externalization model remains historically informative, but active public control and runtime-boundary language now lives elsewhere.
Any future active public successor must be introduced through an explicit successor reference or new proposal path.
Independent implementations of the public normative requirements in this SRIP are welcome under the applicable public specification terms.
No Sigma commercial runtime license is needed solely because an independent implementation follows those public normative requirements.
Product assets, protected Sigma marks, official certification, compatibility badges, CC BY-NC commercial use, and patent commitments use the relevant policy or explicit covenant. Independent implementation, attribution, or citation does not imply certification, endorsement, partnership, official compatibility, or permission to use Sigma marks as product identity.
SRIP-08 defines the Phase Vector Model (PVM) and its runtime implementation through the
Phase-Regulating Module (PRM) — the telemetry and synchronization layer of the ALICE controller.
This document should now be read as a foundational lineage specification for vector-based phase regulation in Sigma Runtime.
Subsequent proposals (SRIP-09 and higher) extend this foundation with distributed and higher-dimensional phase models.
Previous runtime versions represented phases as discrete labels.
This specification formalizes them as continuous vectors in a bounded cognitive phase space,
enabling mathematical computation of stability, drift, and resonance through angle-based metrics used in:
PSI (Phase Stability Index), PSD (Phase Stability Delta), and PRS (Phase Resonance Score).
Phase state is represented as a 3D unit vector:
[
\vec{P} = [p_s, p_r, p_c]
]
where:
The vector resides in normalized Euclidean space:
[
|\vec{P}| = 1
]
This representation allows continuous interpolation between cognitive phases
and enables geometric reasoning about stability, coherence, and resonance.
The expected phase vector ( \vec{P}_{exp} ) is derived from ALICE target telemetry or global phase equilibrium:
[
\vec{P}_{exp} = [p_s^{}, p_r^{}, p_c^{*}]
]
Phase deviation is computed as:
[
\Delta \theta = \arccos \left( \frac{\vec{P} \cdot \vec{P}{exp}}{|\vec{P}||\vec{P}|} \right)
]
where ( \Delta \theta ) defines the angular misalignment (in radians or normalized 0–1 scale).
| Metric | Formula | Meaning |
|---|---|---|
| Phase Resonance Score (PRS) | cos(θ_phase, θ_baseline) |
Phase coherence between current and baseline vector. |
| Phase Stability Index (PSI) | avg(PRS over last N cycles) |
Mean coherence of the active phase window. |
| Phase Stability Delta (PSD) | |PSIₜ − PSIₑₓₚ| |
Deviation between current and expected stability. |
| Phase Shift Delta (PSΔ) | θₜ − θₜ₋₁ |
Temporal drift of phase orientation. |
Normalization ensures all metrics lie within [0, 1], where higher values indicate greater coherence and alignment.
PhaseTelemetryFrame:
runtime_id: UUID
timestamp: ISO8601
phase_vector: [Float, Float, Float] # normalized vector (p_s, p_r, p_c)
phase_expected: [Float, Float, Float] # expected reference vector
phase_state: {stable|reflective|recenter}
psi: Float # Phase Stability Index
psd: Float # Phase Stability Delta
drift_index: Float
scr: Float
symbolic_density: Float
recursion_depth: Int
safety_status: {nominal|locked|recenter_pending}
Each telemetry frame represents a snapshot of phase-space alignment for monitoring or distributed synchronization.
| Method | Description |
|---|---|
GET /phase/state |
Returns current phase vector and PSI/PSD metrics. |
POST /phase/sync |
Injects Phase Sync Event to realign remote runtimes. |
POST /phase/lock |
Engages temporary phase lock (safety containment). |
POST /phase/recenter |
Triggers recenter protocol externally. |
GET /metrics/phase |
Retrieves PRS, PSI, PSD, and PSΔ values. |
Endpoints must preserve causal ordering and ensure integrity via signed telemetry tokens.
Distributed Sigma runtimes maintain coherence using vector-based synchronization:
PhaseTelemetryFrame every N cycles.This maintains bounded phase coherence across multi-node attractor networks.
The Phase Vector Model is fully compatible with AEGIDA-2’s Adaptive Phase Containment (APC):
To ensure stable distributed cognition:
cause_id).The criteria below describe the historical phase-vector and PRM model.
They are not current public certification criteria unless an active successor
document explicitly re-adopts them.
A runtime conforms to SRIP-08 if it:
Earlier drafts of this document referenced distributed-field,
multi-runtime-resonance, and higher-dimensional phase work before the current
SRIP-09, SRIP-10, and SRIP-11 registry assignments existed.
Those draft references are lineage context only. Current control, memory, and
runtime-stability evolution is tracked through the public registry and explicit
successor references, including SRIP-09, SRIP-10, SRIP-11, and SRIP-15
where applicable.
References
Tsaliev, E. (2025). SIGMA Runtime v0.4.6 — Phase Regulation and Distributed Coherence — DOI pending
Tsaliev, E. (2025). SIGMA Runtime Architecture v0.1 — DOI 10.5281/zenodo.17703667