The smallest portable unit of fact, stability, policy, and proof
Canonical shape (copy-ready)
{
"value": <number-or-struct>,
"align": <number in (-1,+1)>,
"band": <string>, # optional but recommended
"manifest_id": <string>,
"stamp": <string> # optional but recommended
}
Intent of each field
value→ the untouched magnitude or small struct (collapse parity:phi((m,a)) = m).align→ bounded stability dial (-1 < align < +1) computed byclamp → atanh → fuse → tanh.band→ human / policy label derived fromalignusing manifest cutpoints.manifest_id→ the rulebook anchor; must resolve to an immutable manifest.stamp→ one-line timing + integrity + chain proof (e.g.,SSMCLOCK1|...|sha256=...|prev=...).
Minimal vs Full (pick what you need)
Minimal (Day-1 adoption)
{
"value": <number-or-struct>,
"align": <number-in-(-1,+1)>,
"manifest_id": <string>
}
Full (recommended for audit)
{
"value": <number-or-struct>,
"align": <number-in-(-1,+1)>,
"band": <string>,
"manifest_id": <string>,
"stamp": "SSMCLOCK1|<utc>|theta=<x>|sha256=<hex>|prev=<hex-or-NONE>"
}
Type & range guidance (copy-ready)
value : number | object
align : float ; must satisfy -1 < align < +1
band : string ; e.g., "A++", "A0", "A-", "CRITICAL"
manifest_id : string ; immutable policy anchor (e.g., "PLANT_A_BEARING_SAFETY_v7")
stamp : string ; tamper-evident time/order chain (recommended)
Canonical subset (for hashing in stamp)
Keep hashing stable and tiny.
canonical(record):
{
"value": <as-emitted>,
"align": <number>,
"band": <string-or-null>,
"manifest_id": <string>
}
Serialization rules (to avoid drift)
• UTF-8, plain ASCII tokens
• stable key order: value, align, band, manifest_id
• floats as plain ASCII (no locale commas)
• explicit nulls if a field is absent downstream
Validation checklist (producer & consumer)
[ ] phi((m,a)) = m holds for value (collapse parity)
[ ] -1 < align < +1 and computed via clamp → atanh → fuse → tanh
[ ] band matches manifest cutpoints (if present)
[ ] manifest_id resolves to immutable manifest
[ ] stamp (if present) verifies: sha256(canonical(record)) and prev-chain continuity
Two copy-ready examples
Industrial cooling
{
"value": { "temperature_K": 296.42 },
"align": 0.87,
"band": "GREEN",
"manifest_id": "THERMAL_LINE_COOLING_PLANT_A_v7",
"stamp": "SSMCLOCK1|2025-11-04T14:05:22Z|theta=132.77|sha256=9fde1c...|prev=72af0b..."
}
Finance collections
{
"value": { "cash_collected_usd": 18420.77 },
"align": -0.31,
"band": "A-",
"manifest_id": "AR_STABILITY_Q4_CLOSE_v2",
"stamp": "SSMCLOCK1|2025-11-04T14:06:41Z|theta=044.91|sha256=ab12d4...|prev=89c2aa..."
}
Navigation
Previous: SSMDE – Putting it together (1.5)
Next: SSMDE – Field-by-field walkthrough (1.7)
Directory of Pages
SSMDE – Table of Contents