INV-032 — No New State Variables Without Necessity

1. Definition

Do not add new state variables when the existing UTS state vector can represent the relevant system condition.

The canonical UTS state vector is:

S = { O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ }

A new concept should not become a state variable merely because it is important, recurring, measurable, symbolically meaningful, or domain-specific.

Therefore:

No new state variables without necessity.

A candidate variable must first be tested as:

diagnostic
derived metric
composite index
domain expression
gate threshold
law variable
scaling modifier
regime condition
lens output
failure-mode indicator
restoration marker
operator parameter

Only if it identifies a distinct, irreducible system state not representable through the existing state vector should it be considered as a new state variable.

2. Purpose

This invariant protects the UTS core model from variable inflation.

It prevents the error:

This condition matters,
therefore it needs a new state-vector variable.

The correct UTS interpretation is:

This condition matters.
Now test whether it maps to O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ,
or whether it should be modeled as a diagnostic, derived index,
threshold, gate, regime condition, or domain expression.

The state vector is the shared grammar of UTS.

If every module adds new variables, the framework loses:

• cross-domain portability
• model stability
• machine readability
• diagnostic comparability
• operator compatibility
• teaching clarity
• registry coherence
• canon stability
• ability to translate across domains

This invariant allows expansion without breaking the core model.

3. Constraint Statement

Canonical Form

No new state variables without necessity.

Expanded Form

A new state variable may be introduced only if the concept represents a
distinct, irreducible system state that cannot be expressed through the
canonical state vector, derived diagnostics, gates, lenses, regimes,
scaling modifiers, laws, failure modes, restoration arcs, or domain-specific
expressions.

Minimal Expression

Do not multiply state variables unnecessarily.

State-Vector Form

Map to S before expanding S.

Canon Form

S = { O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ } remains the default state grammar.

Diagnostic Form

Most measurable conditions are diagnostics, not state variables.

Scaling Form

Scale effects modify state behavior; they do not automatically require new state variables.

AI Form

AI governance conditions should map to S before creating AI-specific state variables.

Principles / Archetypes Form

Symbolic, archetypal, and principle effects must map to S before becoming new variables.

4. Structural Logic

A state variable represents a primary dimension of system condition.

The UTS state vector is intentionally compact.

Each variable is high-level enough to translate across many domains:

Most new concepts are not new state dimensions.

They are usually:

• specific expressions of one variable
• interactions between variables
• derived diagnostics
• threshold conditions
• regime markers
• gate criteria
• domain-local forms
• scaling behaviors
• failure signatures
• restoration targets

The incoherent sequence is:

new condition appears
        ↓
condition is important
        ↓
new state variable is created
        ↓
state vector expands
        ↓
cross-module comparison weakens
        ↓
diagnostic overlap increases
        ↓
machine readability declines
        ↓
ontology debt accumulates

The coherent sequence is:

new condition appears
        ↓
map to S
        ↓
test as derived diagnostic / threshold / regime / gate / lens
        ↓
test as domain expression
        ↓
only if irreducible, consider candidate state variable
        ↓
stress-test across modules and time

This keeps UTS extensible without losing the core grammar.

5. State-Vector Impact

Protected State Variables

This invariant protects the entire state vector:

O   — coherence
H   — hidden debt
ε   — visible error / noise
ι   — inversion
Au  — auditability
µᵢ  — meaning / agent integrity
BΣ  — boundary integrity
K   — compatibility
R   — restoration capacity
Φ   — fitness proxy

Primary Risk Variables When Violated

Au  — auditability declines as variable count rises
K   — compatibility declines across modules
H   — ontology debt accumulates
ι   — expansion appears precise while reducing coherence
ε   — confusion / contradiction / duplication increases

Healthy State-Vector Discipline Pattern

new condition appears
mapped to S
derived diagnostic created if needed
domain expression preserved
S remains stable
Au stable or ↑
K stable or ↑
O preserved

Violation Pattern

