The Seven Laws of Identity

Identity has rules.

The Seven Laws ask whether an identity system serves the person across many contexts without turning them into a universal record. Liir answers each law with an architectural boundary, not a privacy preference that can be switched off later.

Choose a law
Law 1 · User Control and Consent

The person decides what identifying information moves.

A request arrives through one relationship. Nnhren applies the person’s policy, asks when necessary, and sends only the approved result.

Liir mechanismPerson-side authorization
Visible decisionApprove, decline, or set policy
Structural boundaryNo silent disclosure path
The Liir rule: Nothing about a person moves merely because a counterparty knows where to ask.

Why the laws matter

A useful identity system can still be shaped incorrectly.

Encryption alone does not prevent a universal identifier, an unnecessary party, an unreadable consent screen, or a different identity ritual at every door. The Seven Laws test the whole relationship between person, counterparty, operator, and context.

Not a checklist

The laws constrain each other

Minimal disclosure without directed identity can still create a universal trail. Control without consistent experience can still become dark-pattern consent.

Not policy

The boundaries live in structure

Pairwise capabilities, scoped requests, expiring authority, and person-side custody make the safer path the normal path.

Not one issuer

Authority remains plural

Government, institutions, communities, and counterparties retain the authority appropriate to the facts they originate.

Not one context

The human grammar stays familiar

The person sees the same request, scope, counterparty, approval, and receipt pattern across different kinds of interaction.

All seven

Seven laws. Seven concrete consequences.

Each law changes what the system is allowed to know, keep, ask, show, or decide.

1

User Control and Consent

Identifying information moves because the person authorizes a named request, not because an institution can query a central profile.

  • Mechanism: Nnhren policy, fresh approval, expiry, and revocation.
  • Boundary: a request can be declined without opening the Vault.
2

Minimal Disclosure for Constrained Use not built yet

The stable answer is the smallest fact that satisfies the purpose.

  • Mechanism: disclosure ceilings and issuer-signed presentations.
  • Boundary: “over 18” does not require birth date, address, photograph, or ID file.
3

Justifiable Parties

Only parties with a necessary role in this relationship receive the disclosure.

  • Mechanism: named counterparty, purpose-bound capability, recipient encryption.
  • Boundary: Liir does not add itself as the reader, adjudicator, or data broker.
4

Directed Identity

Public presentation and private relationships require different identifiers and different expectations.

  • Mechanism: owner-authorized public artifacts and private pairwise capabilities.
  • Boundary: the master creates authority but never becomes the universal key used at every door.
5

Pluralism of Operators and Technologies

Identity must compose across issuers, authenticators, rails, clients, and operators rather than requiring one sovereign platform.

  • Mechanism: published formats, export, passkeys, standard signatures, and issuer independence.
  • Boundary: Liir verifies accepted authority without becoming the only possible authority.
6

Human Integration

The person is a security component who can recognize what is happening and which counterparty is present.

  • Mechanism: live Liirlit state, shared interaction context, visible recipient, scope, value, and finality.
  • Boundary: copied or static pixels do not inherit live authority.
7

Consistent Experience Across Contexts

People should not need a new identity rulebook for every institution, device, or transaction.

  • Mechanism: the same Greet, Ask, Approve, Prove, Pay, Share, and Recover grammar across Liir surfaces. not built yet
  • Boundary: context changes the request, not the meaning of consent or authority.
One request under seven laws not built yetPerson present
1
Venue requests age eligibilityNamed purpose and counterparty
Now
2
Nnhren shows the smallest answerOver 18 · issuer signed
Waiting
3
Person approves this relationshipNo universal identifier presented
Waiting
4
Verifier receives one factDocument and unrelated fields remain sealed
Waiting
One interaction carries all seven: control, minimal disclosure, justified parties, directed identity, plural authority, human presence, and consistent grammar.

The laws compose

A single proof request must satisfy all seven at once. The person controls it. The answer is minimal. The counterparty is justified. The identity is relationship-scoped. The issuer remains independent. The human sees what is happening. The grammar is familiar.

Liir’s four carved boundaries

Four rules keep the seven laws intact.

Mark

Public never becomes universal

A public Liirlit may identify an owner by choice. Private relationships remain pairwise and unlinkable through Liir identifiers.

Alarm

Warning never grants control

An external send-only destination can warn that authority is changing. It cannot approve or complete Recovery.

Served-Code

Replaceable code does not receive the key

The trusted client boundary keeps storage operators from turning a deployment change into Vault access.

Anti-Graph

Capabilities resolve, people do not

The person’s Liir knows their relationships. Core infrastructure does not assemble them into a central person graph.

See how Communication, Identification, Proof, Handshake, Exchange, Recovery, and Storage put these laws to work.

Explore CIPHERS