A wedding video. A forty-year diary archive. A terabyte of orders. On the Q⁴ Data Engine each of them is named by the same thing: fifteen characters.
Four steps
- Implode: the engine folds the file into a strand and names it with a fifteen-character descriptor.
- Transmit: the descriptor travels by any method, a message, a QR code or a line on paper.
- Decode: confirms you have the right to open it, and for how long.
- Regenerate: with the cell present, the file is rebuilt at the other end, bit-exact.
Why the size does not change the name
The descriptor names the strand, not the bytes. A 1 MB contract and a 1 PB archive both carry fifteen characters. What changes with size is the process behind the scenes, and the lengths we show for it are illustrative until independent validation is complete.
Why fifteen characters are not enough on their own
A descriptor is not a secret. It names a file; it does not open it. Opening needs the cell, which Implexus controls, and a grant that says who may open the file, how, and for how long. Decode checks the grant before Regenerate starts.
The characters travel. The file is rebuilt only where the cell is present, for the people a grant allows.
On the API, the same steps are three endpoints: Safe stores and retrieves, Relay transmits, and Forge gives developers ready environments to build on both.