Changelog
Public-facing changes to the Sgraal protocol, API, and SDKs.
April 2026 — v2.0
LATESTDecision Stability Layer
- Asymmetric hysteresis: USE_MEMORY is never sticky
- Only ASK_USER and BLOCK maintain decision continuity
- Boundary explainer: why WARN and not BLOCK, with confidence score
New Endpoints
POST /v1/compare/grok— side-by-side formal contradiction analysisPOST /v1/propagation/trace— cascade risk + containment statusPOST /v1/fidelity/certify— per-entry fidelity score
Open Standards
- MemCube v2 JSON Schema published
- SMRS v1.0 formal definition published
- Available at api.sgraal.com/v1/standard/memcube-spec
SDK Updates
pip install sgraalv0.2.0npm install @sgraal/mcpv0.2.0pip install mem0-sgraalv0.1.0 (new)
Benchmark
- Joint benchmark with Grok: 100% recall across 239 synthetic structural-corpus cases (every structurally-detectable attack flagged; R14 adversarial hardening in progress)
- Sponsored drift, subtle drift, hallucination corpora
F1 measured against Sgraal's own ground truth on synthetic corpora; Grok independently scored the same corpora — corroboration, not external validation. Production calibration pending.
March 2026 — v1.0
Initial Release
POST /v1/preflight— core memory validation- 85-module scoring pipeline
- 4 decisions: USE_MEMORY, WARN, ASK_USER, BLOCK
- ZK mode:
POST /v1/preflight/zk - Heal:
POST /v1/heal - Explain:
POST /v1/explain
Integrations
pip install sgraalv0.1.0pip install langchain-sgraalv0.1.0npm install @sgraal/mcpv0.1.0