Referral Logic Overview

• Glyph-Linked Access: configs issued only through validated referral glyphs
• Tier Enforcement: access boundaries are shaped by sponsor lineage
• Region Binding: referrals align with jurisdiction or physical node targets
• Usage Entropy: irregular behavior may trigger glyph deactivation

Why Referral Discipline Matters

• Nodes calibrate trust only through known lineage structures
• Public sharing or recycled configs introduce unpredictable actors
• Referral drift weakens signal integrity and erodes node provisioning pools
• Sponsor performance impacts downstream glyph eligibility

Consequences of Referral Misuse

• Silent glyph revocation without notice
• Tier rollback for operators who breach referral trust
• Node entropy scoring downgrade affecting sponsor reputation
• Access throttling or denial for linked operators in the same referral tree

Boundary Integrity Signals

• Glyphs matched against sponsor authenticity and zone bias
• Node logs scanned for anomalous cross-jurisdiction activity
• Zone drift triggers glyph quarantine or manual review
• Referral trees audited weekly for lineage clarity and entropy trends

Best Practices for Glyph Holders

• Only refer operators with verified infrastructure purpose
• Do not share configs or route traffic outside zone assignment
• Monitor Tier status and node stability via dashboard indicators
• Report suspected misuse or glyph drift through encrypted channel

“A glyph is a compass, not a key. Share it without discipline, and it points nowhere.”