One bridge, three spans,
four guarantees.
Here the bridge can be visited up close: the diagram of the attestation engine, the guarantees that hold it up, and the three chapters that go into the detail of each span — where it starts, where it is signed, where it arrives.
One original at the centre, projections on either side.
Cross the bridge, span by span.
Legacy systems
Where the bridge starts: the two entry lanes — direct recording or connector — and the return lane back into your management system.
Enter the chapter →The engine
Where data becomes fact: the signature of whoever generates it, an append-only ledger, one single original — and the translation into every language.
Enter the chapter →The web of data
Where the bridge arrives: what a dataspace is, the three pillars — sovereignty, views, identity — and the return journey.
Enter the chapter →Four guarantees, declared.
Four guarantees hold the bridge up: an explicit data contract for every event, identities conforming to W3C standards, a proof of integrity that outlives the platform, and translations always traceable back to the signed original.
Explicit rules for every event
Every type of event answers to a declared, versioned data contract built on open standards: what comes in is valid by construction, and the evolution of the rules stays tracked over time.
DIDs and Verifiable Credentials (W3C)
People, organisations and machines have decentralised identifiers; attestations travel as signed verifiable credentials. Personal data lives outside the immutable ledger: the mutable master-data records are the GDPR erasure point.
Integrity that resists time
Every fact is protected by a signature and a cryptographic hash, with the proof of integrity ready to outlive the platform: verifiable today, verifiable in ten years, with standard tools.
From the original to every format, and back
Every outgoing format declares the version of the translation that produced it, and from every output you can trace back to the signed original: the check is always possible, in both directions.
On standards and infrastructures we use three precise formulas — compliant with, designed for, aligned with — and we document on what grounds each projection earns them. Precision of language is part of the product.
Open foundations, European frameworks.
TRUST-DAP is aligned with the principles of GAIA-X, designed for eIDAS 2.0 and NIS2, and handles personal data according to the GDPR by construction. Trust is built on open foundations: public standards and European regulatory frameworks, adopted with declared formulas.
GAIA-X
Aligned with the principles of the European data infrastructure: open ecosystems in which the company keeps control over where its own data resides and who can access it.
eIDAS 2.0
Designed for the European digital identity framework: credentials and signatures ready to work with the Union's wallets and certification schemes.
NIS2
Designed according to the requirements of the cybersecurity directive: separation of roles, traceability of access, protection of data throughout the whole cycle.
LEI
Ready to link the digital identity of assets to the legal identity of the company: the chain of trust starts from whoever produces, with a name and a code.
ISO
Data structures aligned with ISO best practice for information quality and security: robust digital processes, calm audits.
GDPR
By construction: personal data lives in the master-data records with its own rights, only identifiers travel in the immutable ledger. Erasure has its exact point.
Want the technical documentation? Write to us →