Three Readers, in Order of Weight

What this means for you

erid.tech serves three audiences, in order. Operators of the pantheon between active sessions. Collaborators and peers evaluating the system from the outside. Curious passers-through forming an impression. There are no customers in this list. There is no funnel.

The pitch

Operators come first. They already know what rocky, ralph, cairnet, hearth, and the rest are; they land on the apex to navigate, to confirm a citizen is up, to read the latest decision. They reward density and refuse marketing fat. Peers want the conceptual map in under a minute. Passers-through are not converting; they are forming an impression that someone took this work seriously.

Who it’s for

Anyone writing copy for the apex, the docs reader, or a coming-soon page. Knowing which reader is being served decides whether a sentence stays or goes.

Proof points

• Three audiences named verbatim in PRODUCT.md, weighted in declared order: operators, peers, passers-through
• Context per PRODUCT.md: workstation or large monitor primarily; mobile for read-only checks; not a customer-acquisition surface
• Apex success criterion is single-sentence: a peer reads the scene once, scans the directory once, closes the tab knowing what the system is
• Zero conversion paths on the apex: no CTA buttons, no email capture, no waitlist form, no countdown timer, no newsletter signup

quadrantChart
  title Reader weight on erid.tech
  x-axis Casual --> Engaged
  y-axis Outsider --> Insider
  quadrant-1 Operators
  quadrant-2 Peers
  quadrant-3 Passers through
  quadrant-4 Returning collaborators
  Operator at 02:14 UTC: [0.92, 0.95]
  Engineer evaluating: [0.78, 0.32]
  Designer scanning: [0.55, 0.28]
  Commit-curious visitor: [0.22, 0.18]
  Returning peer: [0.65, 0.72]