Open Lore NetworkOLN
Network/Register/Handle Policy And Namespace Claiming
Gap Register
G-047Public

Handle policy and namespace claiming

Tier 2 — Structurally thin, not launch-blocking
Status
Open — not started
Owner
Creator
Why now
Atlas profiles cannot ship without handle rules, and a self-serve namespace needs squatting and impersonation guards from day one.
Related
Entry 026, Entry 027, G-004

Define the @handle namespace — charset, uniqueness, claiming, renames, reserved words, and anti-squatting / anti-impersonation rules.

Why this matters

Members are addressed at theopenlore.net/@handle (Entry 026). The @ namespace is the platform's one self-serve address space, so it needs rules before it opens:

  • Charset, casing, length — allowed characters, case-insensitive uniqueness, confusable/homoglyph protection (ties to G-004 Sybil resistance).
  • Claiming and migration — claimed at sign-up or later? Backfilling the existing UUID-keyed profiles rows with handles.
  • Renames — how often, and what happens to old URLs. Attribution is permanent (Layer 9; Entry on Emeritus status), so renames need 301s and a stable internal id beneath the display handle.
  • Reserved words — system routes, network entity-type paths (person, …), and franchise slugs must all be unavailable as handles.
  • Squatting and impersonation — reservation for known contributors, impersonation policy (ties to G-001 Trust & Safety and the disciplinary framework), and memorial / Emeritus locked states.