Inspired by iSPIRT’s DEPA — the Data Empowerment and Protection Architecture.
A data provider, a model owner, and a clean-room provider sign one contract. Training then runs on the cluster that provider already operates. The raw dataset stays with the provider.
One contract, then one training run on a clean room the provider already operates.
The data provider publishes a dataset. The model owner writes a Ricardian contract that names the dataset, the use, and the clean-room provider.
Each party signs. Training does not start until the contract is signed.
The job runs on that provider’s cluster. The result, the logs, and the provenance stay with the contract.
The contract names the cluster. The kubeconfig path stays on the provider’s Cloud Provider card.
Training stays on this machine.
An existing AKS cluster. The job does not create a subscription.
An existing GKE cluster. The job does not create a project.
An existing OKE cluster. AWS does not start a training job.
A missing kubeconfig path fails the job. Attestation stays simulated until a SEV-SNP guest report verifies.
The same contract is the place to check signatures, training, and audit.
Each party’s signature is stored on the contract before training starts.
A key release stores the time of release. The key bytes are not kept.
An auditor checks a sealed Merkle root in this system. That check is not a filing with an external records office.
Write to hello@dpi-apps.space.