new condition appears
new variable added prematurely
overlap increases
S becomes unstable
Au↓
K↓
H↑
ε↑
O↓

Variable Inflation Pattern

conceptual richness↑
state-vector count↑
translation burden↑
machine schema fragility↑
canon drift↑

The danger is not conceptual detail.

The danger is unnecessary expansion of primary state grammar.

6. U-Layer Localization

Primary Layer

U4 — Classification / Metrics

This invariant governs how new measurable or meaningful conditions are classified.

Core Model Boundary Layer

U2 — Configuration / Boundaries

The state vector is a canonical boundary. Expanding it changes the model’s foundation.

Coherence Field Layer

U6 — Coherence Field

Variable inflation can weaken whole-framework coherence.

Memory Layer

U7 — Memory / Recurrence

Once a variable is introduced into canonical memory, it becomes hard to remove.

Time Layer

U5 — Coordination / Time

Candidate variables should be time-tested across use cases before canonization.

Execution Layer

U3 — Execution

State variables affect diagnostics, gates, tools, dashboards, machine schemas, and workflows.

Resource Layer

U1 — Power / Budgets

More variables increase maintenance, documentation, implementation, and teaching burden.

Common Failure Pattern

new diagnostic need appears
        ↓
U4 misclassifies it as state variable
        ↓
S expands
        ↓
existing diagnostics overlap
        ↓
cross-module K declines
        ↓
Au declines
        ↓
ontology H rises

Common Misdiagnosis

Violation of this invariant is often misdiagnosed as:

• precision
• rigor
• sophistication
• completeness
• scientific detail
• module maturity
• technical progress
• symbolic richness
• better measurement
• domain specificity
• improved modeling

The deeper issue may be:

The condition was important, but it was not a new primary state variable.

7. Violation Signatures

7.1 Diagnostic Becomes State Variable

A measurement or derived indicator is promoted into the core state vector.

diagnostic appears
        ↓
state variable created
        ↓
S expands unnecessarily

Example:

Bandwidth, damping, slack, crisis loop index, appeal access ratio,
or goodhart risk are diagnostics unless proven irreducible.

7.2 Domain Expression Becomes Universal Variable

A domain-local condition is promoted into a universal variable.

domain-specific condition
        ↓
universal state variable
        ↓
translation debt↑

Example:

A medical, economic, AI, governance, or symbolic term should first map to S.

7.3 Composite Index Becomes Primitive Variable

A composite diagnostic is treated as a primary state dimension.

multiple variables combine
        ↓
composite index named
        ↓
index mistaken for primitive

Example:

Legitimacy may derive from O, Au, BΣ, R, µᵢ, K, and recurrence,
rather than becoming a new universal variable by default.

7.4 Scaling Effect Becomes Variable

A condition that changes with scale is made into a state variable instead of a scaling rule or modifier.

scale behavior observed
        ↓
new variable created
        ↓
scaling registry bypassed

7.5 Gate Threshold Becomes Variable

A decision threshold is treated as a state variable.

admissibility threshold appears
        ↓
state variable created
        ↓
gate / state boundary blurred

7.6 Failure Mode Indicator Becomes Variable

A failure signature is elevated into the state vector.

failure mode detected
        ↓
variable created
        ↓
diagnostic / failure / state confusion

7.7 Symbolic Term Becomes Variable Too Quickly

A symbolically powerful concept is treated as a state dimension before mapping.

symbolic density↑
S expansion↑
auditability↓

7.8 Existing State Vector Mapping Ignored

A new variable is created even though it maps cleanly to existing variables.

existing mapping available
        ↓
new variable added
        ↓
redundancy↑

8. Related Failure Modes

Primary related failure modes:

• State Vector Inflation
• Variable Redundancy
• Ontology Bloat
• Canon Drift
• Diagnostic / State Confusion
• Gate / State Confusion
• Scaling / State Confusion
• Domain Overgeneralization
• Composite Index Reification
• Symbolic Over-Variable Drift
• Machine Schema Fragility
• Cross-Module Compatibility Loss
• Auditability Collapse
• Teaching Complexity Inflation
• Metric Saturation
• Terminology Saturation
• Registry Boundary Failure
• Model Drift

