Public Entity View — 7 Redesign Directions

Same content as entities/[domain] today (entity details, addresses, registration, partners, children), restyled with the Entity Blue design tokens from Dashboard-UI's DESIGN.md. Pick a direction — none of this touches production code yet.

Cards, Refined

Closest to today's structure — same sections and tabs, but every block becomes a Card with badges, mono addresses, and proper radius/shadow.

Hero + Two-Column

Bold identity hero up top, then a 60/40 split: primary details on the left, a compact sidebar of quick facts on the right.

Stat Dashboard

Leads with a 4-up stat card row (status, jurisdiction, partners, formed date) — same grid pattern used across Dashboard-UI.

Verified Certificate

Leans into "Verified Facts Identifier" — a certificate-style card with a verification ribbon, then supporting sections.

Sidebar App Shell

Sticky identity rail on the left (avatar, quick actions) with tabbed content on the right — mirrors the dashboard's sidebar layout principle.

Entity ID First

Puts the Entity ID at the centre — copy + Open on ENS on every identifier — and groups facts by provenance: Registrar, Global identifiers, and the Entity.ID/RegistryChain system. Surfaces the subject of right and the constitution + constituents model.

Public Record ★

The production candidate from the UX + brand working session: a "good standing at a glance" verdict, provenance-grouped facts with source rails (Registrar → Global identifiers → Entity.ID record), an accountability chain to a verified natural person, and site-voice copy throughout. "Diligence is a URL."