Why Referrals Exist
- Preserve infrastructure exclusivity and control
- Prevent mass onboarding and unauthorized tunnel deployments
- Ensure each operator inherits a verified sponsor lineage
How Access Is Granted
- Glyphs are generated by Tier 2 and Tier 3 users only
- Each glyph contains metadata: Tier level, slot allocation, issuance timestamp
- Glyphs expire after usage or signal drift
- Manual glyph issuance via encrypted voice channel for sensitive deployments
Referral Gate Logic
- Digital onboarding suspended during infrastructure recalibration phases
- Every glyph undergoes backend validation before provisioning
- Referral lineage logged silently - not shown on public dashboards
Best Practices
- Do not share glyphs publicly or outside intended operator identity
- Use encrypted contact methods for sponsor-to-operator issuance
- Review your Tier before inviting, upgrades unlock new referral slots
“Access isn’t granted, it’s inherited through encrypted trust.”