9. Related Restoration Arcs

Primary restoration arcs:

• State Vector Discipline Restoration
• Variable De-Duplication
• Diagnostic Reclassification
• Gate Reclassification
• Scaling Rule Reclassification
• Domain Expression Mapping
• Ontology Compression
• Canon Boundary Repair
• Cross-Module Alignment
• Machine Schema Cleanup
• Glossary Clarification
• Composite Index Decomposition
• Temporal Revalidation
• Registry Reclassification
• Construct Consolidation

Restoration Requirement

A candidate variable must be mapped through the state-vector discipline sequence before canonization.

Minimal sequence:

Identify candidate state variable
        ↓
Define exact system state it claims to represent
        ↓
Map to existing S variables
        ↓
Test as derived diagnostic / composite index / gate threshold / scaling modifier
        ↓
Test as domain expression
        ↓
If reducible, classify accordingly
        ↓
If irreducible, mark as candidate only
        ↓
Stress-test across modules and time
        ↓
Canonize only if non-redundancy is proven

10. Domain Expressions

AI

AI governance frequently generates candidate variables such as:

• alignment
• agency
• autonomy
• trust
• user sovereignty
• epistemic integrity
• refusal quality
• appealability
• memory safety
• representation validity
• model confidence
• dependency risk
• public cognition integrity

Most should first map to S.

Example mappings:

alignment → O + K + BΣ + Au + R + Τ behavior
trust → Au + R + BΣ + recurrence + O
agency → BΣ + µᵢ + exit + R + Au
memory safety → BΣ + Au + µᵢ + R
dependency risk → H + BΣ↓ + exit↓ + K↓

These are often diagnostics, gates, or derived constructs rather than new state variables.

AI Governance

AI governance may require many domain-specific indicators, but not necessarily new state variables.

For example:

appeal access ratio → diagnostic
guardrail transparency → Au expression
false positive repair rate → R / Au / ε diagnostic
user sovereignty → BΣ + µᵢ + exit + Au
epistemic integrity → µᵢ + Au + O + H

These can be powerful without expanding S.

Governance / JGL

Governance concepts should first map into the state vector:

legitimacy → O + Au + R + BΣ + µᵢ + recurrence validation
justice → R + Au + BΣ + O + consequence symmetry
authority → Φ / U3 capacity constrained by Au, R, BΣ
accountability → Au + R + Τ + H reduction
appeal access → Au + R + BΣ diagnostic

Legitimacy is critical, but likely a composite construct rather than a primary state variable.

Security

Security conditions map well into S:

security → O under pressure with BΣ, Au, R, µᵢ preserved
threat exposure → ε / H / BΣ risk
silent extraction → O↓ + σ↓ + ε≈0 pattern
incident count → ε diagnostic
containment health → BΣ + R + Au

Security should add diagnostics and gates, not new state variables by default.

Economy

Economic concepts map into S:

profit → Φ
externality → H
circulation coherence → O + R + BΣ
contract validity → BΣ + Au + K + R
market signal → ε / Φ / U4 artifact
economic legitimacy → Au + O + µᵢ + R

Economy can have domain diagnostics without expanding S.

Biology / Medicine

Biological conditions map into S:

health → O
symptom burden → ε + H expression
chronic compensation → H + R↓ + 𝓓↓
tolerance → K + BΣ + R diagnostic
recovery → R + H↓ + recurrence↓ + O↑
membrane integrity → BΣ

Biology may require domain-specific measures, but the UTS state vector can still hold the conceptual grammar.

CMS / Meaning

Meaning concepts map into S:

discernment → Au + Μ quality + Θ
meaning integrity → µᵢ
shadow debt → H + ι
symbolic coherence → O + µᵢ + Au
spiritual authority risk → Φ + ι + Au↓
embodiment → Τ-validated O + µᵢ + BΣ + R

