5.8 — Change management (knobs and versions)
• Immutable manifests. Any change to eps_a, eps_w, band table, gamma, LUT IDs, or division_policy increments a version and invalidates bit-identical claims.
• Compare like with like. Only compare runs with identical manifests; otherwise label as a new experiment.
• CI checks. Conformance vectors must pass on each build; reject if any tolerance is exceeded.
CI gate (plain text)
test:
python conformance_esuite.py –json > out.json
python – <<‘PY’
import json,sys
d=json.load(open(‘out.json’))
assert all(v==’PASS’ for v in d[‘results’].values())
print(“OK”)
PY
checksum:
python conformance_esuite.py –checksum > checksum.txt
5.9 — Fallback and rollback (plan before you need it)
• One toggle. A single flag disables advisory hooks; logging of (m,a) continues.
• Shadow mode. New bands run in parallel and are logged but do not influence schedulers until promoted.
• Golden floor. Never hide values; bands augment visibility and can be safely ignored in emergencies.
Env toggles (plain text)
ADVISORY_ENABLE=false
SHADOW_MODE=true
5.10 — Integration patterns (minimal friction)
• Side-car field. Add a alongside existing m in structs/messages/tables.
• Adapters. When a downstream block is not lane-aware, pass m and drop or park a; never route a into m logic by accident.
• Backfills. When recomputing history, guarantee batch == stream == shuffled on the lane.
Struct sketch (plain text)
struct KpiPoint { double m; double a; int64 ts; char band[3]; }
Navigation
Back: Shunyaya Symbolic Mathematical Hardware – Readiness & Safety Gates (5.6–5.7)
Next: Shunyaya Symbolic Mathematical Hardware – Ops Levers, Timeline & Release Packet (5.11–5.13)
Directory of Pages
SSMH – Table of Contents
SHUNYAYA 