Architectureshared cryptographic core
Every member of the ARIA-AUT family — physical embodiments and cross-cutting modifiers alike — uses the same per-counterparty key derivation primitive: HMAC-SHA-256 over (sender secret, recipient identifier, content hash, optional session nonce, optional temporal sequence, optional materials response). What differs across embodiments is only the physical or computational input that the KDF binds against. This architectural unification is the core IP claim and the basis for the family's commercial proposition.
Embodimentsfive physical realisations
EMBODIMENT A
Cartographic Content Authentication
Pure cryptographic content authentication. No specialty hardware. Document is rendered as ordinary text; voxel field exists as mathematical overlay computed from rendered content geometry. Per-counterparty key derives address subset; verification by phone camera or text input.
Developer · Business · Enterprise
EMBODIMENT B
Visible Voxel Composition
High-end physical anti-counterfeit. 3-px grid stride with 4.5-px paint footprint, ~30,000 ink voxels per document, 8-shape alphabet visible only under magnification. Per-counterparty key selects which voxel addresses carry which shapes.
Enterprise
EMBODIMENT C
Sparse-Blank Subtractive Steganography
Sparse 3-px gaps placed at counterparty-specific positions inside printed strokes, camouflaged as printer defects. Consumer-printer compatible. Optional substrate-fingerprint upgrade folds paper-fibre microstructure into the KDF, defeating high-quality photocopy attacks.
Business · Enterprise
EMBODIMENT D
Active Responsive Substrate
Stimuli-responsive nanoparticles in substrate. Excitation rig at verifier triggers spectral response; the response is folded into the same KDF as A, B, C. Materials qualification 12–18 months. Conceptual UI/UX mockup only at present.
Enterprise · roadmap
EMBODIMENT F
Mechanochromic Fingerprint Reader
Pressure-responsive substrate patch. Finger-on-patch produces unique chromatic imprint; imprint descriptor is folded into the same KDF as A, B, C. Materials qualification 18–24 months. Conceptual UI/UX mockup only at present.
Enterprise · roadmap
Modifierscross-cutting cryptographic primitives
MODIFIER · SEQUENCE-AS-KEY
Temporal Protocol
Adds log₂(N!) bits beyond static address-set verification. The temporal order of address checks is itself a cryptographic secret. Replay attacks defeated by session nonce binding. Wrong-order, wrong-timing, or replayed-trace attempts fail at the first mismatch.
Available across A · B · C · D · F
MODIFIER · BINÔME
Cooperative Cross-Verification
Two or more independent computational verifiers (different architectures, different training, different operating organisations) must agree before a verdict is accepted. Defeats adversarial-AI attacks optimised against a single target verifier. Three consensus modes: 2-of-2 unanimous strict, 3-of-3 full unanimous, 2-of-3 majority.
Available across A · B · C · D · F
Three-tier offeringcommercial structure
The ARIA-AUT family ships as three distinct service tiers, each targeting a different market segment with different feature surface and different pricing model. Tiers are upgrade paths — every primitive in a lower tier is also available in higher tiers.
Developertier
Devs · platforms · SaaS apps integrating auth
Embodiment A (cartographic content authentication)
Three-call SDK · enroll · issue · verify
REST API · 2-line integration
Self-service enrollment
Usage-based · per verification call
Businesstier
Mid-market · notaries · registries · HR · contracts
Embodiments A + C
Substrate-fingerprint upgrade
Sequence-as-Key modifier
Drop-in enterprise integration
No specialty hardware required
Subscription · per seat or per document
Enterprisetier
Banks · governments · art markets · pharma
Full family · A · B · C · D · F
Sequence-as-Key + Binôme cooperative verification
Tamper-evident options · D & F as roadmap
Dedicated support · audit trails
Certified hardware integration paths
Annual licence · per deployment
Navigationopen any demo
Click any tab in the navigation row above to open the corresponding demo. Each demo is a standalone single-file prototype that runs locally; the family shell loads them in sequence to demonstrate the architectural coherence.
Demos available: Embodiment A (cartographic content authentication), Embodiment B (visible voxel composition), Embodiment C (sparse-blank steganography), Sequence-as-Key modifier, Binôme cooperative cross-verification, Embodiments D & F mockups.