Meaning depth does not require new state variables by default.

Principles / Archetypes

Principles and archetypes map into S through:

principle coherence → O + BΣ + µᵢ + R + Τ
archetype integrity → µᵢ + BΣ + R + H↓
shadow capture → H + ι + BΣ↓
role fusion → BΣ↓ + µᵢ↓ + exit↓
embodiment → O + µᵢ + recurrence validation

Archetypal richness belongs in maps, lenses, cards, diagnostics, or restoration arcs, not necessarily state variables.

11. Scaling Behavior

As the project scales, state-vector discipline becomes increasingly important.

Why

At larger project scale:

• more domains introduce local measures
• more diagnostics are created
• more modules generate candidate variables
• AI-readable schemas require stability
• cross-module comparison becomes harder
• derived metrics multiply
• dashboards become tempting
• terminology saturation increases
• state variables become harder to teach
• machine systems become schema-fragile
• canon drift becomes harder to detect

Scaling Pattern

Project scale↑
        ↓
candidate variables↑
        ↓
state-vector inflation risk↑
        ↓
cross-module comparability↓
        ↓
machine schema fragility↑
        ↓
canon drift↑

Scaling Rule Connection

Scale↑ ⇒ state vector stability requirement↑
Scale↑ ⇒ diagnostic registry should absorb complexity
Scale↑ ⇒ domain expressions should increase before S expands
Scale↑ ⇒ machine schema discipline becomes critical
Scale↑ ⇒ variable admission gates must strengthen

Therefore, high-scale UTS development requires stronger:

Au
K
BΣ
Θ
Μ
Σ
Π
diagnostic registry discipline
machine schema integrity
canon review
variable de-duplication

12. Canonical Examples

Example 1 — Legitimacy as Candidate Variable

Legitimacy is central to JGL.

But it may not need to become a primary state variable because it can be modeled as a composite:

Legitimacy ≈ O + Au + BΣ + R + µᵢ + time validation

So it remains a construct / diagnostic / module concept unless irreducibility is proven.

Example 2 — Trust as Candidate Variable

Trust matters deeply.

But structurally it may derive from:

Au + R + BΣ + recurrence + O

Trust can be a diagnostic or relational construct rather than a universal state variable.

Example 3 — Sovereignty as Candidate Variable

Sovereignty is important.

But in UTS it often maps to:

BΣ + µᵢ + exit capacity + Au + R

So it may remain a construct or diagnostic.

Example 4 — Attention Capacity

Attention capacity is important, but likely a diagnostic related to:

𝓑(t), σ(t), Au, R, Φ pressure, and O

It does not need to become a state-vector primitive unless it proves irreducible.

Example 5 — Appeal Access Ratio

Appeal access ratio is valuable, but it is a diagnostic related to:

Au + R + BΣ + legitimacy pathway

It belongs in diagnostics, not state vector.

Example 6 — Coercive Fusion Risk

Coercive fusion risk is meaningful, but it likely derives from:

BΣ↓ + exit↓ + H↑ + ι↑ + K↓

So it belongs as diagnostic / failure-mode indicator.

13. Anti-Patterns

Anti-Pattern 1 — “Important Means State Variable”

Important concepts can be diagnostics, gates, constructs, or domain expressions.

Anti-Pattern 2 — “Measurable Means State Variable”

Most measurements are diagnostics.

Anti-Pattern 3 — “Domain-Specific Means New Variable”

Domain-specific conditions should map to S first.

Anti-Pattern 4 — “Composite Index Means Primitive”

Composite indexes should usually remain derived.

Anti-Pattern 5 — “Scaling Effect Means State Variable”

Scaling effects belong in scaling rules unless they reveal irreducible state.

Anti-Pattern 6 — “Symbolic Power Means State Dimension”

Symbolic density does not prove state-vector irreducibility.

Anti-Pattern 7 — “More Variables Means More Precision”

Too many primary variables reduce precision by increasing overlap and ambiguity.

14. Related Laws

