CANONICAL IDENTITY ENGINE · PATENT PENDING

ACPROTOCOL& ORACLE Alternating  Current of Canonical Identity

ACIDN — CANONICAL IDENTITY NUMBER

A proprietary deterministic engine that recognizes the canonical elements of an asset and assigns it a single ACIDN, preserving its identity and its evolution over time.

PATENT PENDING — BRAZIL INPI BR 10 2026 010732-8 PROPRIETARY DETERMINISTIC ENGINE BLOCKCHAIN-AGNOSTIC
Presentation

ALTERNATINGCURRENT

ACPROTOCOL — Alternating  Current of Canonical Identity
ALTERNATINGCURRENT

Identifies · Classifies · Preserves

The same asset appears in many records and systems. ACPROTOCOL recognizes when they represent the same asset.

AC⚡IDENTITY
ACIDENTITY

Generates the identity. Extracts the canonical elements of the asset and produces a persistent reference, the ACIDN.

AC⚡IDN
ACIDN

Classifies. Each occurrence receives one of the five public states: ACUNI · ACPAR · ACDUP · ACQTN · ACINL.

AC⚡EVOLUTION
ACEVOLUTION

Preserves. Each asset has a canonical timeline: the document evolves, the identity remains.

The canonical identity (ACIDN) is generated by AlternatingCurrent outside the network and can be used on any DLT, public or private, with or without blockchain registration.

ARCHITECTURE

How the AlternatingCurrent works

Each stage answers one question. The asset comes in as a file or as structured data and leaves with its canonical identity and its state.

AC⚡IDN — Alternating⚡Current Identity

Proof Zero Layer
The document is not stored. After reading and processing, the file is discarded; only the asset's ACIDN and the occurrence record remain.

ACFAST

“Has this file been here before?”

Fast screening: recognizes an exactly identical file before any reading.

file × file

Universal Engine

“Are these files the same document?”

Reads PDF, photo, image or text and extracts the canonical elements. Different representations of the same document produce the same elements.

PDF × photo

Canonical Engine

“Does this asset already have a registered identity?”

Compares the received identity with the registered identities and returns one of the five public states.

registered ACIDN × received ACIDN

ACORACLE

“What is this asset’s identity for the network?”

Delivers the canonical identity and state of the asset to systems, DLT networks and smart contracts, sharing only the identifier.

API query

When the asset arrives as structured data, it goes straight to the Canonical Engine.

CODEFULL NAMEMEANING
ACUNIAlternatingCurrent UniquenessFirst registered occurrence: no other occurrence of this asset in the analyzed collection
ACPARAlternatingCurrent ParitySame identity, different document: the asset has evolved
ACDUPAlternatingCurrent DuplicationA canonical record of this asset already exists
ACQTNAlternatingCurrent QuarantineOpen review: the data does not allow the identity to be stated with confidence
ACINLAlternatingCurrent Not LocatedIdentity not located or document illegible

The code is the same in any language and in any system. AlternatingCurrent classifies; the institution decides.

Examples of occurrences

ACPROTOCOL was designed to create a common canonical reference for the asset, with each institution keeping its own system. The same identity appears in situations such as:

SITUATIONPATH IN THE ALTERNATINGCURRENTRESULT
Land registry record as a digital file and as a scanned copyUniversal Engine → Canonical EngineACDUP: same content in another file
Trade receivable issued and later presented againCanonical Engine (structured data) · Universal Engine, if it arrives as a fileACDUP: a canonical record of the asset already exists
Document received by different institutionsUniversal Engine → Canonical Engine → ACORACLEACDUP: the same identity at both institutions
Second copy or representation in a new formatACFAST (identical copy) or Universal Engine → Canonical EngineACDUP: same content in another file
New occurrence linked to the evolution of the assetUniversal Engine, if it arrives as a file → Canonical EngineACPAR: the asset evolved, the identity remains

Copy, screenshot, photo or new format: ACDUP. Annotation, amendment or rectification: ACPAR.

Operates together with your registry system

ACPROTOCOL adds the identity of the asset and its history in a single place. When a new certificate arrives, everything is automatic:

  • Recognizes the same asset: on its own, through the canonical identity. No manual search, no record-by-record checking.
  • Compares with the previous version and indicates what changed.
  • Records the new occurrence: directly on the timeline of the same ACIDN.

No typing, no manual registration, no operator searching for the asset. Certificates received as files are read by the Universal Engine.

The basis for the change comes from the event recorded by the responsible institution: with an event, ACPAR; without an event, ACQTN for review.

Transparency

What is developed — and what is roadmap

DEVELOPED

  • Patent filed with INPI (Brazil)
  • Deterministic Canonical Engine implemented
  • ACIDN identity with five public states
  • Canonical timeline of the asset

ARCHITECTURE DEFINED, TO BE TESTED

  • ACFAST: validation on real collections
  • Universal Engine: calibration on real collections
  • Differences between versions in ACPAR

Standardizing humans is impossible
Standardizing machines is mathematics

It's not magic — It's Engineering

Contact

Get in touch

Partners, banks, land registries, exchanges, investors and technical evaluators can write directly to:

Open in my e-mail