The declared rulebook for meaning, thresholds, and escalation
A number becomes actionable truth only when the rulebook behind it is known.
In SSMDE, that rulebook is the manifest. It states exactly how align is computed, how band is assigned, and what escalation promises apply — and it is versioned and frozen so meanings cannot drift silently.
What a manifest contains
A manifest is a compact, versioned declaration (human-readable text).
• Baseline / lens (what “normal” means)
• Alignment math knobs (eps_a, eps_w, weight rule, optional gates)
• Band boundaries (e.g., align >= +0.80 → "A++")
• Escalation promises (response actions and time windows)
• manifest_id (unique version anchor)
Collapse parity remains guaranteed even when a manifest is applied:
phi((m,a)) = m
Alignment math (declared, not implied)
The manifest must make the align pipeline explicit so anyone can replay it:
a_c := clamp(a_raw, -1+eps_a, +1-eps_a)
u := atanh(a_c)
U += w * u
W += w
align := tanh( U / max(W, eps_w) )
Example knob defaults to publish:
eps_a := 1e-6
eps_w := 1e-12
w := "uniform" # or a declared rule, e.g., w := |m|^gamma
Bands and promises (policy in plain words)
Bands translate math to duty-of-care. Cutpoints are declared and tied to response windows.
# example cutpoints
A++ : align >= +0.80
A0 : -0.30 <= align < +0.80
A- : -0.80 <= align < -0.30
CRITICAL : align < -0.80
Escalation promises (examples):
CRITICAL => human_response <= 10 minutes
A- => investigate <= 30 minutes
A0 => monitor <= 8 hours
Manifest identity and versioning
Each file carries a unique anchor:
manifest_id := "PLANT_A_BEARING_SAFETY_v7"
If policy changes (cutpoints, weights, windows), issue a new:
manifest_id := "PLANT_A_BEARING_SAFETY_v8"
No silent edits. No retroactive reinterpretation.
Minimal manifest (copy-ready)
{
"manifest_id": "PLANT_A_BEARING_SAFETY_v7",
"align_computation": {
"eps_a": 1e-6,
"eps_w": 1e-12,
"weights": "uniform",
"pipeline": [
"a_c := clamp(a_raw, -1+eps_a, +1-eps_a)",
"u := atanh(a_c)",
"U += w * u ; W += w",
"align := tanh( U / max(W, eps_w) )"
]
},
"bands": [
{ "name": "A++", "align_min": 0.80, "action": "none", "window": "n/a" },
{ "name": "A0", "align_min": -0.30, "action": "monitor", "window": "<= 8 h" },
{ "name": "A-", "align_min": -0.80, "action": "investigate", "window": "<= 30 min" },
{ "name": "CRITICAL","align_min": -1.00, "action": "page human", "window": "<= 10 min" }
]
}
Why manifesting stops disputes
| Without a manifest | With a manifest |
|---|---|
| “GREEN meant something else that week.” | “A0 at this timestamp meant -0.30 <= align < +0.80; here’s the file.” |
| “We tightened thresholds after the incident.” | “Then it must be a new manifest_id; reuse is not allowed.” |
| “Who approved this policy?” | “The manifest is the approval and evidence.” |
Enforcement rule
Every SSMDE record MUST include manifest_id.
This lets any independent party replay the judgment years later, even offline.
Navigation
Previous: SSMDE – Alignment Dial (how stable / how close to danger right now) (1.2)
Next: SSMDE – Stamp (1.4)
Directory of Pages
SSMDE – Table of Contents
SHUNYAYA 