# Temporal **Trait Number:** 23 **Layer:** Abstract **Bit Position:** 7 (bit 23 overall) **Binary Encoding:** `00000000 00000000 00000010 00000000` **UHT Code (self-encoding):** `00 00 02 00` --- # Icon ![[Icon23.png|200]] ## Definition The entity encodes or responds to **time, sequence, change over duration, or event progression**. It may represent temporal data, operate across intervals, or structure behavior over time. --- ## When to Apply Use this trait when the entity: - Involves **duration, timing, or sequencing** - Tracks or expresses **time-based change** - Relates to **scheduling, rhythm, delay, or history** Avoid applying if the entity: - Is **static, atemporal, or instant-only** - Exists purely as a **state or structure** without progression - Has no internal or external **timing component** --- ## Related Traits - [[00 00 01 00 Contextual abstraction]] — Many temporal entities are context-sensitive by sequence. - [[00 10 00 00 Transforms or modifies internal state]] — Entities that evolve may encode temporal structure. - [[00 40 00 00 Emits output or produces effect]] — Outputs may be sequenced over time. --- ## Examples - A clock or timer - A historical event timeline - A scheduler or animation engine - A behavior tree with sequencing - A log file with timestamps - A biological circadian rhythm --- ## Commentary This trait highlights the **dynamic dimension of abstract systems** — those where **change, progression, or ordering over time** matters. Temporal traits are vital in **event-driven systems, simulations, process modeling, music, biology, and control theory**. It’s useful to distinguish **temporal logic** (ordering of events) from just having a state — this trait captures **temporal semantics**, not just motion. --- **© 2025 Steven Holland. All rights reserved.** [[Copyright Statement]]