Sacred Ritual Structure Protocol → Things/Gems

--- ring: sacred-ritual-gems onyx: srsp-things-gems-doc pearl: How the Sacred Ritual Structure Protocol maps to Things/Gems architecture citrine: state: complete ---

# Sacred Ritual Structure Protocol → Things/Gems

The Sacred Ritual Structure Protocol (SRSP) defined how .sh scripts organized sacred artifacts in directory hierarchies. As HEXCRAFT matured, every artifact type found its native home in the Things/Gems architecture.

## The Mapping

| SRSP Artifact | Things Archetype | Key Gems | |---|---|---| | Ritual script (.sh) | command | onyx (name), ruby (config), pearl (body) | | Scroll (.md) | scroll | onyx, pearl (body), sapphire (path) | | Torch definition | torch | onyx, ruby (config), pearl (body) | | FID pillar | fid | onyx, topaz (gaps), diamond (provenance) | | Ring container | ring | onyx, pearl (description), obsidian (parent ring) |

## Material Hierarchy Replaces Directories

Directory nesting is replaced by the obsidian jewelry chain:

``` Thing → obsidian.ring → Ring Thing → obsidian.parent → Material → Root ```

Materials define gem_signature constraints. A Thing inherits what gems it must carry from its Ring, which inherits from its Material.

## Gem Signatures as Schema

Each material enforces a gem signature — the minimum set of gems required:

- **Bronze** (base): onyx, sapphire — name + category - **Metals** (executable): + ruby, pearl — config + body - **Gold** (provenance): + diamond — full ancestry - **Alloy** (relational): + obsidian — relationships - **Biomaterials** (living): + topaz — self-observing

## Rings as Namespaces

Every Thing lives in a Ring. Rings are themselves Things (ring archetype), enabling infinite nesting. The `fid` ring contains all FID documents. The `gem` ring contains all gem definitions. Rings replace filesystem directories entirely.

## Status

Fully implemented. All Portal commands read from and write to Things. SRSP shell scripts are legacy — new artifacts are forged directly into the lattice.