SMN: Semantic Mass Numbers

Status: CANONICAL_NAMING_BOUNDARY

Claim boundary: SMN is a project-local semantic-load measure. It is not atomic mass, not isotope mass number, not physical mass, and not a Mass Number admissibility receipt by itself.

Definition

SMN(x) = semantic load carried by x inside the stack.

An SMN measures how much structured meaning, provenance, relation burden, constraint burden, and decision burden a symbol, channel, ratio, or gate carries.

Keeper rule:

SMN measures how heavy a symbol is inside the model.

Non-Identities

SMN != atomic mass number
SMN != isotope mass
SMN != SI mass
SMN != Mass Number admissibility packet
SMN != proof
SMN != truth

The older phrase "semantic mass number" should now be normalized to:

SMN: Semantic Mass Number

Relationship To Existing Terms

Term	Meaning	Claim boundary
Semantic Mass	Dimensionless semantic/routing pressure or burden	raw load signal
SMN	Counted semantic-load index for a concrete object	measurable/codable load number
Mass Number	Admissibility packet with residual and boundary guard	receipt/gate surface

So the pipeline is:

semantic mass pressure
  -> SMN score
  -> optional Mass Number packet
  -> admissibility / residual / boundary receipt

Do not skip directly from SMN score to truth. SMN can route attention, but a Mass Number receipt is still required for promotion.

Minimal Formula

SMN(x) =
  identity_load(x)
+ relation_load(x)
+ provenance_load(x)
+ constraint_load(x)
+ decision_load(x)
+ repair_load(x)

For compact receipts:

SMN(x) = |bindings| + |relations| + |gates| + |receipts| + |residuals|

Stellar Gas Example

Anonymous vector slot:

EMLINE_GFLUX_1RE[16]

has low SMN because it is only a position.

Named channel:

OIII-5008

has higher SMN because it binds:

oxygen species
+ ionization state
+ wavelength
+ high-ionization role
+ MaNGA provenance

Diagnostic ratio:

log(OIII-5008 / Hb-4862)

has still higher SMN because it adds a relation and a diagnostic gate.

BPT-style proxy class:

OIII/Hb + NII/Ha -> star-forming / composite / AGN-LIER-shock proxy

has higher SMN again because it participates in a decision surface.

Receipt Shape

{
  "schema": "smn_semantic_mass_number_v0",
  "object_id": "OIII-5008",
  "object_kind": "emission_line_channel",
  "smn": 7,
  "components": {
    "identity_load": 2,
    "relation_load": 1,
    "provenance_load": 1,
    "constraint_load": 1,
    "decision_load": 2,
    "repair_load": 0
  },
  "boundary": "SMN is semantic load, not atomic mass and not proof."
}

Working Rule

Use SMN to choose what deserves attention, not to claim correctness.

high SMN + weak receipt coverage = audit priority
high SMN + strong receipt coverage = reusable route candidate
low SMN + strong evidence = useful primitive
low SMN + weak evidence = background noise

3 KiB Raw Permalink Blame History