SSM-NET — Reproducibility of bands & Manifest changes over time (3E–3F)

Anyone can replay the same band decisions — policies evolve by rotation, not edits

3E. Reproducibility of bands
Band decisions must be independently repeatable by any conforming verifier. That means: same manifest bytes → same cutpoints → same band.

Verifier procedure (copy-ready).

# inputs: envelope e, fetched manifest M(e.manifest_id)
# goal: independently confirm the declared band

# 1) if align is public, rebuild the lane (else skip to step 2)
a_c := clamp(a_raw, -1+eps_a, +1-eps_a)
u   := atanh(a_c)
U  += w*u ; W += w
align_local := tanh( U / max(W, eps_w) )

# 2) compute band using the manifest's cutpoint_map and inclusivity text
band_local := cutpoint_map( (align if public else align_local), M )

# 3) compare with the envelope's declared band
assert band_local == e.band

# numeric discipline near cuts
# use manifest.cmp_tolerance for boundary comparisons

Determinism checklist (SHOULD).

- Use the exact manifest bytes bound to e.manifest_id (immutable rulebook).
- Apply declared boundary inclusivity (e.g., left-open/right-inclusive).
- Respect cmp_tolerance for near-cut decisions (avoid flip-flops).
- If align is not public, validate the band deterministically from disclosed inputs + manifest.

Why this matters (human terms).
Two teams, two toolchains, one band outcome. Reproducibility removes debates and “vendor math” from safety decisions.


3F. Manifest changes over time
Meaning evolves; history must not. SSM-NET enforces change by rotation (new manifest_id), never in-place edits.

Rotation workflow (copy-ready).

# authoring a new policy
draft_new_policy()
new_manifest := finalize_rulebook()
new_id := mint_manifest_id(new_manifest)       # stable identifier for the frozen text
publish("/.well-known/ssmnet/manifest/"+new_id, new_manifest)

# start using the new policy
for future_envelopes:
    envelope.manifest_id := new_id             # reference the new, immutable rulebook

# keep old manifests online
# never edit bytes at the old manifest_id

Operational rules (MUST / SHOULD).

- MUST NOT edit a published manifest body for an existing manifest_id.
- MUST mint a new manifest_id if any band, threshold, inclusivity, or obligation changes.
- SHOULD announce non-normative release notes (effective-from timestamps).
- SHOULD maintain a public index of available manifest_id entries and their digests.

Audit implications.
Past envelopes are judged under the exact rulebook they cited. Reviews remain fair and replayable, even years later.


Navigation
Previous: SSM-NET — Publication & discovery (3D)
Next: SSM-NET — Sender & Receiver (4A–4B)