# Encoding Guide > How to create a 32-bit UHT code that semantically represents any entity. This guide explains how to assign a **Universal Hex Taxonomy (UHT)** fingerprint to any object, concept, system, or force by selecting the traits that apply across four semantic layers. --- ## Overview Each UHT code is a 32-bit binary string (or 8-character hex code), where each bit corresponds to one of 32 traits. These traits are grouped into four **semantic layers**: - **Physical (1–8)**: Material form, perception, passivity - **Functional (9–16)**: Purpose, behavior, system interaction - **Abstract (17–24)**: Symbolism, logic, hierarchy, temporality - **Social (25–32)**: Culture, governance, identity, visibility --- ## Encoding Steps ### 1. **Identify the Entity** Be specific and narrow in scope — are you encoding: - A physical object? - A type of behavior? - A document, tool, or concept? > *Tip: Avoid encoding a category unless you intend to define its archetype.* --- ### 2. **Apply a Critical Minimalist Mindset** UHT encoding uses a **"seek-to-exclude"** approach: - Default to **false** unless the trait clearly applies - Justify every **1** with evidence, not intuition - Compress meaning without distortion > *“Sparse but precise is better than bloated and vague.”* --- ### 3. **Evaluate Traits by Layer** #### **Physical (Traits 1–8)** Does the entity... - Exist materially? - Have a fixed shape? - Exhibit passivity? - Come from nature, engineering, or biology? #### **Functional (Traits 9–16)** Does it... - Serve a purpose? - Emit signals or outputs? - Operate independently or as part of a system? #### **Abstract (Traits 17–24)** Is it... - Symbolic? - Logical or rule-based? - Temporal or self-referential? #### **Social (Traits 25–32)** Is it... - Constructed or governed socially? - Culturally visible or identity-linked? - Taught or interpreted through shared norms? --- ### 4. **Toggle Traits & Build the Code** Turn on only the traits that are justifiably true. This will result in a: - **Binary string** (e.g., `01011101 10101010 01111111 11111111`) - **Hex code** (e.g., `5D AA 7F FF`) Use tools like **[[HexLens v0.1]]** to build and visualize the code. --- ## Encoding Tips - **Don’t conflate visibility with materiality** — something can be perceptible but not made of matter. - **Passivity ≠ uselessness** — a wall or resistor can be vital but still passive. - **Symbolic ≠ visual** — a rock may be seen but not symbolic unless it represents something. - **Be cautious with Trait 32 (“Widely known”)** — it implies global recognition or archetypal familiarity. - **System-critical ≠ important** — it must be necessary for the function of its containing system. --- ## Example: Encoding a Rock - **Physical:** 1 (Object), 4 (Fixed), 6 (Perceptible), 7 (Material), 8 (Passive) - **Functional, Abstract, Social:** *None* → **UHT Code:** `93 00 00 00` See also: [[93 00 00 00 - Rock]], [[93 00 00 00 - Raw Natural Substances]] --- ## Related Pages - [[UHT Trait Definitions (Full List)]] - [[HexLens v0.1]] - [[5D AA 7F FF - Canonical Layers]] - [[UHT Overview]] - [[Hex Decoding Guide]] --- > UHT encoding is not about guessing — it’s about **semantic compression** with precision and discipline. Metaclass [[5D AA 7F FF - Formalised Semantic Frameworks]]