SSM-NET — Well-known endpoints: Introduction & Purpose (7.0, 7A)

Predictable, read-only discovery anyone can replay

7.0 Introduction. This section presents the well-known discovery endpoints that make SSM-NET independently verifiable. Any party can fetch manifests (rulebooks), read the current continuity HEAD, and pull compact evidence bundles—all read-only, cache-friendly, and profile-agnostic. These surfaces enable verification without private coordination while preserving payload invariance (collapse parity phi((m,a)) = m).

Hash & continuity recap (context).

# declared canonical subset (illustrative)
subset := ["value","band","manifest_id"(,"align_ascii"?)]

# integrity over declared subset (+ raw body bytes if declared)
HEAD := sha256( serialize(subset) [+ raw_body_bytes] )

# single-link continuity (append-only)
stamp := "SSMCLOCK1|<UTC_ISO>|nonce=<...>|sha256=" + HEAD + "|prev=<HEX or NONE>"

Normalization note. Any textual material used in hashing SHOULD be UTF-8 and MUST be normalized to UTF-8 NFC before digest computation to avoid cross-platform drift.


7A. Purpose. Provide public, predictable URLs for rulebooks, continuity, and evidence so anyone can fetch, verify, and replay integrity and duty-of-care without changing payload bytes or relying on private trust channels.

Operator quick checklist (non-normative).

- Expose: /.well-known/ssmnet/manifest/<id>, /checkpoint, /evidence
- Keep read-only; never mutate history at these paths
- Normalize to UTF-8 NFC before hashing
- Prefer label-first (value+band); reveal align only if declared public
- Cache: long TTL for manifest, short TTL for checkpoint


Navigation
Previous: SSM-NET — Mirrors, Streams, Evidence (6C–6E)
Next: SSM-NET — Well-known endpoints: Endpoints (7B)