The seven components of the canonical identity engine — definitions from the Official Vocabulary v1.3.
Captures, reads and prepares any input — PDF, image, XML, JSON, API, sensor. May use OCR, computer vision or other interpretive technology. Interprets the world — never decides identity. No output from the Universal Engine takes part in the canonical proof.
Works exclusively with verifiable Canonical Keys and exact mathematical rules. Never interprets: verifies. No AI, no probability, no heuristics — the same valid input always produces the same result, across any independent implementation.
"The Universal Engine interprets the world. The Canonical Engine proves identities. No interpretive output takes part in the Canonical Proof."
Capture and extraction of structured fields from the input element — physical or digital documents, in any format. The capture technology (OCR, parsers, computer vision) is replaceable; the functional step remains.
Canonical normalization and scanning that prepares the canonical vector: abbreviations, accents, order and formats converge into a single representation of the same information.
The immutable heart of the protocol. Applies deterministic normalization over the asset's verified Canonical Keys and produces the canonical representation that originates the AC⚡IDN. Same valid input, same result — no AI, no probability, no heuristics.
The parity engine emits the protocol's official, legally-neutral response in five public states: AC⚡UNI [Unique] · AC⚡DUP [Duplicity] · AC⚡PAR [Parity — legitimate variant] · AC⚡QTN [Quarantine — under validation] · AC⚡INL [Identity not located or document illegible]. The protocol delivers evidence; the legal conclusion belongs to the institution.
The knowledge base consulted in every decision: Golden Rules, canonical profiles per asset family, relationships between variants and history. Does not register assets; does not execute decisions — governs the rules applied by the Parity Engine.
Permanent record of approved decisions and assets, with blockchain anchoring links. The Oracle decides; the Registry only preserves.
The asset's genealogy: versions, transformations (split, merge, succession) and variants mathematically linked to the ancestor — including the chain of authorizations that produced each change. Duplicity remains detectable even after the asset changes.