This invariant connects strongly to:

• State Vector Compression Law
• No New Primitive Law
• Ontology Compression Law
• Canon Drift Law
• Classification Integrity Law
• Diagnostic-State Separation Law
• Metric Saturation Law
• Complexity-Auditability Gap Law
• Translation Fidelity Law
• Machine Schema Stability Law
• Variable Inflation Law
• Temporal Validation Law

15. Related Scaling Rules

Related scaling rules:

• State Vector Inflation Risk Under Scale
• Diagnostic Registry Absorption Requirement
• Machine Schema Fragility Under Variable Growth
• Cross-Module Comparability Burden Growth
• Terminology Saturation Under Scale
• Domain Expression Growth Before State Expansion
• Variable Admission Gate Strengthening
• Canon Review Requirement Under Scale
• Metric Saturation Risk Under Scale
• Translation Fidelity Loss Under Scale
• Teaching Burden Growth

16. Related Gates

Relevant gates:

• State Variable Admission Gate
• Canon Admission Gate
• Registry Classification Gate
• No-New-Primitive Gate
• Diagnostic / State Separation Gate
• Gate / State Separation Gate
• Scaling / State Separation Gate
• Composite Index Gate
• Domain Translation Gate
• Machine Schema Integrity Gate
• Temporal Validation Gate
• Cross-Module Compatibility Gate

Gate Logic

A candidate state variable fails the admission check when:

it maps cleanly to existing S variables

or when:

it is a diagnostic, derived metric, threshold, gate, lens, regime,
law, scaling modifier, failure indicator, restoration marker,
operator parameter, construct, or domain expression

or when:

it is domain-specific but not cross-domain irreducible

or when:

it increases measurement detail while reducing auditability or compatibility

or when:

it has not survived temporal and cross-module validation

17. Related Operators

18. Machine-Readable Summary

id: UTS-INV-032
name: No New State Variables Without Necessity
registry: UTS Invariants Registry
category: State Vector Integrity Invariant / Ontology Integrity Invariant / Canon Safety Invariant
status: Draft-Integrated
version: 0.1

definition: >
  Do not add new state variables when the existing UTS state vector can
  represent the relevant system condition. A new concept should not become a
  state variable merely because it is important, recurring, measurable,
  symbolically meaningful, or domain-specific.

constraint: >
  A new state variable may be introduced only if the concept represents a
  distinct, irreducible system state that cannot be expressed through the
  canonical state vector, derived diagnostics, gates, lenses, regimes,
  scaling modifiers, laws, failure modes, restoration arcs, or domain-specific
  expressions.

canonical_form:
  - "No new state variables without necessity"
  - "Do not multiply state variables unnecessarily"
  - "Map to S before expanding S"
  - "Most measurable conditions are diagnostics, not state variables"
  - "S = { O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ } remains the default state grammar"

protects:
  - state_vector_integrity
  - canon_stability
  - ontology_integrity
  - auditability
  - cross_module_compatibility
  - machine_readability
  - diagnostic_comparability
  - teaching_clarity
  - translation_integrity

state_vector_effects_when_preserved:
  O: "preserved_through_state_grammar_stability"
  H: "not_created_by_variable_redundancy"
  ε: "reduced_through_clear_classification"
  ι: "stable_or_decreasing"
  Au: "stable_or_increasing"
  µᵢ: "preserved_through_clear_variable_meaning"
  BΣ: "state_vector_boundary_intact"
  K: "high_across_modules"
  R: "available_for_reclassification_if_needed"
  Φ: "measurement_detail_not_misclassified_as_coherence"

state_vector_effects_when_violated:
  O: "decreasing_due_to_state_vector_bloat"
  H: "increasing_from_redundancy_and_maintenance_debt"
  ε: "increasing_as_confusion_contradiction_or_duplication"
  ι: "increasing_when_variable_expansion_appears_precise_but_reduces_coherence"
  Au: "decreasing"
  µᵢ: "degraded_by_variable_saturation"
  BΣ: "state_vector_boundary_weakened"
  K: "decreasing_across_modules"
  R: "required_for_consolidation"
  Φ: "local_measurement_gain_dominant"

