Sigma Runtime Standard – License Notice
This document is part of the Sigma Runtime Standard (SRS).
It is licensed under Creative Commons Attribution–NonCommercial 4.0
(CC BY-NC 4.0).The license for this specific document is authoritative.
See/legal/IP-Policyfor the full repository-wide licensing framework.
Sigma Runtime Improvement Proposal
Category: Interoperability / Safety Hooks
Status: Draft
Editor: E. Tsaliev
Last Updated: 2025-12-26
SRIP-05 defines the interoperability layer for Sigma Runtime implementations.
It establishes schemas, protocols, and synchronization rules that allow multiple runtimes — operating independently or in distributed environments — to exchange state, drift signals, and attractor metadata without loss of coherence.
The specification ensures semantic and operational compatibility across conformant Sigma systems.
SigmaPacket:
header:
protocol_version: "1.0"
source_runtime_id: str
target_runtime_id: str
timestamp: str
payload:
attractor_state:
id: str
type: str
stability: float
phase: str
scr: float
drift_metrics:
sdi: float
sv: float
pd: float
di: float
memory_snapshot:
summary_hash: str
retention_index: float
safety_flags:
aegida_status: str
phase_lock: bool
recenter_active: bool
signature:
checksum: str
integrity_token: str
This schema defines the minimal transferable state unit between Sigma runtimes or monitoring systems.
| Endpoint | Function | Method |
|---|---|---|
/field/state |
Exchange field vectors, drift metrics, and SCR. | POST / GET |
/memory/snapshot |
Push or request serialized memory segments. | PUT / GET |
/phase/telemetry |
Stream ALICE phase data in real time. | WS / SSE |
/aegida/safety |
Query safety and fail-safe envelope parameters. | GET |
/runtime/handshake |
Negotiate protocol version and runtime UUID. | POST |
All endpoints use JSON-LD or YAML serialization with optional compression for long-horizon sessions.
protocol_version in every packet.runtime_capabilities.yml).state + drift only).attractor_state.drift_metrics.memory_snapshot schema.Together they form the Cross-Runtime Coherence Protocol (CRCP) — a shared substrate for distributed Sigma fields.
To prevent propagation of unstable attractors across runtimes, drift-based synchronization follows deterministic thresholds aligned with SRIP-03:
| Condition | Allowed External Sync | Action |
|---|---|---|
DI < 0.45 |
✅ Full sync allowed | Normal field exchange |
0.45 ≤ DI < 0.5 |
⚠ Caution zone | Sync allowed with reduced frequency |
DI ≥ 0.5 |
⛔ Sync Blocked (Drift Containment Active) | Runtime enters Reflective phase; external state export suspended |
DI ≥ 0.6 |
🔒 Recenter Phase | All external links temporarily isolated until stability restored |
This ensures a unified isolation threshold (DI ≥ 0.5) across SRIP-03 and 05, enforcing containment before cross-runtime drift can propagate.
A runtime conforms to SRIP-05 if it:
DI ≥ 0.5 → sync block).DI ≥ 0.5 and re-enabled once DI < 0.45.These measures maintain coherence and prevent propagation of unstable fields in distributed environments.
References
Tsaliev, E. (2025). SIGMA Runtime v0.4.6 — Interoperability and External Field Protocols — DOI pending
Tsaliev, E. (2025). SIGMA Runtime Architecture v0.1 — DOI 10.5281/zenodo.17703667