Lexicon

The words we use, and what they mean.

One meaning for each word, across this site, the SDK and the licence.

The Implexus process

Three parts, from a file to the same file at the far end.

The Implexus process: Implosion, transmission and regeneration: a file is named, its name crosses, and the file is rebuilt at the far end.
Implosion: The first part, carried out by the Implode step. The file is folded into a strand and named by fifteen characters.
Transmission: The second part, carried out by the Transmit step. Only the descriptor crosses, on any channel that carries text; the file stays where it is.
Regeneration: The third part, carried out by the Decode and Regenerate steps. The right to open the file is checked, then the file is rebuilt where the cell is present, bit-exact.

What a file becomes, and what names it.

Descriptor: Fifteen characters that name a file. A descriptor names a file; it does not open it.
Strand: The form the engine holds a file in. It is named by fifteen characters and rebuilt where the cell is present.
Digital DNA: The strand itself: a file in its imploded state, which travels anywhere text does.
The cell: Where strands are held. A file is regenerated only where the cell is present, for the people a grant allows.Custody model to confirm
Fingerprint: A value computed from one piece of a file, used to name the piece and to check it.
Root: The single value a file's fingerprints fold into. The descriptor names it.
Bit-exact: Every bit of the rebuilt file matches the original. What comes back is what went in.

The process, step by step. Every use case runs the same four.

Implode: The file is folded inward into a strand and named by fifteen characters, with nothing lost. It is not made smaller and sent; it is named.
Transmit: The descriptor crosses any channel that carries text. Relay is the Transmit step as an API.
Decode: Confirms you have the right to open it, and for how long. It checks the grant and who you are before Regenerate starts.
Regenerate: The file is rebuilt where the cell is present, bit-exact. Implode and Regenerate are the same step run in opposite directions.

A descriptor names a file. These decide who opens it.

Grant: The record of who may open a file, how, when and how often. Terms are enforced against the grant record Implexus holds. When a grant ends or is withdrawn, the file no longer opens for that party.
Secure element: The part of a device that holds its secret and never lets it out. A device without the right one stays shut, even with a copy of the descriptor.
Scan mark: A printed mark that carries a descriptor. It points to a document; it opens nothing on its own.

SDK: One SDK with three endpoints.
Endpoint: One of the three APIs under every product: Safe, Relay and Forge.
Safe: Store any file as a strand. Retrieve it bit-exact.
Relay: Move strands between people, systems and devices.
Forge: Build and launch applications on the engine.Scope to confirm
Reference design: A worked example a developer or OEM team starts from.
Use case: An example of a job the engine does, shown step by step. Use cases on this site are examples, not current deployments.

Licences are subject to agreement. No rates are published.

Licence: An agreement to build the engine into products: evaluation, product, portfolio or academic. More types are coming.
Royalty per device: What a licensee pays as devices with the engine inside reach the market. It ties what you pay to what you ship.
OEM: A company that builds the engine into the products it makes.
White label: A partner ships a ready application under its own brand.

Each use case runs the four steps in its own demo.