Seven capabilities. One architecture.

Communication, Identification, Proof, Handshake, Exchange, Recovery, and Storage. CIPHERS is the map of what a Liir does and the test every feature must pass.

CIPHERS
C · Communication

Nobody speaks into a relationship they do not hold.

Communication begins with shared context and a pairwise capability. A guessed name does not create reachability.

PrimitiveMutual relationship channel
Person controlsReachability and severance
Counterparty receivesOne authenticated channel
Liir refuses to keepA central contact graph

Why one Liir can do all seven

Everything comes from three primitives.

The same recoverable root creates relationship-specific authority; the same mutual channel carries each authorized interaction.

The root

Recoverable authority

The master creates and rotates pairwise authority. It does not become the identifier used in ordinary relationships.

The pairwise key

One spoke per relationship

Each counterparty receives a capability meaningful only inside that relationship.

The Mutual

Shared interaction context

Two endpoints can prove they are acting in the same live exchange without publishing the person.

Nnhren + Vault

Operate and remember

Nnhren evaluates requests. The Vault holds the person’s surviving state under their control.

The complete map

Seven verbs for a person-centered internet.

Each CIPHER names a human capability and a structural refusal.

CCommunicationSpeak through relationships people accepted, not through a universal address book or platform-owned contact graph.
IIdentificationLet the person appear publicly or privately per context without turning one identifier into a cross-site join key.
PProof not built yetPresent the requested sentence with issuer provenance instead of sending the document and every fact behind it.
HHandshakeLet two present endpoints confirm the same interaction and mutually create one private relationship.
EExchange not built yetBind payment, disclosure, recipient, and approval together while Liir holds keys rather than value.
RRecoveryReconstruct authority from two of three Recovery keys, raise an external alarm, and preserve surviving relationships.
SStorageKeep credentials, records, relationship state, and private artifacts in a Vault under the person’s key.
CIPHER testFive questions
MechanismPairwise channelWhat makes the capability work?
SecurityRelationship keyWhat prevents unauthorized action?
PrivacyNo global addressWhat information never needs to exist?
FailureCapability endsWhat happens when the relationship stops?
TruthShared contextWhat can the system honestly prove?

The five-question discipline

A feature is not complete when it only works.

Every CIPHER is examined from five directions: mechanism, security, privacy, failure, and claim accuracy. The last two keep a useful demo from quietly becoming an unsafe product promise.

The refusals

We refuse to read

Your data is not the business model

Storage and disclosure remain under the person’s key. Infrastructure carries authorized ciphertext and scoped results.

We refuse to decide

Issuer authority stays with issuers

Governments, institutions, and counterparties remain responsible for the facts and decisions that belong to them.

We refuse to carry value

The Liir is a key ring, not a purse

Payment authority reaches regulated rails. Liir does not become the balance everyone must trust.

We refuse the graph

Capabilities resolve, people do not

Core infrastructure need not assemble private relationships into a central map of the person.

Now see the laws underneath them.

CIPHERS describes what Liir does. The Seven Laws describe the identity discipline that keeps those capabilities centered on the person.

Read the Seven Laws