1. Short Definition

Trajectory is the long-horizon direction or bias of system evolution across time, revealed through repeated selection, consequence, recurrence, and field effects.

2. Canonical Definition

In UTS, Trajectory is represented by the operator:

Τ

Trajectory describes where a system is going, not merely what it claims, intends, performs, or displays in the moment.

Trajectory is revealed through:

• repeated selections
• consequence patterns
• recurrence
• delayed effects
• ring-down
• hidden debt movement
• boundary changes
• meaning continuity
• field-level coherence

Canonical question:

Where is the system actually moving over time?

Trajectory is therefore central to time validation.

3. Functional Role in UTS

Trajectory supports:

• intention validation
• identity continuity
• restoration closure
• basin transition
• governance legitimacy
• AI behavior review
• contract validity
• justice repair
• meta analysis
• meaning integrity

A system’s trajectory may contradict its stated values, local metrics, or immediate presentation.

UTS evaluates trajectory because coherence must persist across time, not only appear in the present.

4. Diagnostic Signatures

Coherent trajectory

Τ coherent
O↑ or stable over time
H↓
µᵢ preserved
R sufficient
𝓓(t) improves
recurrence weakens

Trajectory drift

stated aim ≠ revealed direction
O↓
H↑
µᵢ↓
Φ replaces O
old basin recurs

False trajectory claim

declared transformation
but recurrence remains unchanged

This indicates narrative change without real directional shift.

5. Canonical Distinctions

Trajectory is not stated goal

Goals are claims.

Trajectory is revealed by time, selection, and consequence.

Trajectory is not intention alone

Intention is directional bias.

Trajectory is the actual path taken under constraint.

Trajectory is not short-term movement

A local improvement may still belong to a degraded long-term trajectory.

Trajectory is not destiny

Trajectory can be redirected through constraint, repair, selection, and attractor change.

6. U-Layer Mapping

7. Common Failure Patterns

8. Restoration Implications

Trajectory restoration requires redirecting repeated selection, not merely changing language or immediate output.

Typical sequence:

Μ map revealed trajectory
→ compare claim, action, consequence, and recurrence
→ Ξ detect drift or inversion
→ restore Au and FI
→ repair H
→ seed higher-coherence attractor
→ Τ validate new direction over time

A trajectory is restored when the system repeatedly selects toward coherence under pressure.

9. Machine-Readable Summary

glossary_entry:
  id: "GL-150"
  term: "Trajectory"
  symbol: "Τ"
  short_definition: "The long-horizon direction or bias of system evolution across time, revealed through repeated selection, consequence, recurrence, and field effects."
  term_family: "Foundational System Terms"
  term_class:
    - "Core Concept"
    - "Temporal Primitive"
    - "Selection Pattern"
  diagnostic_positive:
    - "Τ coherent"
    - "O↑ or stable over time"
    - "H↓"
    - "µᵢ preserved"
    - "R sufficient"
    - "𝓓(t) improves"
  diagnostic_negative:
    - "stated aim ≠ revealed direction"
    - "O↓"
    - "H↑"
    - "µᵢ↓"
    - "Φ replaces O"
    - "old basin recurs"
  core_distinctions:
    - "Trajectory is not stated goal."
    - "Trajectory is not intention alone."
    - "Trajectory is not short-term movement."
    - "Trajectory is not destiny."