Acceptance checklist and a crisp adoption summary.
J10) Acceptance checklist (must pass before ship)
Core invariants
- Parity preserved. For all items,
phi((m,a)) = m(classical values untouched). - Boundedness. All lanes:
|a| < 1; chooser/gate:|RSI|, |RSI_env| < 1. - Order/shard invariance.
U += w*atanh(a),W += w⇒ batch == stream == shuffled == shard-merge. - Determinism. Same manifest + same inputs ⇒ identical
RSI,RSI_env, bands, stamps.
Division & gating
- Division policy. Under
"strict", near-zero denominators flagged; routing falls back to classical, stamped. - Gate purity. Changes only alignment (RSI → RSI_env);
mremains identical.
Governance & safety
- Privacy checks. Features are declared aggregates, not PII; masking enforced for notes.
- Reproducibility.
knobs_hashlogged; stamped CSV replay reproduces results within dtype tolerance. - Drift visibility. (U,W) roll-ups plotted for operational monitoring.
Pass these → ready for deterministic, alignment-safe deployment.
One-line takeaway
A tiny SDK, golden tests, and manifest-as-contract ensure bounded, deterministic alignment beside classical numbers — without ever touching your metrics (phi((m,a)) = m remains inviolable).
Navigation
Previous: SSM-AI – Appendix J — SDK Packaging & Golden Tests (J7–J9)
Next: SSM-AI – Appendix K — SSM-Search (K1–K3)
Directory of Pages
SSM-AI — Table of Contents