WISP™ — the identity object

WISP is the object at the center of the architecture: a multi-attribute composite identity — narrative, temporal, role, spatial, behavioral — bound under a one-way cryptographic transformation and resident on a manifold of configurable topology. It is explicitly not a credential: there is nothing separable to steal, replay, or revoke. The LOGOS™ pipeline produces it, scores it for coherence, trust, and drift against its own history, and re-measures it live every time execution is requested. The object primitive is the estate’s first granted patent; the architecture operating on it is filed separately — which is why WISP is the most documented technology in the stack.

Imagine no passwords. Nothing to invent, nothing to forget, nothing to reset on a Monday morning — and nothing to phish, reuse, stuff, or spill in a breach, because there is no secret anywhere to spill. A password is a secret you must remember that someone else can steal; a token is only a password a machine remembers for you. Both fail the same way: possession is authorization, so whoever holds the artifact is you.

WISP removes the artifact. Authorization is not a thing you hold; it is a measurement of who you are — taken live, from how you write, when you act, where you are, and how you behave — scored against your own history, and taken again at every dispatch.

And the measurement runs where you are. WISP runs locally: the signals it reads never need to leave the device that read them. There is no company server holding your history, no behavioral profile accumulating in someone else’s cloud — the identity object is computed from data that stays yours, on hardware that stays yours. Privacy is not a policy promise bolted on afterward; it is the topology — and the topology is dynamic, itself part of what is filed. The architecture’s trust boundaries are free variables, and the same objects run unchanged across every drawing of them: one machine, air-gapped — the tightest, a single device measuring its own user; local with a remote notary; or fully distributed. The interactive stack lets you switch between those topologies yourself and watch the boundaries redraw.

There is nothing to remember, so nothing to forget. There is no separable bearer credential in the authorization path, so the attacks that depend on obtaining one behave differently: an intercepted measurement is bound to the moment it was taken and to the history it was scored against, which is what defeats replay. And because nothing is issued, there is nothing to revoke — expiry is a property of the object rather than an entry on a list. These are specific structural properties rather than a general security guarantee; the classes of attack they remove are named in the standard, and the ones they do not are named beside them. This is the claim of utility, and it is not aspirational — it was written as an essay in May 2025, filed that same week, examined, and issued as granted U.S. Patent 12,688,267 B1. The documents below are that claim, at every altitude — from the granted claims to the standard an independent implementation can be certified against.

The written trail is the estate’s longest: the May 2025 provisionals (narrative-coherence identity), the founding essay on replacing passwords with measured behavior (arriving with Arc’s Archive), the S(R,F) series’ Wisp paper, the utility filed August 2025 and granted eleven months later, the standard and specification of September 2026, and the certification mark on file. Where WISP sits in the running system — and how the pipeline that produces it composes — is the interactive stack.