Network/Register/Profile Recognition And Badge Model
Gap Register
G-051Public

Profile recognition and badge data model

Tier 2 — Structurally thin, not launch-blocking
Status
Open — not started
Owner
Creator
Why now
Founding, Emeritus, and memorial markers are constitutionally required on Profile but have no data model or UI yet.
Related
Entry 026, Entry 027

Model the recognition markers the Constitution requires on Profile — Founding-contributor, Emeritus, memorial / posthumous — and how they derive and display on the @handle surface.

Why this matters

The Constitution requires recognition to be visible on Profile — Founding status (founding-grants appendix), the Emeritus badge and memorial / posthumous designations (Layer 13). The Atlas profile (Entry 027) is the surface, but nothing is modeled. Open decisions:

  • Data model — badges / recognition as records on the identity entity, and which are permanent versus state-dependent.
  • Derivation — markers that are pure functions of credit / Power history and grant records (Founding, Emeritus thresholds) versus those granted by process (memorial designation).
  • Lifecycle states — memorial and posthumous accounts, Emeritus re-entry, and locked / heir-editable states (Layer 13).
  • Display — how recognition renders on /@handle and in inline attribution, within the declarative (no-arbitrary-markup) profile.