primary_u_layer: U4
core_model_boundary_layer: U2
field_layer: U6
memory_layer: U7
time_layer: U5
execution_layer: U3
resource_layer: U1

violation_signatures:
  - diagnostic_becomes_state_variable
  - domain_expression_becomes_universal_variable
  - composite_index_becomes_primitive_variable
  - scaling_effect_becomes_variable
  - gate_threshold_becomes_variable
  - failure_mode_indicator_becomes_variable
  - symbolic_term_becomes_variable_too_quickly
  - existing_state_vector_mapping_ignored

related_failure_modes:
  - State Vector Inflation
  - Variable Redundancy
  - Ontology Bloat
  - Canon Drift
  - Diagnostic State Confusion
  - Gate State Confusion
  - Scaling State Confusion
  - Domain Overgeneralization
  - Composite Index Reification
  - Symbolic Over Variable Drift
  - Machine Schema Fragility
  - Cross Module Compatibility Loss
  - Auditability Collapse
  - Teaching Complexity Inflation
  - Metric Saturation
  - Terminology Saturation
  - Registry Boundary Failure
  - Model Drift

related_restoration_arcs:
  - State Vector Discipline Restoration
  - Variable De Duplication
  - Diagnostic Reclassification
  - Gate Reclassification
  - Scaling Rule Reclassification
  - Domain Expression Mapping
  - Ontology Compression
  - Canon Boundary Repair
  - Cross Module Alignment
  - Machine Schema Cleanup
  - Glossary Clarification
  - Composite Index Decomposition
  - Temporal Revalidation
  - Registry Reclassification
  - Construct Consolidation

related_laws:
  - State Vector Compression Law
  - No New Primitive Law
  - Ontology Compression Law
  - Canon Drift Law
  - Classification Integrity Law
  - Diagnostic State Separation Law
  - Metric Saturation Law
  - Complexity Auditability Gap Law
  - Translation Fidelity Law
  - Machine Schema Stability Law
  - Variable Inflation Law
  - Temporal Validation Law

related_scaling_rules:
  - State Vector Inflation Risk Under Scale
  - Diagnostic Registry Absorption Requirement
  - Machine Schema Fragility Under Variable Growth
  - Cross Module Comparability Burden Growth
  - Terminology Saturation Under Scale
  - Domain Expression Growth Before State Expansion
  - Variable Admission Gate Strengthening
  - Canon Review Requirement Under Scale
  - Metric Saturation Risk Under Scale
  - Translation Fidelity Loss Under Scale
  - Teaching Burden Growth

related_gates:
  - State Variable Admission Gate
  - Canon Admission Gate
  - Registry Classification Gate
  - No New Primitive Gate
  - Diagnostic State Separation Gate
  - Gate State Separation Gate
  - Scaling State Separation Gate
  - Composite Index Gate
  - Domain Translation Gate
  - Machine Schema Integrity Gate
  - Temporal Validation Gate
  - Cross Module Compatibility Gate

19. Compact Canon Statement

UTS-INV-032 states that no new state variables should be added without necessity. New concepts must first be mapped to the canonical state vector `S = { O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ }` or classified as diagnostics, derived metrics, gates, regimes, lenses, scaling rules, laws, failure indicators, restoration markers, constructs, or domain expressions. A new state variable is admissible only if it represents a distinct, irreducible system state that the existing vector cannot express.

20. Short Reference Version

UTS-INV-032 — No New State Variables Without Necessity

Map to S before expanding S.

S = { O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ }

Important does not mean state variable.
Measurable does not mean state variable.
Domain-specific does not mean state variable.

Most new conditions belong as diagnostics,
derived metrics, gates, regimes, lenses,
scaling rules, failure indicators, restoration markers,
constructs, or domain expressions.

Core rule:

Do not expand the state vector unless irreducibility is proven.