SSMT – Profiles and Upgrade Path (2.7–2.9)

How to start light, add safety, and then scale to fleets — without over-engineering.

2.7 Keeping it simple (anti over-engineering guardrails)
Shunyaya Symbolic Mathematical Temperature (SSMT) is layered on purpose. You are not expected to ship everything on day one.

Start here:

• S1 (Lite)

  • Emit only:
    • e_T (unitless contrast around a declared baseline)
    • manifest_id
    • health flags
  • No a_T, no pooling, no hysteresis.
  • Who is this for: city analytics, buildings, weather dashboards, anomaly feeds, general monitoring.
  • Goal: kill °C vs °F drama and get one stable, comparable number.

• S2 (Freeze/survival aware)

  • Add:
    • a_phase (which side of a safety pivot like freezing or warp)
    • Q_phase (soft hysteresis memory so alerts don’t flicker at the edge)
  • Who is this for: cold chain, perishable or medical storage, human comfort/safety zones, structural stress bands.
  • Goal: “Are we entering the danger band?” without false alarms every time we wobble by 0 °C / 32 °F.

• S3 (Fleet / ML / gating)

  • Add:
    • a_T (bounded dial in (-1,+1) for pooling, dashboards, ML priors)
    • pooling rules (weight_rule, eps_w)
    • optional env-gate coupling for throttling/controls
  • Who is this for: aerospace, multi-zone industrial systems, chemistry with automated gating, large fleets with automated response.
  • Goal: stable cross-sensor dials you can average safely, audit later, and even plug into automated response.

Upgrade policy:

  • Move S1 → S2 only if phase safety really matters (freeze/gel/warp/human safety band).
  • Move S2 → S3 only if you can prove you need pooled fleet dials or automatic gating.
  • You must write the reason for each upgrade in the manifest notes. This is part of SSMT’s ethics and auditability.

Why this matters:
SSMT is designed to block “feature sprawl.” Every dial you emit becomes something you must defend in audit, regulation, and incident review. Start with the smallest surface that actually helps.

2.8 Versioning and compatibility
Once you emit SSMT, regulators, customers, and auditors will treat it like evidence. So you must treat it like evidence.

Rules to follow:

  1. New fields must be optional with sane defaults.
    • Example: you add uncertainty later. Older clients that ignore it should not break.
  2. Deprecations must be supported for at least 12 months.
    • You cannot silently stop sending a_phase next week if downstream alert logic still depends on it.
  3. Consumers must ignore unknown fields.
    • Parsers should not crash just because a new JSON key appears.
  4. version in the manifest is the declared spec version (for example "1.1").
    • This lets you prove: “We followed SSMT rules as documented in version 1.1 for this fleet / mission.”

Plain meaning:
When you attach a manifest_id to a live stream, you’ve created a contract. You can extend the contract in a backward-safe way. You cannot secretly rewrite it mid-flight.

2.9 Example manifests (copy-ready)
Below are three canonical starting shapes. They map directly to S1, S2, S3.

A) Weather / City Analytics (S1, log lens)
Simple anomaly / comfort tracking across locations with zero °C/°F fights.

SSMT_manifest_v1:
  version: "1.1"
  compliance_level: "S1"
  lens: "log"
  anchors:
    T_ref: 295.00
    DeltaT: null
    E_unit: null
    tau: null
    alpha: null
  guards:
    clamp_a_eps: 1e-6
    eps_TK: 1e-6
    T_valid_range_K: [230.0, 330.0]
  phase_block:
    T_m_list: []
    rho: 0.90
    k_side: 2.0
  outputs:
    emit_e_T: true
    emit_a_phase: false
    emit_a_T: false
  notes: "City anomaly; unitless e_T only"
  # optional:
  # privacy: { mode: "P1", step: 0.02 }  # quantize before public release

Highlights:

  • Only e_T leaves the device.
  • No phase dial, no pooling, almost no knobs.
  • Perfect to prove value fast.

B) Cold Chain / Medical Storage (S2, linear lens + phase dial)
“Are we drifting into unsafe?” with flicker-resistant memory.

SSMT_manifest_v1:
  version: "1.1"
  compliance_level: "S2"
  lens: "linear"
  anchors:
    T_ref: 277.15
    DeltaT: 2.0
    E_unit: null
    tau: null
    alpha: null
  guards:
    clamp_a_eps: 1e-6
    eps_TK: 1e-6
    T_valid_range_K: [260.0, 320.0]
  phase_block:
    T_m_list:
      - { tag: "product", T_m: 273.15, DeltaT_m: 2.0, c_m: 1.2 }
    rho: 0.90
    k_side: 2.0
  outputs:
    emit_e_T: true
    emit_a_phase: true
    emit_a_T: false
    emit_Q_phase: true
  notes: "Phase-aware excursion; no alignment channel"
  # optional:
  # gate:
  #   enabled: true
  #   lane: "Q_phase"
  #   L: 60
  #   kappa: 1.0
  #   mu: 3.0
  #   rho_g: 0.9
  #   theta_g: 0.2

Highlights:

  • Uses "linear" because cold chains operate in a tight band.
  • a_phase = “which side of safe band are we on?”
  • Q_phase = “don’t panic unless we’ve stayed unsafe for long enough.”
  • Optional gate lets you turn this into an automatic “hold / stop / escalate” signal.

C) Space Ops / Extreme Fleet (S3, hybrid lens + pooling)
Mixed subsystems, huge spans, and pooled fleet dials.

SSMT_manifest_v1:
  version: "1.1"
  compliance_level: "S3"
  lens: "hybrid"
  anchors:
    T_ref: 200.0
    DeltaT: 10.0
    E_unit: null
    c_T: 0.7
    tau: 5.0
    alpha: null
  guards:
    clamp_a_eps: 1e-6
    eps_w: 1.2e-12
    eps_TK: 1e-6
    T_valid_range_K: [3.0, 500.0]
  phase_block:
    T_m_list:
      - { tag: "propellant", T_m: 65.0, DeltaT_m: 3.0, c_m: 1.2 }
    rho: 0.95
    k_side: 3.0
  pooling:
    weight_rule: "health"
  health_flags:
    enable_range_ok: true
    enable_sensor_ok: true
    enable_drift: true
  validation:
    dataset_ref: "url-or-id"
    test_vectors_ref: "url-or-id"
    metrics: { E_HOT: 0.8, Phi_freeze: 0.10 }
  outputs:
    emit_e_T: true
    emit_a_phase: true
    emit_Q_phase: true
    emit_a_T: true
  notes: "Mixed regimes; bounded fleet dials and validation hooks"
  # optional:
  # privacy: { mode: "P2", b: 1.0, eps: 1.0 }
  # gate:
  #   enabled: true
  #   lane: "w1*abs(a_T)+w2*Q_phase"
  #   w: { w1: 0.5, w2: 0.5 }
  #   L: 60
  #   kappa: 1.0
  #   mu: 3.0
  #   rho_g: 0.9
  #   theta_g: 0.25

Highlights:

  • "hybrid" lens = linear near baseline, log for big excursions. Good for missions with both gentle habitat control and brutal thermal extremes.
  • Declares pooling, health flags, validation references. This is what you show to auditors later: “We didn’t guess. We tested against known data.”

These three profiles are the mental anchor:

  • S1: baseline comparability.
  • S2: safety dial + memory.
  • S3: pooled fleets + gating.

Navigation
Previous: SSMT – Field Definitions, Payload Keys, and Staying Backwards-Safe (2.4–2.6)
Next: SSMT – Device Passport, Auto Lens Policy, and Audit Stability (2.10–2.11)

Directory of Pages
SSMT – Table of Contents