UserBus
THE MECHANICS
Seven steps carry every job, named in the same terms the platform uses: request, match, lease, execute, verify, deliver and settle. Each step below says what happens and who is responsible for it.
01 / THE SEVEN STEPS
A job runs on the model the buyer requested and on the runtime the provider declared.
A buyer submits a request from the console with one model and its parameters. Each submission carries an idempotency key, so a retry resends the same request and returns the same job.
Each provider registers the exact tuple it runs: kind, model, version and runtime. UserBus offers the job to a provider whose tuple matches the request.
The job is leased to one provider at a time. The lease carries a deadline and is renewed by heartbeats while the job runs.
The provider runs the job on its own hardware while it holds the lease. The lease decides who may change the job and its result.
UserBus checks the uploaded file itself: its size, its media type and its digest. A verified upload is the event that completes the job.
The buyer collects the verified result through the console on their own session. Results belong to the account that requested them.
One settlement record is written per completed job, and providers are paid for verified work.
OPEN THE CONSOLE
Requests, job status and results all live in the console.