Light-weight Identity

A mid-2000s decentralized web-identity architecture that used subject-controlled HTTP URLs, published service metadata and public-key authentication without a central identity provider.

Version

v1 · 2026-09-08 · History

Domain-specific #

5325

Origin domain

digital identity

Subdomain

decentralized web identity

Core Idea

Light-weight Identity was a protocol family and implementation approach in which a person's web URL identified them and exposed decentralized authentication, profile and messaging services. A relying party dereferenced or discovered metadata from the identity URL, associated cryptographic keys and endpoints with the subject, and performed REST-style authenticated exchanges. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

Light-weight Identity belongs to digital identity and is useful where the analyst can specify a subject-controlled URL, a web server, machine-readable identity metadata, public and private keys, HTTP interactions, service endpoints, and relying parties, then evaluate identity authority is rooted in control of the subject's URL and corresponding keys rather than registration with one central provider. The scope is broad within that domain but bounded by the need for identity authority is rooted in control of the subject's URL and corresponding keys rather than registration with one central provider. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity

The abstraction clarifies a crowded vocabulary by making identity authority is rooted in control of the subject's URL and corresponding keys rather than registration with one central provider the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Light-weight Identity can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Light-weight Identity. Light-weight Identity compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

1. Identify the carrier. State what the elements, states, objects, or observations are: a subject-controlled URL, a web server, machine-readable identity metadata, public and private keys, HTTP interactions, service endpoints, and relying parties. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express identity authority is rooted in control of the subject's URL and corresponding keys rather than registration with one central provider independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of digital identity because they reuse a subject-controlled URL, a web server, machine-readable identity metadata, public and private keys, HTTP interactions, service endpoints, and relying parties, A relying party dereferenced or discovered metadata from the identity URL, associated cryptographic keys and endpoints with the subject, and performed REST-style authenticated exchanges., and type the carrier, state every parameter and convention in the definition, test that identity authority is rooted in control of the subject's URL and corresponding keys rather than registration with one central provider, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Current abstraction Light-weight Identity Domain-specific

Parents (1) — more general patterns this builds on

• Light-weight Identity is a kind of Representation Prime

  The proposed strict upward parent is prime:representation.

Hierarchy path (1) — routes to 1 parentless root

• Light-weight Identity → Representation → Abstraction

Neighborhood in Abstraction Space

Light-weight Identity sits in a moderately populated region (56^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Messaging Protocols & Networked Services (23 abstractions)

Nearest neighbors

• URL — 0.91
• Passwordless authentication — 0.89
• Anonymous P2P — 0.88
• Multi-factor authentication — 0.87
• Domain application protocol — 0.87

Computed from structural-signature embeddings · 2026-09-08