Its own standard: cooperate widely, never get diluted
What independence means
SSMDE is not a nicer wrapper for someone else’s transport or schema. It defines a truth-carrying contract that must remain recognizable wherever it travels.
# identity of an SSMDE record (core surface)
{ value, align, band?, manifest_id, stamp? }
If these meanings change, it isn’t SSMDE.
Non-negotiable semantics
value := exact observed/computed magnitude # collapse parity: phi((m,a)) = m
align := bounded dial (-1,+1) from clamp → atanh → fuse → tanh
band := human/policy label derived from manifest cutpoints
manifest_id := immutable rulebook identifier (resolves to replayable policy)
stamp := time + integrity + order chain (e.g., ...|sha256=...|prev=...)
Cooperate without impersonating
You can carry SSMDE inside buses, files, APIs, DB rows. You cannot remap or rename away the contract.
Allowed
• Embed SSMDE block inside your envelope unchanged
• Store fields as first-class columns
• Add optional fields (privacy, compliance) alongside the block
Not allowed
• Mutate value then still call it value
• Emit an unbounded “score” and call it align
• Hand-paint bands that don’t match manifest cutpoints
• Point manifest_id to mutable or opaque policy
• Replace stamp with a plain timestamp
Adapter pattern (keep meanings intact)
# legacy envelope → SSMDE slot
envelope := {
"topic": "plant/lineA",
"ts": utc_now(),
"ssmde": {
"value": legacy_payload, # untouched
"align": tanh( U / max(W, eps_w) ), # after clamp → atanh → fuse
"band": band_from_align(align, mid),
"manifest_id": mid,
"stamp": "SSMCLOCK1|...|sha256=...|prev=..."
}
}
Independence tests (quick self-check)
[ ] Can a 3rd party replay band from align using my manifest_id?
[ ] Does phi((m,a)) = m hold byte-for-byte for value?
[ ] Is align strictly within (-1,+1) for all emitted records?
[ ] Would stamp verification fail if I edited, dropped, or reordered a record?
[ ] If I changed a cutpoint today, did I mint a new manifest_id?
Why this matters
Independence protects:
- Adopters: free to integrate anywhere without refactoring their whole stack.
- The standard: no vendor can dilute the field meanings and still call it SSMDE.
- Auditors & safety teams: same semantics everywhere → comparable, defensible truth.
Navigation
Previous: SSMDE – Scope and claim (2.1)
Next: SSMDE – Interoperability (2.3)
Directory of Pages
SSMDE – Table of Contents
SHUNYAYA 