01
Sensors
<16KB RAM · µW
Architecture
One factory. Every device.
From a 16KB sensor to a GPU cluster: ONE derives the right encryption for every environment by configuring the same proved primitives, never inventing new ones. Every configuration is a signed, witnessed version. The factory is the construction kit. The SDK is how a client picks.
Continuum
Hardware, not an abstraction
Micro sensors, edge nodes, PLCs, gateways, servers, data centers, GPU clusters. Same library. Different signed spec.
one factory: same proved primitives, a signed spec per device. Hardware, not an abstraction
01 · Micro sensors · <16KB RAM · µW
Temp, vibration, beacons, wireless. Ascon-class AEAD. Footprint <4KB. Custom spec · signed v1.
Seven tiers
One continuum of protection
Physics-inspired search. Proved primitives. Deterministic evolution. Optimization tunes parameters; it never invents cryptography.
Engine
How the factory works.
1
Sense & model
Hardware, data, threats, latency, power, memory, compliance targets.
2
Reason & select
Physics-inspired search over proved constructions. Selection, not invention.
3
Configure & synthesise
Same primitives, new parameter set. Generate the optimised implementation.
4
Verify & prove
Machine-checked composition. Known-answer tests. No proof, no ship.
5
Deploy as version
Signed artifact vN. Witnessed, diffable, revocable. Adaptation is never silent.
Factory
The ONE encryption factory
Adaptive configuration engine, live. Same library, different parameter set. Select a tier. Watch the primitives get constructed. Every column is a version bump, not a rewrite.
Live factory
Primitives constructed, not invented
same library · signed spec per tier
1 · Sense & model
Hardware, data, threats, latency, power, memory, compliance targets.
2 · Reason & select
Physics-inspired search over proved constructions. Selection, not invention.
3 · Configure & synthesise
Same primitives, new parameter set. Generate the optimised implementation.
4 · Verify & prove
Machine-checked composition. Known-answer tests. No proof, no ship.
5 · Deploy as version
Signed artifact vN. Witnessed, diffable, revocable. Adaptation is never silent.
Library → this construction
AES-256-GCMChaCha20-Poly1305X25519ECDSAML-KEMML-DSASLH-DSAAsconSPHINCS+ tinysymmetric-firstContext-aware KEMObject semantic cipherProgrammable handshakeML-KEM ∥ X25519AES-GCM ∥ ONE AEADclassical + PQ dual
Ascon-AEADHKDFCTR-DRBG
Output · signed version
Micro sensors
<16KB RAM · µW
Temp, vibration, beacons, wireless. Ascon-class AEAD. Footprint <4KB.
spec v1 · no proof, no ship
the object cipher: your data carries its terms, wherever it goes
“Encrypt the sensitive files in these folders; decrypt only in-terms.”
Q4 forecast
patient file
model weights
board pack
shared cache
agent memory
locked files · ciphertext anywhere · out-of-terms
keys live in hardware, and hardware can travel as its own tiny cloud
HSM-A
epoch 13
HSM-B
epoch 13
HSM-EDGE
epoch 13
Provably secure
Proof replaces assumption. No proof, no ship.
Right-sized
A signed spec per device, from 16KB to GPU scale.
Data that carries its terms
The object cipher carries terms with every object.
Keys in hardware
Rotating, witnessed, mobile. A traveling HSM.
Architecture
Right crypto. Right size. Right now. Everywhere.
See how ONE scales from a sensor to a GPU cluster without changing the trust model.