Atlas Face Things and Gem Chords
# Atlas Face Things and Gem Chords
## Invocation
The question is not which gem "owns" an Atlas face in the abstract.
The question is: if each Atlas face is itself a **Thing**, what gem arrangement — what **gem chord** — gives that Thing its essence?
This means gem meaning must remain fixed. The gems do not change their law from Thing to Thing.
What changes is: - which gems dominate, - which fields matter most, - and how the Thing's body is composed.
This is the proper distinction.
---
## Gem Law Must Remain Canonical
The current canonical assignments are:
- **onyx** = name - **sapphire** = archetype / kind - **pearl** = content / body - **ruby** = classification / tags - **topaz** = all numeric measurements - **amethyst** = access / visibility - **obsidian** = relationships - **diamond** = provenance - **emerald** = timestamps / time - **citrine** = locality / realm / host / path
This law must not be bent casually.
So when speaking of an Atlas face-Thing, the correct move is not to reassign gem meaning, but to identify the **dominant gems in the chord**.
---
## General Thing Chord
Most Atlas face-Things will carry the same skeletal body:
- `onyx` — the Thing's name - `sapphire` — the Thing kind - `pearl` — descriptive body/content - `ruby` — classifications - `topaz` — numeric values - `obsidian` — linked Things - `citrine` — where it lives - `diamond` — provenance - `emerald` — when it was created/updated - `amethyst` — visibility/access
The difference between face-Things is not that this law disappears. The difference is **which gems become most load-bearing**.
---
## Example Correction: Node Thing
A Node Thing should not bend gem meaning either.
A more correct cut is:
- `onyx` = node name - `sapphire` = `"node"` - `pearl` = body/description of the node - `ruby` = classifications such as role, tier, kind - `topaz` = numeric fields such as port, weight, load, coordinates - `obsidian` = links to mesh, peers, services, parent Things - `citrine` = host, realm, path, network locality - `diamond` = provenance of creation - `emerald` = timestamps - `amethyst` = visibility/access
For **IP address**, the strongest canonical home is usually **citrine**, because IP is locality. Only if represented numerically for technical reasons would it lean topaz. If it is modeled as a relation to another network Thing, it may also appear through obsidian.
---
## Atlas Face Things
### 1. Element Thing
**Dominant gems:** pearl, ruby, obsidian, topaz
- `onyx` = element name - `sapphire` = `"atlas-element"` - `pearl` = body/description of the element - `ruby` = classifications such as leaf, rune, chip, decal - `topaz` = width, height, area, count - `obsidian` = links to atlas, family, surface, layer - `citrine` = atlas sheet or source locality
An Element Thing is pearl-heavy because it is the visible packed unit itself.
---
### 2. Mask Thing
**Dominant gems:** ruby, topaz, obsidian
- `onyx` = mask name - `sapphire` = `"atlas-mask"` - `pearl` = description of what the mask does - `ruby` = mask mode such as alpha, cutout, binary, gradient - `topaz` = threshold, falloff, channel values - `obsidian` = links to element, surface, or layer Things - `citrine` = where the mask asset lives
A Mask Thing is not a new gem category. It is a Thing whose body is dominated by classification, numeric cut law, and relation.
---
### 3. Bounds Thing
**Dominant gems:** topaz, citrine, obsidian
- `onyx` = bounds name - `sapphire` = `"atlas-bounds"` - `pearl` = note or description of the region - `ruby` = region class such as frame, bleed, reserved, active - `topaz` = x, y, width, height, padding - `obsidian` = links to element and atlas - `citrine` = local sheet or field locality
Bounds are topaz-heavy because they are fundamentally measurement.
---
### 4. Index Thing
**Dominant gems:** obsidian, topaz, ruby
- `onyx` = index name - `sapphire` = `"atlas-index"` - `pearl` = lookup/body description - `ruby` = index mode/classification - `topaz` = slot number, ordering, numeric index - `obsidian` = links to indexed members - `citrine` = scope or locality of the index
Index is not "sapphire by essence" merely because it feels formal. Its actual body is relation plus ordered retrieval.
---
### 5. Surface Thing
**Dominant gems:** pearl, ruby, topaz, obsidian
- `onyx` = surface name - `sapphire` = `"surface"` or `"atlas-surface"` - `pearl` = body describing material appearance - `ruby` = classifications such as rough, polished, emissive, organic - `topaz` = roughness, metallic, opacity, scale values - `obsidian` = links to material body, textures, and elements - `citrine` = vessel or asset locality
Surface is pearl-heavy because it is still a descriptive/rendered body, but it relies heavily on classification and numeric channels.
---
### 6. Variation Thing
**Dominant gems:** ruby, topaz, obsidian, pearl
- `onyx` = variation family name - `sapphire` = `"variation"` - `pearl` = description of how variants differ - `ruby` = classifications such as damaged, bright, dark, seasonal - `topaz` = seed, weight, probability, count - `obsidian` = links to sibling variants and parent element - `citrine` = source locality
Variation is a family Thing, not a violation of identity.
---
### 7. Scatter Thing
**Dominant gems:** topaz, obsidian, citrine, ruby
- `onyx` = scatter law name - `sapphire` = `"scatter"` - `pearl` = description of distribution behavior - `ruby` = clustering mode/classification - `topaz` = density, radius, jitter, spacing, falloff - `obsidian` = links to target field, atlas, mask - `citrine` = target locality or realm
Scatter is topaz-heavy because it is operationally numeric.
---
### 8. Layer Thing
**Dominant gems:** ruby, topaz, obsidian, citrine
- `onyx` = layer name - `sapphire` = `"layer"` - `pearl` = description of the layer's purpose - `ruby` = classifications such as overlay, underlay, decal, UI, terrain - `topaz` = order, depth, opacity, blend weights - `obsidian` = links to neighboring layers and affected Things - `citrine` = where the layer exists
Layer is a relational stratum, not just a visual term.
---
### 9. Resolution Thing
**Dominant gems:** topaz, ruby, citrine, obsidian
- `onyx` = resolution profile name - `sapphire` = `"resolution-profile"` - `pearl` = notes on fidelity - `ruby` = tier classifications such as low, medium, high, bake, runtime - `topaz` = width, height, mip count, pixel density - `obsidian` = links to surfaces/materials/vessels - `citrine` = platform or vessel locality
Resolution is topaz-heavy because fidelity is still measurable.
---
### 10. Packing Thing
**Dominant gems:** topaz, obsidian, ruby, citrine
- `onyx` = packing schema name - `sapphire` = `"packing"` - `pearl` = description of packing strategy - `ruby` = classifications such as tight, grid, grouped, channel-packed - `topaz` = fill ratio, padding, slot count, utilization - `obsidian` = links to atlas members and output sheet - `citrine` = output sheet locality
Packing is not "emerald" by essence even if it feels ecological. Canonically it is still classification, measurement, relation, and locality.
---
### 11. Projection Thing
**Dominant gems:** obsidian, citrine, topaz, ruby
- `onyx` = projection name - `sapphire` = `"projection"` - `pearl` = description of mapping behavior - `ruby` = classifications such as UV, triplanar, screen-space, decal, object-space - `topaz` = scale, offset, angle, projection depth - `obsidian` = links source atlas to target object/surface - `citrine` = target world, realm, or locality
Projection is relation-heavy because it is fundamentally a crossing from one body-space into another.
---
### 12. Vessel Thing
**Dominant gems:** citrine, ruby, obsidian, topaz
- `onyx` = vessel name - `sapphire` = `"vessel-target"` or a more specific vessel archetype - `pearl` = description of the incarnation target - `ruby` = classifications such as web, unreal, blender, ui, ar - `topaz` = numeric constraints, budgets, limits - `obsidian` = links to atlas, material, and object Things - `citrine` = where the vessel lives
Vessel is citrine-heavy because incarnation always has a locality.
---
## The Law of Dominance
So the correct language is not:
- "Mask belongs to Obsidian" - "Bounds belongs to Citrine" - "Packing belongs to Emerald"
That is too loose and risks breaking gem canon.
The stronger wording is:
- **Mask Thing is ruby/topaz/obsidian-heavy** - **Bounds Thing is topaz-heavy** - **Index Thing is obsidian/topaz/ruby-heavy** - **Surface Thing is pearl/ruby/topaz-heavy** - **Scatter Thing is topaz-heavy** - **Projection Thing is obsidian/citrine/topaz-heavy** - **Vessel Thing is citrine-heavy**
This preserves the canon while still naming the Thing's essence.
---
## Closing
**Gem meaning stays fixed.** **Thing essence changes by which gems dominate the chord.**
That is the law worth keeping.
A Thing is not made true by inventing a new gem meaning for convenience. It is made true by arranging the canonical gems in the correct body.
That is what gives the Thing its chord. That is what gives the Atlas faces their proper essence.