Compute-to-Data

NOOSChain routes authorised analytical and AI workloads to nodes that are permitted to access the required bucket data. The workload executes locally; protected source records do not need to leave their authorised environment.

Execution status, results, artifact references, workload identity and provenance are recorded through the blockchain.

Lifecycle

1. Register a signed workload.
2. Request access under the authorization model.
3. Apply an execution policy.
4. Route and run the workload through the workload lifecycle.
5. Record results and artifacts.

Data boundary

• Travels: the signed workload or immutable container reference, its digest, requested buckets and execution policy.
• Stays local: protected bucket records and payloads.
• Recorded: authorization, execution status, result commitments, permitted results, artifact references and provenance.

Authorising a workload does not authorise its creator to read the underlying data. See the security model.

Typical uses

See AI and analytics for inference, model training, statistics, feature extraction, validation and local transformation examples.