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.
The Seven Laws of Identity
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.
A request arrives through one relationship. Nnhren applies the person’s policy, asks when necessary, and sends only the approved result.
Why the laws matter
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.
Minimal disclosure without directed identity can still create a universal trail. Control without consistent experience can still become dark-pattern consent.
Pairwise capabilities, scoped requests, expiring authority, and person-side custody make the safer path the normal path.
Government, institutions, communities, and counterparties retain the authority appropriate to the facts they originate.
The person sees the same request, scope, counterparty, approval, and receipt pattern across different kinds of interaction.
All seven
Each law changes what the system is allowed to know, keep, ask, show, or decide.
Identifying information moves because the person authorizes a named request, not because an institution can query a central profile.
The stable answer is the smallest fact that satisfies the purpose.
Only parties with a necessary role in this relationship receive the disclosure.
Public presentation and private relationships require different identifiers and different expectations.
Identity must compose across issuers, authenticators, rails, clients, and operators rather than requiring one sovereign platform.
The person is a security component who can recognize what is happening and which counterparty is present.
People should not need a new identity rulebook for every institution, device, or transaction.
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
A public Liirlit may identify an owner by choice. Private relationships remain pairwise and unlinkable through Liir identifiers.
An external send-only destination can warn that authority is changing. It cannot approve or complete Recovery.
The trusted client boundary keeps storage operators from turning a deployment change into Vault access.
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