The architecture separates task coordination from workload execution. The control plane authenticates requests, evaluates policy and maintains authoritative state. Executors receive narrowly scoped leases. Acceptance and accounting services retain records independently of executor claims.
Request flow#
The gateway validates the request and binds it to a tenant. The coordinator freezes the workload, input digest, acceptance profile and quote, reserves eligible capacity and issues a lease. The executor retrieves authorized inputs, runs the specified workload and submits an output reference. The checker evaluates that delivery before the accounting service applies the agreed charging rules.
Deployment and chain boundary#
An initial pilot can operate within one administrative domain while keeping privileges and records separate. Logical separation does not establish independent control. Any shared ownership of coordination, execution and checking must be disclosed.
Inputs, outputs, queues and operational logs remain offchain by default in this design. An onchain commitment or payment record is an optional extension subject to privacy, cost and finality review. A transaction alone cannot establish that a model ran correctly. No chain identifier, contract address or network consensus mechanism is specified as deployed.