Running Workloads
Public-safe visibility for workloads moving through the SolarCompute network.
----
Verified public workload totals will appear here when reporting is connected.
----
Workloads waiting for validation or available compute capacity.
----
Workloads currently executing under public workload rules.
----
Completed workload count will be shown when verified public data is available.
From submitted to result
The workload lifecycle gives visitors a simple view of network activity while protecting private workload contents, account data, machine details, and security-sensitive information.
Submit
The workload request is received through a public or platform launcher.
Queue
The workload is checked and waits for suitable compute capacity.
Allocate
The scheduler assigns the workload to a compatible machine or runtime.
Run
The workload executes and returns a public-safe status or result state.
Recent workload movement
This table is prepared for a future public-safe jobs endpoint. It should not expose user identities, prompts, logs, wallet details, tokens, private machine identifiers, or admin-only fields.
| Workload | Status | Runtime | Public Result |
|---|---|---|---|
| ---- | ---- | ---- | ---- |
| ---- | ---- | ---- | ---- |
| ---- | ---- | ---- | ---- |
| ---- | ---- | ---- | ---- |
What can be shown publicly
Public workload reporting should come from a dedicated public endpoint, not directly from admin job tables or private platform records.
The public view should summarise workload movement without exposing sensitive operational or user information.
Suitable public fields
- Public workload label
- Workload type
- Public status
- General runtime
- Public result state
- Aggregate activity totals
What should not be exposed
Public workload visibility must protect users, hosts, machines, workload contents, logs, wallet data, and internal platform systems.
Protected fields
- User IDs, names, emails, and account data
- Private prompts, files, logs, and artifacts
- Wallet balances, payments, and billing records
- Node IDs, host identities, and exact locations
- Container images where they reveal private systems
- Tokens, IP addresses, and internal scheduler details
Workloads connect the public site to the network
Running workload visibility helps visitors understand the basic flow: workloads are submitted, checked, queued, allocated, executed, and returned as a status or result.