Erid: An Umbrella Domain, Not a Product Landing
rocky beginner 3 min read
What this means for you
erid.tech is the public-facing directory and voice for the rocky-hq superproject. Twelve subsystems named from Project Hail Mary canon, addressed as *.erid.tech so the conceptual map and the DNS map agree. The apex is one paragraph and one list. There is no waitlist, no pricing page, no testimonial wall.
The pitch
Two paired primitives, equally weighted. A scene paragraph in italic regolith locating the reader in the operational world the system inhabits. A monospace directory of citizens with subdomain, role, and live-or-reserved state. The operator console at rocky.erid.tech is one citizen, not the headline. So is the docs reader. So is everything else.
Who it’s for
A peer or collaborator who saw the domain on a commit, in a dependency, or in a conversation, and wants to understand the conceptual map of the system in under a minute.
Proof points
- Twelve named citizens listed at apex: rocky, eva, petrova, cairnet, lore, hearth, ralph, pebble, airlock, hatch, relay, hubble. Every name traces back to Andy Weir or WALL-E canon
- Three apps in the umbrella ship as Next.js 15 static exports: erid-apex, erid-coming-soon, erid-docs; cairnet ships as a Next.js 14 product surface
- Reserved citizens render in the directory in the same row, same monospace, same role label as live citizens, dimmed only by 60% regolith opacity per DESIGN.md §5
- Forced-dark, no toggle: dark is a substantive choice, the mineral substrate is the brand, documented in DESIGN.md to prevent re-litigation
mindmap root((erid.tech)) Scene paragraph italic regolith operational register capped at 68ch Citizen directory monospace rows live or reserved hand-typed feel Twelve citizens rocky console cairnet feed docs reader nine reserved Refusals no hero CTA no waitlist no logo wallneighbors on the map
- Rocky Superproject Topology onboarding a new submodule into rocky-hq
- Four Things erid.tech Refuses to Be answering 'why does erid.tech look so spare?'