The technologies

These are not products; they are the named organs of one architecture — and the architecture itself is the Sovereignty Stack: the LOGOS™ pipeline producing and continually re-validating the WISP™ identity object over the SOV substrate. WISP™ decides who. SAGE™ decides whether. RITA™ decides as whom. KRONOS decides when — and how much time has cost. MUSASHI™ and KNOX™ turn decisions into cryptographic authority; AEGIS™ enforces it; LOGOS™ gives the whole system its semantic senses; Pulse Mesh™ carries every message between the parts, in one fixed 128-byte envelope. Each technology follows the same lifecycle — written first, filed second, built throughout, published after — and each card below links to wherever that technology’s documentation currently lives: whitepaper, standard, formal paper, or the registry entry holding its estate.

The architecture reads as a hierarchy, and no single technology sits at its head. Substrate carries, runtime composes, engines decide, surfaces meet the world — and nothing depends upward, so the foundation is the substrate, where every type, wire format, and transport primitive originates. WISP™ is the identity object within that architecture: one of the technologies, sitting among the engines, and the one that so far carries a granted patent. Because the role, governance, and custody engines all consume the composite identity object it produces, WISP illustrates a large component of the architectural foundations — but it is not the architecture itself.

signals → AXIS normalizes → RITA™/SAGE™ mint the authorization → KNOX™ notarizes with temporal authority → AEGIS™ enforces the boundary → the WISP™ travels out — and is re-measured on return — Canon, Lexicon, Pulse Mesh™, Musashi™/Kronos, and Hermes carry it all

Beneath the seven, the supporting stack — each a named system with its own filed estate, documented as its layer of the architecture publishes. The full stack, with the estate behind every entry, lives in the registry’s stack view.