Minimum Requirements

• Operator must represent a team, organisation, or deployment group
• Use case must reflect infrastructure discipline (no personal tunnel activity)
• Regional preference must match available zone trust logic

Signal & Behavior Checks

• Initial contact reviewed for entropy, drift behavior, and sponsor integrity
• Sponsors may request prior deployment history or audit trail
• Unstable signals or misaligned use cases may be silently rejected

Tier Expectations

• Most new glyphs begin at Tier 1 - basic infrastructure access
• Tier 2 may be granted for config deployment roles or multi-node operations
• Tier 3 is reserved for infrastructure stewards and cannot be requested directly

Sponsor Vetting Logic

• Issuing sponsor decides eligibility based on signal review and lineage risk
• Glyph behavior is monitored post-issuance - degraded use may affect both operator and sponsor Tier
• Sponsors may pause glyph issuance during entropy recalibration periods

Best Practices

• Submit complete operational details when requesting access via voice channel
• Indicate your nearest jurisdiction and intended deployment scale
• Maintain sponsor relationship for future upgrades or zone requests

“Eligibility isn’t about who you are, it’s about how your signal behaves.”